We went down a similar path (using Hotwire, non the less!) and got to many of the same conclusions. It is impressive to see what CSS does and how many of the headaches are gone and :has is very powerful.
Alas, after several months we tore it all out and went back to React+Tailwind.
We still use native HTML popovers and :has selectors and other things we've have learned.
But writing UIs across three files (template, stimulus controllers, css) is such a tremendous bore. Concepts that belong together are spread out and I needed to be diligent with placing attributes and classes and remember to remove them all when removing functionality again. Obviously no compile-time checks, just magic strings and runtime errors. The Hotwire docs were also surprisingly hard to work with. All in all a lot of friction.
This just was not worth it.
inb4 rage, it is possible to use React for the UI alone and pass in fully formed view models, use form submissions and links.
I remember, maybe 2-3 years ago, chuckling at Google with their Bard naming and being late to the game and so on. It seems like I was very wrong and that they caught up quickly enough. I was also wrong in thinking MS doing well, when their recent Copilot moves across Office, Windows, and GitHub have been a joke.
I disagree with the new rule. The old one is fine and applies to LLMs.
Vibing and good enough is a terrible combination, as unknown elements of the system grow at a faster rate than ever.
Using LLMs while understanding every change and retaining a mental model of the system is fine.
Granted, I see vibe+ignorance way too often as it is the short-term path of least resistance in the current climate of RTO and bums in seats and grind and ever more features.
There are all of the usual signs. Overuse of em-dashes (34 of them), overuse of colons (41 of them), overuse of lists of three items comma-separated, incoherent overusage of bold text, overly terse "x → y" lists.
Some excerpts that are particularly obvious:
> Approve a drug that kills: massive public scandal, congressional hearings, career destruction—the action is visible, attributable, punishable. Delay a drug that would save lives: invisible deaths, no scandal, no attribution—the people who died waiting never become a story.
---
> The mechanics:
> *Interaction implies liability*: Help a homeless person imperfectly → criticized for the imperfection
> *Profit implies guilt*: Sell cheap water in a drought → "profiteer," "monster"
> *Ignorance implies innocence*: Ignore the problem entirely → zero criticism
---
> The Copenhagen Trap doesn't just affect decisions. It affects *who makes decisions*. This is not about individual choices. It is about civilizational selection pressure.
People do not typically use a combined 75 of them in one short essay, and I pointed out several other reasons. Do you know many people IRL who use a colon/em-dash in almost every single paragraph they write, while also just so happening to mimick multiple other LLM writing patterns? Please do not be so childishly reductive. If my comment could be reduced to "it contains em-dashes", then the comment I would've wrote would be "it contains em-dashes".
please don't defend this atrocious llm writing style (and thus, implicitly, the broader issue of people outsourcing writing to llms) by picking random aspects thereof and pointing out that there are human writers who share them
t. someone who uses a lot of em-dashes and doesn't plan to stop
Some apps only (usably) exist on mobile, like Tinder or Tiktok. Not sure that niche is worth a full new OS though, but Googlers need their promotion so here we are.
My laptop can go on for days as well as long as I plug it in to a power bank. I just need to lug them around, defeating the purpose.
reply