4 ms·

The skeleton I use to create weekend projects is the same as what I use to create enterprise projects. I don't see the need to juggle "simpler" frameworks for n

The skeleton I use to create weekend projects is the same as what I use to create enterprise projects. I don't see the need to juggle "simpler" frameworks for no reason, especially when those "simpler" frameworks are harder to use (because you have to remake everything yourself) There are many small things I don't want to recreate that are always needed in every web app. Translations, authorization, accessibility, bug tracking, and more. Another person said it best. You aren't going to use your own C++ compiler just because it's simpler and you don't need all the features, why do the same to the toolchains for the web?

dclusin 7y ago
Following this logic Spring never would have been invented in the Java world because Java EE does everything you need it to even though you don't need all of those features. Frameworks and tool chains become bloated and convoluted over time. I'm not super well versed in react/js/etc web development, but given the regularity that you see and hear about these sorts of posts, a not insignificant minority feels like the toolchain is overly complex for lots of use cases. If it wasn't then the post wouldn't have made it to the front page. It wouldn't have been upvoted just like our comments in this discussion :) Just because you find the toolchain an easy to understand time saver that's pretty DRY doesn't mean everyone else does. Who knows? Maybe complexity in React will continue to increase and someone somewhere will invent the Spring equivalent for React. Why would they? Because they didn't need all of those features. (Also thought of Vue.js spinoff from AngularJS)