if the rich western world you mentioned is the US, I'd like to remind you that no economy needs that amount of fast food workers

What you described is that your team is producing software. That is exactly what a team of developers did 10 or 20 years ago.

Doing X in Y days does not mean much, same thing happened with Ruby on Rails.

what's up rauchg?

is it you, rauchg?

> they were quite religious, arguably to a fault

to what fault, slavery?

Slavery was ended for largely religious reasons so unless you think slavery is a good thing then that wouldn’t make sense. I was thinking more of rigid and highly dogmatic moral beliefs that cause people to condemn heretics. “Anyone who disagrees with me is a nazi/witch” sort of stuff. It’s a very American thing I would argue, but it seems to be spreading quite quickly.

taking advantage of the collective is still a scam.

why would it be big in web if that is not the reason people use lua?

I always thought selling a good product is easy.

Creating a good product that is hard.

And selling a bad product is hard so the people with this skill makes a lot of money.

Creating a good product requires lots of interaction with your target customers. You can call the "sales" in the beginning, but it's really understanding how to tweak your product from an idea to solve a problem into something that fits into the customer's workflows and solves their problems. The only way to really validate the product is to see who pays money for it.

Maybe the problem is using React for that.

> The only downside is that sooner or later, you hit the scaling trap.

Which they might be able to overcome faster with the help of AI, again.

Trying to fix broken architecture with the same AI that wrote it leads to recursive technical debt. AI can rewrite code, but it cannot make strategic decisions if the operator doesn't understand the problem. In the end, instead of a fix, you get a Big Ball of Mud, just built 10x faster