left-pad
logrus
left-pad | logrus | |
---|---|---|
7 | 32 | |
1,178 | 24,078 | |
- | - | |
0.0 | 3.0 | |
about 5 years ago | about 1 month ago | |
JavaScript | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
left-pad
-
The Case for Frameworks
It's pretty easy to find that the example I gave isn't gamed... A cursory search on GitHub can find a couple examples like dotenv [1] and npm's cli [2] both use it via an older version of nodejs/readable-stream [3].
There's also the classic left-pad debacle - https://github.com/left-pad/left-pad/issues/4
[1] - https://github.com/motdotla/dotenv/blob/master/package-lock....
-
Serverless Containers vs Serverless Next.js SSR on AWS, GCP and Vercel
when using some other modern libraries like tailwind, you have to update the Next.js version carefully or you may have some errors following the Next.js update. Nothing new in javascript world, if something is working it's not guaranteed it will last :) It is important to really read the Next.js release notes as the base configuration may change in between the releases.
-
This resume got me an interview!
It's OK, it's reddit, it happens. I will say however that unless you are deploying to a windows server on premise somewhere you are using open source. (And soon even that won't be true because eventually Windows is going to be based on Linux.) I'm not asking people to give up their weekends or anything, but IMO if you consume open source, you have an obligation to contribute back something. Even if it's just reporting a bug on some library that you use.
-
XKCD 2347
Funny story, on the day that they unpublished it, the package.json states the license to be "WTFPL", which allows NPM to Do What The Fuck You Want To
-
Algorithmic Complexity of Left-Pad
It had been optimized (and deprecated) since then. See https://github.com/left-pad/left-pad/blob/master/index.js
- We’ve all been there
- Announcing Standard Ruby 1.0
logrus
-
Authentication system using Golang and Sveltekit - Initialization and setup
It's some sort of logging system well explained by Alex Edwards in Let’s Go Further. As stated, we could have used logrus or any other popular logging system in Go.
-
Renaming public Go modules
Option 2, please. You may not have been around for the logrus debacle, but it was a giant pain.
- What is the common log library which is industry standard that is used in server applications?
-
Observing AWS Lambda with Golang and Datadog
For the example I’m using the very popular logrus library and then I’m setting the log formatter to be JSON
-
Best Logging Library for Golang
For choosing the candidates for the poll, I didn't do any thorough research. I was looking for a library to use in my project at work, and I ended up at sirupsen/logrus which was already being used by one of the dependencies in that project.
-
Follow up to previous post: I contributed to an open source project outside working hours despite being asked not to. I was fired. No legal action.
I contribute to OSS as part of my job on the regular. The company is good about contributing upstream, signing CLAs, and all that. We still work against private forks for two main reasons: 1. Some changes that we need are not accepted by maintainers based on philosophical or architectural reasons that we can’t otherwise work around. You’re beholden to then unless you publicly fork the repo which has other legal/PR overhead for the company and OSS political implications. 2. Maintainers in the past have taken down repos, renamed repos, or changed the licensing on repos that have left us in a lurch. We always build against our own private forks because we need predictability and can’t be beholden to some other party for business continuity. We sync them down from the public upstream at our leisure.
-
Sourcehut will blacklist the Go module mirror
If they change the case on their username on the other hand, the Go ecosystem explodes: https://github.com/sirupsen/logrus/issues/570#issuecomment-3...
-
Lies we tell ourselves to keep using Golang
Like, for example, some projects importing logrus with a capital L and some with a lowercase L, and go modules having no way to reconcile the two: https://github.com/sirupsen/logrus/issues/553
-
go-coffeeshop - A practical coffee shop application event-driven microservices built with Golang
Ugh. Wish people would stop using logrus. It’s in maintenance mode and slow, especially its stack tracing.
- Criando uma API Rest com Fiber - Uma história pessoal de aprendizado
What are some alternatives?
featured
zap - Blazing fast, structured, leveled logging in Go.
RawRead - Platform-independent tool for creating, reading and erasing NoFS-formatted memory cards
zerolog - Zero Allocation JSON Logger
glog - Leveled execution logs for Go
lumberjack - lumberjack is a log rolling package for Go
slog
log15 - Structured, composable logging for Go
seelog - Seelog is a native Go logging library that provides flexible asynchronous dispatching, filtering, and formatting.
log - Structured logging package for Go.
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
go-log - a golang log lib supports level and multi handlers