OP mentioned using this to scale WordPress instances in one of the comments. So I assume that had something to do with the choice. It probably wouldn't be TOO hard to support multiple dialects of SQL in the future though.
So much that we presume in the modern cloud wasn't a given when Apache Kafka was first released in 2011.
kevstev wrote just above about Kafka being written to run on spinning disks (HDDs), while Redpanda was written to take advantage of the latest hardware (local NVMe SSDs). He has some great insights.
As well, Apache Kafka was written in Java, back in an era when you were weren't quite sure what operating system you might be running on. For example, when Azure first launched they had a Windows NT-based system called Windows Azure. Most everyone else had already decided to roll Linux. Microsoft refused to budge on Linux until 2014, and didn't release its own Azure Linux until 2020.
Once everyone decided to roll Linux, the "write once run everywhere" promise of Java was obviated. But because you were still locked into a Java Virtual Machine (JVM) your application couldn't optimize itself to the underlying hardware and operating system you were running on.
Redpanda, for example, is written in C++ on top of the Seastar framework (seastar.io). The same framework at the heart of ScyllaDB. This engine is a thread-per-core shared-nothing architecture that allows Redpanda to optimize performance for hardware utilization in ways that a Java app can only dream of. CPU utilization, memory usage, IO throughput. It's all just better performance on Redpanda.
It means that you're actually getting better utility out of the servers you deploy. Less wasted / fallow CPU cycles — so better price-performance. Faster writes. Lower p99 latencies. It's just... better.
Now, I am biased. I work at Redpanda now. But I've been a big fan of Kafka since 2015. I am still bullish on data streaming. I just think that Apache Kafka, as a Java-based platform, needs some serious rearchitecture,
Even Confluent doesn't use vanilla Kafka. They rewrote their own engine, Kora. They claim it is 10x faster. Or 30x faster. Depending on what you're measuring.
They explicitly don't have a "nostr coin" or do anything "on chain" which I applaud them for especially since the Venn Diagram of Nostr and the crypto community is basically a circle.
Very odd. This must be some kind of Ubuntu issue. Out of curiosity I tried it in Chrome, Firefox and Safari on MacOS 15.5 and saw very little CPU usage and no difference with/without the video playing. I don't have a Ubuntu Desktop handy to confirm. Looking at the video it's nothing special. Just a fairly small mp4 using a native html5 video element to play it. Really no reason this should be causing issues.
Just in case... Maybe you didn't wait long enough? I saw nothing so I came to the comments expecting a lot of others to day the animation is broken. However, it turns out it's a lot slower/longer than I thought. I saw the little bar on the left shrink to nothing and thought that was it and exited, but that's just the start. The full animation is the red circle shrinking all the way until it disappears. There is no illusion until the circle shrinks quite a bit.
Depending on the mass they may have been able to remove it manually. A colleague used to use paperclips to study the field lines, and those had very little force.
The problem is that normal MRI math tries its damnedest to avoid actually solving the right equations. Instead, with a flat enough field, you can assume linearity and just FFT the thing. They'll physically place bits of metal and magnets at various places on the big magnet to calibrate and better adjust the field to being approximately linear. A hunk of metal bigger than a shim sounds like it would mess with that.
I went through your exact same hate timeline. The CoffeeScript one was so bad that I was REALLY hesitant about TypeScript, but the whole "it's a superset of JS" thing won me over in the end.
I still hate PHP the most, and I very much mean PHP 5 when I say that, and have no idea what happened beyond that, and honestly the scars are so deep I don't care to find out.
I don't think the risks are high with this. It's not writing for you. It's just correcting your grammar. If you're 99% writing it yourself and just having it highlight grammar mistakes I wouldn't expect it to trigger an alarm....... but I haven't been in school since waaay before LLMs were viable/common. So, maybe it's worse than I think.
