You can use lit-html to get declarative reactivity, but then it's just basically react again.

On the inside, but not on the outside. Web Components standardize the interface for components to interact like MCP standardized the protocol but the server itself can be in and language. You can't just mix Solid, React and Vue components together but you can use any web component in a Lit app.

Running apps is what RAM should be used for, not wasted on the base system.

This is just slop.

It was already brought down by Rockstar as well.

This isn't just reverse engineering, it's a decompiled source from the original binary.

Would that be Urban Chaos?

Yes! That's the one! Thanks! Omg, I need to play that game now!

Airbnb, Uber and Amazon were already making everything worse. We're past the "bleak threshold" for over 10 years now.

Airbnb is inflating the real-estate bubble everywhere. Apartment building now are mass produced, tiny, and expensive, targeting investors who are only interested in Airbnb.

Uber/ifood and other transport/delivery apps are just working around labor laws, undoing centuries of progress towards worker rights and approaching slavery-like situations.

Amazon is just another monopoly, not sure why you put it beside the others, but it's one of the companies lobbying to make the world a worse place.

Then came crypto"currency", which started the "age of anything goes", where tons of money are thrown in the trashbin for the next speculative pseudo-tech bubble.

AI is just the bubble that came after crypto, little practical utility with lots of hype from billionaires who threw money at it.

After it bursts, there'll probably be another.

As far as Uber, was it better when there was both a medallion system monopoly in cities like New York and less access to cabs? Where people had to rent overpriced medallions and couldn’t make any money

Or sometimes depending on what you looked like, where you were going or where you were coming from, you couldn’t get a cab at all.

https://abcnews.go.com/GMA/race-cab-hailing-ride-black-white...

I have used Uber all over the US and in a few other countries. Most Uber drivers I talk to like the flexibility.

Half the “benefits” that people bemoan that Uber drivers don’t get shouldn’t be the responsibility of any private employer. For instance health care shouldn’t be tied to your employee anyway.

The US is a terrible example for anything, anyway.

I was talking about the civilized world.

I'm pretty good at C++.

By using a very simple technique, I've managed to write 0 bugs in it in the past 15 years.

I assume that simple technique is to not write any C++, despite being pretty good at it?

Yes, that was the joke.

I wish I lived in the same world as you.

There's basically 0 rust jobs available that aren't scam startups.

That's the main problem with vibe coding.

The whole point is having the LLM figure out what you want from vague hand-wavy descriptions instead of precise specification.

You don't need an LLM to parse a precise specification, you have a compiler for that.

It's entirely possible to have specifications somewhere between "vague hand-wavy descriptions" and source code. But it's really not my job to defend AI against all the people who want it to be completely useless, seem to need it to be so, really. I just use it, it works a lot of the time, doesn't work other times, and that's that. Results carry more weight than opinions.

> That's the main problem with vibe coding.

It's not a problem. It's in fact the core trait of vibe-codig. The primary work a developer does in vibe coding tasks is providing the necessary and sufficient context. Hence the inception of the term "context engineering". A vibe coder basically lays out requirements and constraints that drives LLMs to write code. That's the bulk of their task: they shift away from writing the low-level "how" to instead write down the high-level "what".

> The whole point is having the LLM figure out what you want from vague hand-wavy descriptions instead of precise specification.

No. The prompts are as elaborate as you want it to be. I, for example, use prompt files with the project's ubiquitous language and requirements, not to mention test suites used for acceptance tests. You can half-ass your code as much as you can half-ass your prompts.

Sounds like a compiler with extra steps.

A jinn granting wishes is the best analogy for LLMs I've seen so far.

Ecept that LLMs aren't mischievous. They're just stupid.