4 ms·
It's a bad sign for .js devs: trouble ahead.
by puppetmaster3 13y ago
It's a bad sign for .js devs: trouble ahead.
- edwinnathaniel 13y agoJS ecosystems in terms of quality, tooling, and engineering is already bad, can't be worse than that really... PS: No, yet-another-js-library-to-replace-jquery is not considered tooling. No, yet-another-replacement-for-grunt/bower/yeoman is not a good sign of the ecosystems. Java has Maven since 2004.
- puppetmaster3 13y agoMaven is horible. Hth
- edwinnathaniel 13y agoIt's awesome and other tools (bundler) are copying it or build on top of it (gradle, buildr, Ivy repo). XML is horrible, not Maven. Python tools don't even come close. Ditto with .NET NuGet. Find me a tool that can compare feature by feature with Maven and still relevant for a long time.
- Buttons840 13y agoI've always said: "With Java plus XML, you can have one language for the price of two." With Java, you write a lot of syntax to get static typing, but it's worth it because static typing! Then you throw static typing away (because now it's to restrictive I suppose?) to use XML files which must be structured a certain unpredictable way or you'll cry at the traceback you receive, and pray your imminent Google search can make sense of it all.
- RyanZAG 13y agoNobody with any sense uses XML in Java anymore. Everything uses annotations now.
- coldtea 13y agoWell, your responses mostly amount to "OMG, I hate Java coders / everything there sucks" etc. Not really insightful.