muspimerol

Because like 30% of the websites in the world are on WordPress, and countless others in custom PHP? Not exactly a trivial task.

The flaw in that ideology is that everyone relies on the next generation for care in their old age. Taking advantage of the future generation without contributing to raising it isn't selfless in the slightest.

If you live in a developed country you probably already have a demographic crisis. Not having kids is hurting the next generation, not helping.

There's still a cost/benefit to building and maintaining a service. LLMs make it easier to build, but the cost does not scale to zero.

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.

Good thing that's exactly what the article suggests!

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.

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?

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.

> Does the fact that WFH is not a thing mean that in the real world, for most people, coming to the office IS actually more efficient?

I don't think the labor market is efficient to such a degree that we can draw this conclusion. Lots of startups are doing this, but it takes time, capital and luck to achieve the success of the big corporate competitors, which have a huge amount of middle management who hate WFH.

Fair point, but I have seen a lot of shitty software developed with this mantra. Usually because the "iterate" part is forgotten in favor of the next "rapid" development. I agree that the quickest way to learn whether your solution is valid is to ship & experiment. But once you know the solution (which is sometimes not even that complicated) then you should really take the time to produce a solid piece of software before moving on.

But I agree, my original comment is probably a little too critical. There are valid times to rapidly iterate and ship. When it turns into the _only_ way you ship software, I think it becomes a problem.