DBeaver requires Java, supports more RDBMSs, supports plug-ins, supports ER diagrams, but is also a project split into a community/enterprise model so some features are just never going to be implemented or improved upon without you paying an annual fee.

HeidiSQL is written in Delphi, supports the major RDBMSs (except Oracle), and is more focused on being a query analyzer than anything else. There is no edition split or paid model, so you're more likely to see new features in the free edition.

IMX, HeidiSQL is faster. It loads quickly and performs better, though I will say that my experience with both is about 10 years old at this point. From my memory, the DBeaver interface has always felt clunky in that way unique to Java applications, and many of the features in DBeaver are things I never wanted or needed. At the time, HeidiSQL was Windows-exclusive, with Linux support only about a year or two old at this point. My opinion 10 years back was that I would use HeidiSQL when I could and DBeaver if I had to.

It just takes that long to get a fab up and running.

Like it's not a case where you just yank out a CPU as you like as though it were a spindle in a RAID-6 array. Especially if there's only one CPU. The state machine can't maintain state if the only component that tracks and maintains state goes missing.

Now try patching glibc like that. Not only does almost every thread have it in memory, several of them will have it in process, and some of them will have it swapped to disk while the thread sleeps. You're going to quickly decide that you actually just want a little bit of downtime or else you want to stand up a redundant system. There's a reason that some live patching systems explicitly exclude glibc and similar libraries.

This is the "who killed Hannibal" meme. If Padilla and Warner didn't know about this, then they're incompetent themselves. Especially because they reported on it last year:

https://www.padilla.senate.gov/newsroom/news-coverage/cnn-tr...

Why did you forget this happened, Padilla?

First, you might not reload everything in memory, so it will be patched on disk but not in process.

Second, you have not tested that the system can boot to a functional system. Say you have done live patching for 5 years and never rebooted, and then you have a power loss or hardware failure/upgrade that takes the system down. When you try to bring it back up, it doesn't work. Which configuration change in the past 5 years caused that? Which backup do you use?

And, yeah, everything is hot swappable on VAX. Those machines also cost 6+ figures, and often require a service contract that includes a permanent on site tech.

That's always been one of the problems, though. Writing code for class is much less stressful than writing code that other people will rely on.

Obviously, a better search engine that also doesn't display ads is better. But is it $20/month better? When it's also got daily usage limits? And they're almost certain to start injecting ads as soon as they possibly can without alienating people?

Really, though, if you want someone to blame, Instructure is not a particularly compelling target. Let's review:

1. Iran is intentionally targeting infrastructure due to a war started by the current administration.

2. China is actively seeking corporate secrets to steal and commercialize for themselves, spurred by extreme protectionism and retaliatory tariffs.

3. North Korea is doing anything they can -- including just taking a remote job by proxy -- in order to extract any money.

4. And Russia is working with and aiding all of them, after everything else going on has forced the embargo to break.

5. All of this while completely alienating every single one of the United States' allies.

6. Meanwhile, the American DHS is currently shut down.

7. And this is after Trump cut funding and personnel for CISA severely enough they've had to end the contract with MS-ISAC, meaning all state and local entities can only remain in the organization if they foot the bill for it directly and CISA and other agencies responsible for cybersecurity are more thinly staffed than they have been in decades.

In short, the current administration systematically disassembled all the protections we have built over the last 100 years, and then placed infrastructure -- schools, in this case, but also power companies, water treatment facilities, communications companies, local governments, hospitals, food producers -- directly on the front lines of the modern geopolitical conflict.

That vast ocean that has kept us safe historically is a poor moat in the modern era.

How do I use DNS on my home network to set up my home router? It's the same problem as TLS certificates on web interfaces for infrastructure.

And the commercial solution is going to be "pay us a subscription fee so your home device can get an Internet management interface on top of all the egregious data collection".

This is a big part of it. Apart from extra addresses, it offers remarkably little benefit in terms of networking features from an operational management perspective. It sounds like it should be better when you look at the features, but, in actual operation the features don't really offer that much.

Further, there's the general problem that for some reason the network equipment manufacturers seem to think that because you don't frequently need NAT that now you don't need to have a stateful firewall just always on by default on a network edge device.

Plus the general confusion among tech neophytes that NAT itself is offering actual security features, so that a stateful firewall is a downgrade. This is such a fundamental misunderstanding that you can't even communicate with a person that believes it to be the case. I fear that this confusion will remain with us for decades. I'm sure me even mentioning it will spawn a whole thread of people vehemently disagreeing, because there is always at least one.

This is coupled with the fact that the addresses are just ugly. Like, I'm sorry, but unless you're exactly an electrical engineer, the IPv6 addressing scheme is difficult to remember. IPv4 has the same problem -- the magic numbers are only easy to remember if you have memorized the binary values, too -- but it's really only a handful of things to remember in comparison. Hex values are just not as easy to read or remember compared to decimal numbers. So even though IPv6 isn't harder to use, it feels like it's much harder to use.

No, but commercial trucks use diesel, which carries about 25% higher taxes per gallon. And vehicle registration on semi-trailer trucks is significantly higher as well. They pay, on average, between $25,000 and $30,000 in taxes and fees each year.

> Turns out markets are pretty good when you leave them alone.

No, they aren't. They're ridiculously bad when you leave them alone because someone captures the market, ramps up anti-competitive practices, and immediately begins rent-seeking as hard as possible.

Free markets are pretty good at finding good prices. Markets that are left alone do not remain free. That lauded "self-interest" encourages businesses that have reached nearly 100% market share to increase profit in other ways.

Worse, the owners of those fields are often foreign companies. That means they use tremendous amounts of water in one of the driest regions on earth, in the middle of a multiple decade drought, and the wealth these farms generate disappears overseas.

Because I would call a situation where the development team fails to appreciate the severity of a security vulnerability and has an established procedure that requires the researcher and not the kernel team to communicate with downstream users is already a major failure of process. Security is not just patching the vulnerability, and it seems that the Linux kernel developers or the Linux kernel security team does not understand that.

This is the result of that failure.

If this were any other software, we'd be here with pitchforks and torches. The researcher gave the developers timed disclosure, and even waited until after the developers had patched the issue. And... it's still a problem.