3 ms·
I used to be fully convinced around 2010-2013 that full-stack was the way to go. I've since then become much less convinced. All aspects have become more comple
by ajmurmann 8y ago
I used to be fully convinced around 2010-2013 that full-stack was the way to go. I've since then become much less convinced. All aspects have become more complex. Back then you need to know CSS, HTML and jQuery and the front end was under control (at least if you knew how to deal with some of the browser weirdnesses). On the back end you frequently had a monolith Rails server. Now on the front end you frequently have a single page app where JS is much more integral and comes with its own range of frameworks and it's own pipelines that seem to change every few years. On the back you now likely will have a bunch of micro services that want to be orchestrated. Not sure if the world needs to be more complicated, but it certainly often times is.
- collyw 8y agoYou could just ignore the JS churn and stick with enough jQuery to be useful. Most SPA apps don't need to be SPA. Backends don't need to be micro services.