Tailwind UI is a phenomenal product, but, there's a simple mathematical reason you cannot sell code like in this way to create a sustainable business

same way a lesser engineer might say they cannot do X or Y

hate only comes from below!

Can't enforce everyone to scan

What are you going to do? Arrest everyone?

> ... providers to search all private chats, messages, and emails automatically for suspicious content [1]

Even if that were the case, the answer is the Framework phone

[1] https://www.patrick-breyer.de/en/posts/chat-control/

The point is that the site, contacting your local MEP, and all the discussion in this thread, is pointless to affect some kind of durable societal change

Pointing out that it's vibe-coded just emphasises that all of the above actions are just low-effort cope

States control what’s centralized; incentives ensure they keep doing so.

Protesting it is like arguing with a thermostat—it can’t hear you, and it’s built to tighten control.

As technologists, we have a lot more power than we realise.

(Yes, I’m speaking to the blob, but the Venn overlap of anti-crypto and pro-this seems big.)

What could go wrong?

I see this "one tool to rule them all" and instantly my senses go off that this is too good to be true to work in all the long-tail scenarios.

There always seems to be some strange edge-cases with tools of this nature.

Just don't use them, and, outcompete those who do. Or, use them and outcompete those who don't.

Belittling/lamenting on any thread about them is not helpful and akin to spam.

This. The dev's outcompeting by using AI today are too busy shipping, rather than wasting time writing blog posts about what ultimately, is a skill-issue.

There’s your issue, the skill of programming has changed.

Typing gets fast; so does review once robust tests already prove X, Y, Z correctness properties.

With the invariants green, you get faster at grokking the diff, feed style nits back into the system prompt, and keep tuning the infinite tap to your taste.

For Rails's productivity, there's many reasons. One is the 'Active Stack' which acts as a 'standard library' of sorts for the framework.

It provides extremely seamless tooling all the way from the most frontend of concerns (ActiveView - HTML/JS) to the backend (ActiveRecord - SQL ORM layer) and anything in between (ActiveController - HTTP Requests, ActiveMailer - Emails etc.). These tools are simple, robust and cohesive.

These primitives are built on by the community to provide powerful tooling (Devise, OmniAuth, amongst others) that allows one to implement the standard plumbing most SaaS/CRUD apps need in a few minutes - billing, auth, emails so you can get to writing business logic in a few minutes and have the boring stuff solved quickly.

Implementing just these basics in JS can take many hours and have you scratching your head wondering "Why are there 20 different ways to implement X? Why is there no tried and true way for something that are surely been done thousands of times? Why hasn't someone abstracted these details all away yet? Why do I have to npm install for this basic functionality? Wait, why did my build tooling just break?"