The problem is simple:
Browsers have to apologize for JS and 30 years of backwards compatibility.
On the surface, you conclusion is correct: Move on to better tech alreday.
However, JS and backwards compat IS the moat for browser makers. Setting aside the fact that it'd be a big bang moment for the internet, browser makers have no vested interest in actually doing that, being that for a viable competitor to enter the market, it requires a Herculean effort a la LadyBird. They like that. It's good for them. And the longer this goes on and the more convoluted and bloated it can become, the better.
@air_framp_one@ggs4ns It's not just cross platform apps he's getting at, but an environment that is also agnostic as to the guest language so long as that language can target wasm.
and for the record, I spent a LONG time contemplating exactly what you are describing about two years ago, and the long story short is that it just isn't practical, even if it were possible. The entire browser platform is just flawed inherently and there's no getting around that.
The way to go is to just build an entirely new runtime platform and not think about the browser at all, which is what I ended up doing.
I have already built this in Odin. I build my own apps in whatever language I want (provided it compiles to wasm), and manipulate the UI with an API I spec'd for the guest language to use.
I also have a local model "store". So the guest app can request use of a model (e.g. a vector model), and then the runtime will run download it off hugging face if it's not already there and make it available for the guest app to use.
It's pretty cool. But you are not by definition building a browser. It's just a runtime env.
I find myself picking up the phone and calling businesses more and more because AI text chat bots are terrible, and even if they weren't no one likes to talk to them because consumer confidence has been so thoroughly eroded by bad experiences.
It'd be interesting to see the data on consumer behavior as more and more AI text chat bots take over support.
Software Engineering is not automated.
Not even coding has been automated.
It depends on what you're working on.
If you're building CRUD apps for the web or desktop in a commonly used language with common tooling and frameworks, yes, coding is largely, but still not entirely automated.
Anything beyond that, the idea that a human is no longer needed is not, not will it ever be, automated.
@rfleury I think this is an important point, and agreed.
Not all software is dirt, needing to be moved from point A to point B.
Choose the projects you focus on.
I had @grok 4.6 generate a very long mdbook for a site I've created while I was asleep last night, hoping it'd burn through a chunk of the remaining 50% of my tokens before the reset on Friday.
Fortunately it was near-perfect.
Unfortunately it only used 2%.
I can't endorse Grok enough.
If you spend money with Anthropic, stop.
They are outright anti-technology, are irreparably damaging the industry in a cowardly and pathetic attempt to benefit themselves, and do not deserve your money.
They are making you worse at your job, and that is their goal as they lie through their teeth about “how concerned they are”.
This has to be the single most morally bankrupt company that has ever existed in modern technology, and nobody—least of all developers who know better—should support them.
Just stop.
@HSVSphere But won't you miss manually turning your fans on and off so kernal_task doesn't grind your machine to a halt because Steve Jobs didn't like fan noise
Today, on the heels of a very large production deployment involving load balancers, networking, applications, and a mix of 10+ application and db servers both on VMs and as-a-service, I carved out the requisite few hours to manually produce the documentation.
I could have uploaded all the notes and existing docs into a copilot chat and had it spit out the documentation, but I chose not to, despite AI being able to complete such a task, imminently more so than writing code.
The reason I wrote the documentation myself is because I also have to maintain the system. I want to know it--and actually writing out what *it* is--*is* the process of coming to know the system.
Skipping the process of manually producing the documentation introduces a risk vector that *will* come to bear.
The production of the documentation is as important as it having been produced, and to the extent this applies to documentation, it applies infinitely more more to a code base.
I have tried vibe coding and literally can not wrap my head around how people take any of this seriously.
Even “AI assissted” coding is a dumpster fire.
Even “just add comments” is useless because adding comments and cleaning up is an exercise in understanding the code.
Despite having tried, I can not find a reasonable use outside of a chat bot to ask questions.
@vvsmoe@garrytan The right to free speech is a philosophical principle any individual can and should endorse.
What someone actually speaks when exercising that right is a choice that others can choose to support or not.
Pitting these two concepts against each other is a false dichotomy.