gadr90

I tried to build and sell a CMS and frontend-as-a-service for 3 years. We "failed" as in not-rocketship-revenue. Now we are on board the software factory train and we are _replacing_ the services companies that used to operate our software. Now we are growing 20x faster. Welcome to the brave new world of Service as Software, I guess! Testing this mostly in Brazil/enterprise, launching support for Shopify this month.

I asked ChatGPT to replace "current AI" and synonyms with "HUMANS" and I'm satisfied. My favorite revised sentences:

"Does HUMANS represent a dead end?"

"HUMANS should not be used for serious applications."

"HUMANS are unmanageable, and as a consequence their use in serious contexts is irresponsible."

"HUMANS have no internal structure that relates meaningfully to their functionality."

"HUMANS have input and state spaces too large for exhaustive testing."

"HUMANS do not allow verification by parts (unit testing, integration testing, etc)."

"HUMANS have faults, but even their error behaviour is likely emergent, and certainly hard to predict or eradicate."

"HUMANS have no model of knowledge and no representation of any ‘reasoning.’"

"HUMANS represent a dead end, where exponential increases of training data and effort will give us modest increases in impressive plausibility but no foundational increase in reliability."

"HUMANS cannot be developed, or reused, as components."

"There is no possibility for stepwise development — using either informal or formal methods — for HUMANS."

and my favorite:

"In my mind, all this puts even state-of-the-art HUMANS in a position where professional responsibility dictates the avoidance of them in any serious application."

Worse things have been said about them

That is true. Good docs, examples and community wins.

There are those who would say they created a "bait and switch" from their open framework into their closed for-profit deployment platform. That is not objectively wrong, though. But still, many complain. I say: good for them. Let competition happen.

I happen to be from Rio de Janeiro, Brazil, so I never met Nate — yet! But I'm pretty sure our paths will cross in the long long road of web development ahead of us :)

I am a fierce hater of the complexity and closed-ness which Next.js became, BUT "results don't have to be explained" and Mr. Guillermo unarguably executed the hell out of it. It IS the default for new frontend developers, right now. I don't think it will necessarily remain, specially because of things like One!

What the hell, Nate! As a long-time web developer who witnessed the divide between frontend and backend, this looks like the most transformative step forward since Next.js. What you have built here is amazing, and it's definitely something that the industry needs right now.

Me and my team have been working on a new Web Draw-first IDE that we're going to launch in a few weeks. And I just sent this thread to my engineering team demanding that they swiftly integrate One into our web draw, or they will walk the board! Just kidding. We're not really pirates. Anyway, amazing work, looking forward to using it for many projects here!!!