You should look into rbs-inline. It's a huge DX improvement. The community spoke up and they are moving in the right direction now.

AI is thinking the same way a film's picture actually moves.

It's an illusion that's good enough that our brains accept it and it's a useful tool.

> At this point I'd rather use GCP over Azure and I have zero seconds of experience with it.

TBH, GCP is very good! More people should use it.

I know for some people the prospect of losing their Google Cloud access due to an automated terms of service violation on some completely unrelated service is worrisome.

https://cloud.google.com/resource-manager/docs/project-suspe...

I'd hope you can create a Google Cloud account under a completely different email address, but I do as little business with Google as I can get away with, so I have no idea.

That's generally speaking a good practice anyways. My Amazon shopping account has a different email than my Amazon Web Services account. I intuited that they need to be different from the get go.

I haven't used much of GCP, but I have had a good experience with Cloud Run and really haven't found a comparable offering from the other clouds.

Cloud Run is incredible. It’s one of those things I wish more devs knew about. Even at work where we use GCP all the “smart” devs insist on GKE for their “webscale” services that get dozens of requests a second. Dozens!

Isn’t ECS Fargate pretty much the same thing?

ACI is the corresponding service in our favorite cloud.

>I've used AWS, Azure, and recently GCP. You do NOT want to use GCP.

>TBH, GCP is very good! More people should use it.

These takes couldn't be further apart. Gotta love HN comments.

GCP console is not the best but as a long term multicloud user, I can assure you that GCP is much better than Azure portal and/or Azure APIs which is fucking hell

have used both. I prefer Azure. Much easier to use. found GCP unintuitive.

I mean, it's clear he means for the majority of users and OSes... not the HN crowd specifically.

Also, to be clear, I’m mostly goofing about it CLIs, and — as I mentioned in the piece — I use one every day. But yes, there are four or five billion internet users who don’t and never will. And CLIs are a poor user interface for 99+% of the tasks that people accomplish on computing devices, or with browsers, which is pertinent for the point I was making.

If I’d anticipated breaching containment and heading towards the orange site, I may not have risked the combination of humor and anything that’s not completely literal in its language. Alas.

Anil, your blog is too wide for my iPhone 11 Pro’s screen. I have to scroll side-to-side to read it.

Anyone normal knew what you meant

Honestly, seeing the Datastar server-side snippets reminded me of writing RJS in Rails back in the day.

Everything old is new again.

Having the backend aware of the IDs in the HTML leads to pain. The HTMX way seems a lot simpler and Rails + Turbo has gone in that direction as well.

i don't know what the big deal is

with a REST API, the front and back ends need to agree on the JSON field names

with an HTML API for Datastar, the front and back ends need to agree on the element IDs

Really not a huge difference

Right but this isn’t a REST API. This technique specifically rejects that approach.

With htmx, the server just returns HTML and the logic for handling it is entirely in the front end.

Huh? HTML is sitting right there and it's out of the box with Rails. CSS3 is basically scss now.

I don't understand the aversion to actually writing HTML and CSS!

> their homemade JS solutions (Stimulus, Hotwire, JS import maps) should be the default choice instead of industry standards like Intertia and Vite.

Funny you should list those out. JS Import Maps (https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...) are literally an industry standard while Inertia and Vite are decidedly NOT standards in any way, shape, or form.

Industry standards are not platform standards. React (enabled by Inertia) is in many ways is an industry standard for building UIs on the web today, yet it's not part of the platform. Same with Vite, it's the standard way to bundle on the web.

Decidedly, Import Maps are not used as a standard for dependency management in the web dev industry.

> If adding tools to the setup is needed

It is not needed.

Basically, LLMs are the guy from Memento.

Which seems like a trivial addition if it's not there?

It is, but now you're burning a bit of context on something that might not be necessary, and potentially having the agent focus on time when it's not relevant. Not necessarily a bad idea, but as always, tradeoffs.