Re:The tragedy of running an old Node project
by dilap on Tuesday November 19, 2024 @11:56AM
(#42185563)
Plus even if you were using lots of deps, the Go code would almost certainly keep working, thanks to minimal version selection and the Go module mirror. (And of course for maximum reliability, could even easily vendor deps with "go mod vendor".)
Re:The tragedy of running an old Node project
by guappa on Tuesday November 19, 2024 @03:15PM
(#42187619)
> Go is especially good because of the large stdlib
Come on… compare it with what java and python have.
Re:The tragedy of running an old Node project
by blizdiddy on Tuesday November 19, 2024 @03:59PM
(#42188024)
Java can't even read/write json without third party libraries.
Tell me a single thing that Oracle has added to the standard library. As far as I can tell, more and more of what was once standard is now getting offloaded and trademark-washed with the eclipse and apache foundations.
Re:The tragedy of running an old Node project
by dartos on Tuesday November 19, 2024 @03:28PM
(#42187755)
What does Java or Python have in their stdlib that go doesn’t?
Re:The tragedy of running an old Node project
by guappa on Tuesday November 19, 2024 @04:53PM
(#42188499)
Well python has syslog, mmap, just to name a couple of things.
Re:The tragedy of running an old Node project
by dartos on Wednesday November 20, 2024 @08:29AM
(#42193768)
They had mmap, but it was dropped at some point, I guess.
They do have syslog though https://pkg.go.dev/log/syslog
This is true but there's also a factor from the language/framework in use. Node is especially bad because of it generates huge package dependency trees. Go is especially good because of the large stdlib (which I use to minimize deps in https://github.com/contribsys/faktory) and excellent backwards compatibility.