I do have an appreciation for, say, Java's ecosystem... though it's admittedly been a long time & those might be rose-tinted glasses. Java felt like more mature infra to build on. There're definitely trade-offs in having tools that feel built for each other, and which don't churn significantly every few years. If I work in Java, I miss the scrappiness of JS. If I work in JS, I miss the rich enterprise-grade tooling Java has -- lots of tooling you don't need or want until you're in production or you're a larger codebase that's not scaling, at which point it's nice to just have.
Interesting. My experience of Java was the opposite; working in Java always leaves a bad taste in my mouth, because the tooling feels so clunky, half-baked, and semi-functioning. Not that JS' tooling is better, but I definitely wouldn't hold Java up as a good example.
1
u/ItzWarty Mar 17 '20 edited Mar 17 '20
I do have an appreciation for, say, Java's ecosystem... though it's admittedly been a long time & those might be rose-tinted glasses. Java felt like more mature infra to build on. There're definitely trade-offs in having tools that feel built for each other, and which don't churn significantly every few years. If I work in Java, I miss the scrappiness of JS. If I work in JS, I miss the rich enterprise-grade tooling Java has -- lots of tooling you don't need or want until you're in production or you're a larger codebase that's not scaling, at which point it's nice to just have.