Remix.run Logo
gregates 14 hours ago

> Lee's argument for moving to code is that agents can work with code.

So do you think this is a misrepresentation of Lee's argument? Again, I couldn't be bothered to read the original, so I'm relying on this interpretation of the original.

arionmiles 14 hours ago | parent [-]

There's no sense in answering your questions when you actively refuse to read the article. You're more susceptible to misunderstand the arguments given your apparent bias on AI-motivated downsizing, which I must reiterate is not covered in the article at all.

gregates 13 hours ago | parent [-]

Alright you badgered me into reading the original and the linked post does not misinterpret it.

> Previously, we could @cursor and ask it to modify the code and content, but now we introduced a new CMS abstraction in between. Everything became a bit more clunky. We went back to clicking through UI menus versus asking agents to do things for us.

> With AI and coding agents, the cost of an abstraction has never been higher. I asked them: do we really need a CMS? Will people care if they have to use a chatbot to modify content versus a GUI?

> For many teams, the cost of the CMS abstraction is worth it. They need to have a portal where writers or marketers can log in, click a few buttons, and change the content.

> More importantly, the migration has already been worth it. The first day after, I merged a fix to the website from a cloud agent on my phone.

> The cost of abstractions with AI is very high.

The whole argument is about how it's easier to use agents to modify the website without a CMS in the way.

This is an AI company saying "if you buy our product you don't need a CMS" and a CMS company saying "nuh-uh, you still need a CMS".

The most interesting thing here is that the CMS company feels the need to respond to the AI company's argument publicly.

antonvs 7 hours ago | parent [-]

> This is an AI company saying "if you buy our product you don't need a CMS"

No, it isn't. The AI company was explicit about their use case not being a general one:

> "For many teams, the cost of the CMS abstraction is worth it. They need to have a portal where writers or marketers can log in, click a few buttons, and change the content. It’s been like this since the dawn of time (WordPress)."

> Alright you badgered me into reading the original

It's not "badgering" you to point out that your comments are pointless if they're just going to speculate about something you haven't read. But if you feel "badgered", you could just not comment next time, that way no-one will "badger" you.