Recently, I’ve been working with Quarkus[1], the quarkus-qute[2] (a type-safe templating engine), and htmx. I found the experience quite positive. Quarkus offers lightning-fast compilation with a hot-reloading Maven wrapper (mvnw), making development seamless. Picking up qute was straightforward, and combining it with htmx, especially with qute’s #fragment support for htmx, felt like a natural fit.
Base on numbers you put, you would need to have stable 50-100GB/s speed to your disc system to just read 3TB data in 40-60sec. Would you mind sharing your setup?
Last year I built a balcony watering system using an 8x ESP32 relay system from Lilygo, paired with mini submersible pumps. To monitor plant health, I integrated MiFlora sensors over BLE. Managing minimum soil moisture and pump duration has been 'configured' by hosting a configuration files on Pastebin.
This year, I'm taking it a step further by developing a management front-end. Instead of the hacker GUI using Pastebin, I'm implementing an extra M5 Atom running MicroPython with a web GUI. This interface allows me to configure the sensors, visualize sensor data with charts, and send notifications via NTFY to my phone.
Apologies, I didn't mean to imply DCEVM went poof, just that I was sad it didn't make it into OpenJDK so one need not do JDK silliness between the production one and the "debugging one" since my experience is that's an absolutely stellar way to produce Heisenbugs
And I'll be straight: Graal scares me 'cause Oracle but I just checked and it looks to the casual observer that it's straight-up GPLv2 now so maybe my fears need revisiting: https://github.com/oracle/graal/blob/vm-23.1.0/LICENSE
Java continues to get immense real-world usage, as it has for decades, so it will continue to make headlines. Meanwhile, each trendy lang will make headlines for a few years as 4 startups gush about it before they move to the next trendy lang.
Waiting on the whole async dead-end to come to terms to cheap threads here. It's going to take a long time, but let's not kid ourselves: the TCO-driven accountants hold the roots of true power.
I can test it. What would be the advantage if I use it in my tool instead of Ubuntu? At the end of the day with Kubernetes I don't think it makes much difference which OS you use. I picked Ubuntu because it's standard and servers with this image build very quickly with Hetzner Cloud.
CoreOS (and its spiritual successor Flatcar) are immutable, which gravely limits the silliness that can be done to them post-launch. We use now use Bottlerocket since we're on EKS, but it's even more locked down since to even get an interactive shell is some major hoopjumpery. I believe Talos goes even further and is completely devoid of a shell
So, yes, it absolutely matters which OS you use, of course depending on your threat model and tolerance for "no, you don't get to ssh onto a Node and do whateverthehell you want"
[1] https://quarkus.io/
[2] https://quarkus.io/guides/qute
reply