I'm in agreement with your claim, though if you recall some of these micro SaaSes went hyperfocused on niches. The value proposition is then smaller, with larger data liability than with some behemoth's of SaaS.
Though for the later ones, one might also ask themselves if they are worth their cost when using 20-30% of provided functionality.
The point is that we will still need senior level employees, but the way fresh grads get to that level is generally through entry level positions, experience and mentorship. I don't think we can expect the university system to start pumping out senior level graduates.
This happens regardless of which framework is used or even if no framework is used. Plenty of web developers do not understand how the browser or JS work at a deep level.
Yeah, it's pretty close to the "Imagine how great the world would be if everyone used Lisp/Haskell/WhateverLang instead of Java/JS everywhere!" take you sometimes see. As if the common developer wouldn't just write in all those languages like they're Java/JS, and keep clear of the advanced macros/type systems/whatever.
Even languages or environments that try to "steer the developer into the correct direction" have only really managed it when the new direction is something they already might've chosen to write. Otherwise, you just end up with many square pegs filed down to fit in round holes.
How does versioning work? After you fork an HTML app, is there a way to update it and get newer features without manual intervention?
I'm thinking about the Kanban board example I saw in the demo video. It looks like column re-ordering wasn't supported yet. What if I fork the app, put time into creating my Kanban, then I want to update to a new version that supports column re-ordering?
> a mishmash of vibe coded stuff you don’t understand.
No, there is a difference between "I wrote this code" and "I understand this code". You don't need to write all the code in a project to understand it. Otherwise writing software in a team would not be a viable undertaking.
Why do you say "JSX"? JSX is an HTML templating language for JavaScript. templ looks like an HTML templating language for Go. Every popular web backend language has an HTML templating language... so that it can produce HTML - is it really that surprising?
Here's the react-table example app with 112,500 records, just like your example. I am not really seeing much of a performance difference (and this is in dev mode - it would be faster if built for production):
This comparison is disingenuous and off-putting. When I read "a React button" I assume you are talking about `<button>` and the React runtime, not some third party libraries.
But logging in and posting don't seem like "undoable" actions to me. That would be similar to undoing a save or undoing a login to Adobe CC in Photoshop. Things definitely get trickier with network requests, but that can be solved with something like CRDT.
