4 ms·
Yeah, there is the legacy of the thousands of mature libraries, frameworks and development tools. Legacy isn't always a bad thing.
by gerbilly 7y ago
Yeah, there is the legacy of the thousands of mature libraries, frameworks and development tools.
Legacy isn't always a bad thing.
- crimsonalucard 7y agonever said it was bad. But just wanted to state that it's not all newness.
- gerbilly 7y agoTo me Java is like a diesel engine, old but proven technology that can keep on chugging for hundreds of thousands of hours. (Not to discount the recent improvements in GC, etc which are also amazing...)
- tomohawk 7y agoHaving moved to a stack with a much more competent standard library, it's much nicer to have that great standard library than to have to wade through a rich set of libraries all the time to achieve the same thing. I'm talking about Go, of course. It's just nice getting right to work coding up an http server without having to think about what "web framework" I should need to select, or which logging library to use.
- kgc 7y agoWhat stack?