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

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.