relistan

Are you in middle school?

Yep a bunch of people who often exhibit swarm behavior.

Sure, but you cannot deny the hypocritical swarm behavior, which is the point.

Hacker News: “It’s unfair the burden put on maintainers of the core pillars of open source software. Show some respect for the maintainers, and do your best to contribute.”

… little changes …

Also Hacker News: “I have the right to tell you how to manage the project that you created and have maintained for 30+ years, because I feel very self-righteous about AI and code quality!”

This is now the word

They did say "everything I can find" which, while not citing references, you would also have found it you tried to Google this at all. Here's one

https://www.nytimes.com/2026/05/24/business/what-is-naphtha....

here's another one:

https://www.irishtimes.com/world/asia-pacific/2026/05/19/ple...

It's wider than Japan, it's in other countries in Asia. It's directly tied to the war and the closure of the Strait of Hormuz. But it's pretty clear you have your own axe to grind.

Having built two production, scaled evented systems over the last decade, I don’t see the need for this. Properly designed events flatten to a table schema in a regular DB quite easily. Tools like Trino/Presto and therefore Athena, let you deep query on a JSON field, as well (e.g. against a Parquet-based event store on block storage), so if you use a standard envelope, the bodies are all still available without having to provide the schema for every event. This works to quite huge amounts of data given that you do rollups and/or snapshots.

I am a Go dev, too. I consider Go my main language. The BEAM has a very, very similar architecture to the M:N scheduler in Go. Goroutines are not dissimilar to BEAM processes. You can similarly run thousands of processes on the BEAM. But Go does not have a real Phoenix equivalent and there are reasons to use Elixir and BEAM, especially on the web side, including some of what I already mentioned above.

At least they can patch all of them to fix it at once. 16 year old new drivers are harder to patch.

Elixir and Phoenix is a better production platform than Django.. I’m not throwing shade on Django, many production systems use it happily. I’m saying that Phoenix/Elixir is better, partly because of the BEAM and OTP and partly because of the language and the framework. Real concurrency. Better performance. Far more robust in production. The language is pre-compiled, and while not statically typed, that alone provides one more safety layer. It’s functional, which avoids a lot of the ugly patterns in both Rails and Django. It has a built-in fast and reliable KV store. It has distribution between the nodes if you want it (e.g. for a distributed cache). It enables you to debug with a remote shell connected live to the running system. There’s a lot more than I can add here.

Contrast that with my personal experience of items from the UK (specifically the UK, my experience is different elsewhere) where “untested” almost always means “I tested it and I know it’s broken but I want to try to get a better price anyway”. Especially when testing would involve plugging it in with the adapter it comes with and seeing that it doesn’t light up, for example.

And, thank you for that! Still my favorite site on the internet.

I found a similar (though much smaller! 1GB) Kingston drive from about 2008 that had been in storage since I moved overseas. 14 years later it still had all the data on it.

It’s not clear to me from this, but I hope that the “removability” component of this means the end of “disposable” vapes with a fixed lithium battery installed. I can’t even count the number of these I’ve seen littering the roadside. Ideally this raises the cost of that business model enough to also eliminate some vendors from that product category (“disposable” vapes), which is primarily aimed at/used by children anyway.

While some things are doing great, there's a not insignificant amount of inertia in government for the last decade. This is actively being discussed in the Irish press. And Ireland has a long history of cronyism. I suspected (author clarified below) that is what was leading to the cynicism in the original post.

Alternatively, it's successful and is expanded to support more artists in the future. Cynicism with governance not unjustified in Ireland, but here we are looking at some actual progress.

These things work well on the extremely limited task impetus that we give them. Even if we sidestep the question of whether or not LLMs are actually on the path to AGI, Imagine instead the amount of computing and electrical power required with current computing methods and hardware in order to respond to and process all the input handled by a person at every moment of the day. Somewhere in between current inputs and handling the full load of inputs the brain handles may lie “AGI” but it’s not clear there is anything like that on the near horizon, if only because of computing power constraints.

Way back, Perl got off the ground really because, in contrast to the C compilers of the era, code written on one Unix ran on the others, usually unmodified. In my first jobs, where we had heterogeneous mixes of commercial Unixes, this was unbeatable. It also wrote like higher level shell, which made it easy to learn for systems people, who really were the only ones that cared about running things on multiple platforms most of the time anyway.

As things became more homogeneous, and furthermore as other languages also could do that “one weird trick” of cross platform support, the shortcomings of both Perl and its community came to the fore.

My guess is that you're letting the context get polluted with all the stuff it's reading in your repo. Try using subagents to keep the top level context clean. It only starts to forget rules (mostly) when the context is too full of other stuff and the amount taken up by the rules is small.

I actually had Claude and Gemini both do it and revise each other's work to get to the final doc. Worked surprisingly well.

To a certain extent you are probably still not using it optimally if you are still doing that much work to clean it up. We, for example, asked the LLM to analyze the codebase for the common patterns we use and to write a document for AI agents to do better work on the codebase. I edited it and had it take a couple of passes. We then provide that doc as part of the requirements we feed to it. That made a big difference. We wrote specific instructions on how to structure tests, where to find common utilities, etc. We wrote pre-commit hooks to help double check its work. Every time we see something it’s doing that it shouldn’t, it goes in the instructions. Now it mostly does 85-90% quality work. Yes it requires human review and some small changes. Not sure how the thing works that it built? Before reviewing the code, have it draw a Mermaid sequence diagram.

We found it mostly starts to abandon instructions when the context gets too polluted. Subagents really help address that by not loading the top context with the content of all your files.

Another tip: give it feedback as PR comments and have it read them with the gh CLI. This is faster than hand editing the code yourself a lot of times. While it cleans up its own work you can be doing something else.

As AI tools become more dominant, businesses are going to want their documents to be fully read by their AI in whatever format they are in. I wouldn’t be surprised to see a fight over all of this brewing in the next couple of years.

All of this is a mess. But it should never even have been possible for it to fall to a single developer to screw up and commit a key like that.

If there were anything like proper processes in place, controls would have made that very difficult.

Then there are the weird issues about why obvious close ties to xAI here....

Try googling for the solution you would have used here and report back ;)

Author here. Nearly 30 years as a UNIX sysadmin. Yes, I know about POSIX ipc. It's not well supported on the BEAM, and anyway would violate most of what makes Erlang/Elixir apps so robust. Not really an option worth even considering.

Author here. I know all about POSIX IPC (nearly 30 years UNIX admin here). It's not supported on the BEAM in a sensible way. Not to mention that if it were implemented, it would almost certainly violate the sensible failure domain management of the Erlang/BEAM ecosystem and OTP.

As for GRPC: we don't use it anywhere else. So we'd have needed all of the tooling on two stacks, calling patterns without native error handling that we'd have had to implement, and instead we have a thin wrapper that allows the Elixir app to call Go like native Elixir code. GRPC would have been worse in almost every way.

Bad for everyone, but not surprising at this point.

These brands face massive competition from Chinese no-brand electronics on one end, and Apple, Sonos, and many others at the other end.

Basically any time a market changes drastically you see older players consolidate. Too often that leads to one big collapse of the consolidated entity. We’ll see what happens in time.

:shrug: who knows

Seems hard to believe that no one would have bought this brand at least.