kajman

Cities: Skylines 2 is a particularly rough pick for this concept, since it's one of very few games I need frame generation to run even passably. LLMs seem plenty capable of tweaking existing assets to make a ton of variants, but actually displaying all of those performantly is then an engineering problem.

And without many variants, things like "splotchy wall apartment building" would get old so much faster when there's several square blocks of them instead of bizarrely pristine ones.

This should be updated. It appears they've removed the regex triggered easter eggs, and it's well known that a Super Intelligence system is a combination of off the shelf LLM and hand written regex cases.

Or hand-prompted, more likely.

I was once a juror during a very vindictive two day civil trial against what was essentially a hobby business. I left with a newfound respect for binding arbitration.

My feelings are different where there's grave power imbalances like you describe, but there's very little about dealing with a large corporations that is just or dignified these days.

> And a pure native app is _always_ going to behave better than react native.

Maybe iOS is better about consistency, but I've used enough horribly made Android apps that I would not expect one that's vibe coded to behave better than a professionally made react native version.

Maybe, but what about when "Claude do this" picks WordPress for someone that doesn't know what a reverse shell is?

"AI" is relevant context here but apparently not the Jaguar Land Rover hack.

It only makes sense that fetuses which choose to be born into blue collar families in the wrong zip code are more likely to continue to make poor decisions for the rest of their lives. You just can't trust people with such a poor history of judgement. Unless they're C-Suite.

I'm glad I don't have any ~~bookie~~ prediction app accounts, because I'd now be willing to put money on an incoming settlement.

The content does not read like it's well thought out to me, but I am at least convinced it's human.

> If you'd used `slices.Contains(s, needle)`, on the other hand, it could have such a performance bug in it and you'd never know.

Perhaps you're much better at programming than I am, but I prefer these semantics in a language because I figure they're much more likely to have been optimized empirically, support vectorization, and be less buggy than another rote loop I'm trying to speed through.

For once I wish they would've taken a more technological solution to this social problem and enforced more limited CI time and disk space quotas by default. Seems like it'd be fairer and require less active policing. My read from their post was that the resolution had more of an ideological bent than being just about resources, which is certainly their community's right to have.

Are you a voting member?

> So while the following use cases are discouraged (similar to private repositories), they are likely to be tolerated in practice:

> Side projects and experiments with little resource usage > Specific tools and custom scripts that would be unlikely to find a community anyway, even if they were not LLM-generated

I really don't want to join a commons where something I make might be "tolerated in practice" based on a given moderator's vibe. Which I suppose is the message I was meant to receive from the issue that passed the vote.

I've found LLMs useful for surfacing popular recommendations. I also get the overwhelming feeling that it's all very early days still when the machine mixes together whatever was crawled into the weights with a web search or two and dumps it into a markdown blurb.

I totally agree with the above that a more polished and less obvious use of LLMs integrated back into search engines may be more useful, but will definitely be more usable.