12,322 karma · joined April 5, 2007
http://techspot.zzzeek.org
googled it so this becomes a PSA: https://simonwillison.net/2026/Aug/25/eve-online-move-to-pyt...
so it's neither, it's their own: https://github.com/carbonengine/scheduler
so that's interesting
in this case a ratio of 196 points to 479 comments points to a very poorly received yet comment-inspiring article.
The blog post rightly points out we should get good at spotting all this but this is not the scary part, the scary part is that the audience for these ecosystems is not even humans, it's the big AI players like Gemini and ChatGPT, and those are places that a lot of people are going to get information and advice on things.
I use Gemini quite a lot and lately I've already noticed it's very quick to give me a broad spectrum vibe on some issue or topic and not good at all at backing it up with reputable sources. So I think this is potentially a very ominous development of the entire web itself becomes a giant poisoned cauldron of untrustworthy AI maliciously influencing "trustworthy" AIs.
Update: i fed this comment into Gemini and asked "what is Google doing about this?" and it produced a very long, detailed answer, leading off with tagging this as the so-called "internet ouroboros" problem. For those who don't feel like doing the same, I can distill it's answer as follows: "Yo. Chill. We got this, bro. Lol" so we're good!
Maybe a US thing
this article seems to be talking about commercial cloud managed PG services, which yes, those absolutely need to support connection pooling and of course they're going to use pgbouncer.
I guess just another area where the LLM is useful only as long as you remain in charge using your own programming experience as a guide.
I'm not sure why "you can lose your home insurance for having one of these" isn't being brought up more.
You don't need to return a boolean. You need to return an object that implements __bool__.
Get it ?
And even then, when you're dealing with objects that are special to expressions, you don't actually even need __bool__ that much
I want pay-per-crawl. I clicked the link for it a year ago, got presented with a "request access" button, I "requested access" and obviously since I'm nobody I heard absolutely nothing. Now they're touting the link again, I checked, still that same "request access" button. I have no idea if anyone even has access to this feature.
I don't care about all this other stuff, I want the AI crawlers to pay me cash. Because boy do those fuckers want to crawl me. I'll gladly double the size of my gerrit/jenkins servers to keep up with the load if these stupid bots want to pay to crawl every jenkins build artifact and every changeset source file on the server, as they really seem to want to do.
Trying to explain how the global economy and welfare of most of humanity is hugely dependent on free software production labor, without the advent of actually seeing a world where this actually happens, is just like when we try to explain something like consciousness. There is no explanation that makes sense. So predictions about new avenues of doom (like "MIT licensing was a huge mistake! we should have all been GPL!") similarly dont carry a lot of weight, because of course these predictions make perfect sense in the abstract, yet real world results don't line up at all.
Basically open source software is an emergent phenomenon, like consciousness or evolution, or perhaps even how very large language models suddenly seemed like real people. It's something that would never be predictable in its own absence, which means it will remain largely unpredictable how it will respond to ongoing changes such as "the open source authors and contributors now use programs themselves to produce more code".
People are really really tired.
Because of not just Claude, but also "the recession" "the strait of hormuz closed" "we've never recovered our economy from COVID" "everyone works from home now / the company is forcing us to all come back in" "FAANG had 10000 layoffs" "the global warming" "the <panic about XYZ>", our employers are making us work much harder, with a subtle but palpable panic in their emails, with WAY less promises of any kind of job security, companies that never had layoffs for decades are now doing them regularly, our githubs are flooded with people pointing robots at our issues to generate tepid pull requests, and at our pull requests to generate tepid reviews, and look shit is just crazy now.
So I think the whole "how would you approach this interesting problem..." thing is, for now, at least for me it feels a little bit on hold. Like oh that problem. How to scale? how to horizontally shard PostgreSQL? sure, real problems. But geez whatever we're building, it will be replaced in three months anyway. That's a hard problem you have there! I remember when I used to have problems like that, and my solutions sucked anyway and it was replaced with a node.js app two years later. Whatever advice I have, Claude is going to have 98% of it plus another 10% that I didn't even have.
This is all bad. So I think your post is possibly extremely useful. Maybe we should, for people we know and trust as humans in the real world, actually take the time and approach an issue as though we didn't have the Matrix to approximate it for us. I'm going to think about this and consider it.
yeah how do you "know" this? our kid is obsessed with wimpy kid and a few other similar series and "cynicism" nails it perfectly, is there a list? of what's known to be "cynical" and what's not?