4 ms·
It sure looks like we’re nearing the “peak Java Enterprise Edition” moment for frontend web development space. We got here honestly: Single Page Apps made “fat
by jt2190 4y ago
It sure looks like we’re nearing the “peak Java Enterprise Edition” moment for frontend web development space.
We got here honestly: Single Page Apps made “fat” clients possible in the browser, but that meant a lot of logic had to move to the front end, so they naturally became bigger and more complex. Meanwhile, we still want to have the “lazy installation” experience of browsing to a web page and having things load quickly, and this adds all sorts of complexity like bundle splitting, hydration, “edge” hosting, etc.
I’m not sure where we go from here, complexity-wise, but here are some guesses:
* no/low code will produce a new “ruby on rails” for the modern SPA space. (There are already contenders.)
* increased environment complexity will move development into the cloud and off of our local machines.
* there won’t be a sudden disappearance of the older approaches, just like SPAs didn’t kill RoR.
- stavros 4y agoI think we'll just go back to the old approaches. I already build apps with thin frontends, and maybe use HTMX if desired. Fat frontends aren't worth the complexity unless you have an interactive app (e.g. Google Docs), which you very probably don't.