And a whole lot of content that I frankly would have preferred not to have seen.
When you’re 12 and your parents have no idea what you’re doing, you’ll end up in very dark corners.
And a whole lot of content that I frankly would have preferred not to have seen.
When you’re 12 and your parents have no idea what you’re doing, you’ll end up in very dark corners.
Train nerds are a weird bunch.
Please never change.
The long-term goal is for Rust to overtake C in the kernel (from what I understand
Your understanding wrong. Rust is limited to some very specific niches within the kernel and will likely not spread out anytime soon.
critical code gets left untouched (a lot of the time) because no one wants to be the one that breaks shit
The entire kernel is “critical”. The entire kernel runs - kind of by definition - in kernel space. Every bug there has the potential for privilege escalation or faults - theoretically even hardware damage. So following your advice, nobody should every touch the kernel at all.
Germany has a Sovereign Tech Fund for exactly this, and while it’s not perfect, it’s one of the better uses of my tax euros.
Replacing C with Rust in the upstream kernel is akin to replacing the engine in a car while it’s running or being used every day.
That’s in no way what’s been proposed. Rust is used in a very well defined niche, nobody wants to get rid of C.
But it’s just that sentiment that got us here, you’re arguing against a non-existent threat, and thus reject the whole proposal.
And it’s a bad argument anyway. You’re only good at memory management until the first bug takes down production.
Rust isn’t a panacea and certainly has problems, but eliminating an entire class of potentially very dangerous bugs is a very good argument.
No, I’d argue you simply didn’t want to invest in the other tools.
Think about it, you probably spent hours on customizing and automating vim, and then say you’re faster in that. Well, that’s called a habit.
IDE are objectively more powerful and since you can actually see options and navigate quickly, you don’t need to memorize every obscure feature.
All the terminal editor enthusiasts are actively holding us back, because they insist everything outside vim is garbage for enterprise and kiddies.
If your tool of choice is actively hostile to new users for no reason other than “that’s how it’s always been, and thus it’s better”, well then you’re digging a moat to automate your gatekeeping.
I understand it very well. And that’s exactly why I’m writing this.
Ok, I can see you have no idea what you’re talking about.
Then say, grandmaster delusion, what purpose does vim serve, where it is actually the best tool? Writing code? Hardly, it’s way too limited and requires a ton of upfront investment and headspace. Writing config files? Hardly, because if you write these by hand, you’re living in the 90s, that’s what Ansible, Terraform etc are for.
You just don’t want to admit, that vim is nothing more than a habit. Muscle memory.
You’re using the terminal, because you’re used to it. It is not the better tool, it’s simply what you happen to know already.
People who argue with productivity because of some key bindings live in the world of the 80s. You don’t just sit there and type code 12h a day, that’s not how modern software development works.
And all those blockheads down voting me are caught up in their weird superiority complex. They are the powerful superhackers, and don’t understand that we are just highly qualified plumbers.
…so your infrastructure is outdated.
And how often does that happen in the real world?
VIM may have been a very useful tool 20 or 30 years ago, but today it’s nothing else but a tool for one’s sense of superiority. It’s the vinyl of editors.
If you have to type that much code in a terminal, your infrastructure is outdated. Simple as that.
And that’s especially true for Linux and other big projects.
I’m not a kernel or C developer by any stretch, but a few years ago fixed a small bug that caused my knockoff PS2 controllers to act super weird. Nothing serious, something like one constant and maybe 5 lines of code. Would have gladly pushed that upstream, but fuck me sideways is that a complicated process. Patches via email??? And the argument is always “but it works for us”, yeah burning witches and slavery also work for some people, doesn’t mean it’s something to continue doing.
If there isn’t a serious revamp, Linux will die a slow death or become just a corporate graveyard product like Cobol.
Of course, but most governments are allowed to mostly be sovereign.
Sweden or Australia play ball on their own, no need for a coup here.
The US tried to invade Cuba as well, and tried to kill Castro, several times. That’s ultimately why he did align with the USSR - choosing the bully that’s slightly more on your side.
That’s actually the really sad story here.
Every “experimental” regime was either toppled (Chile) or had to align with the USSR (Cuba) to survive. There was never a real attempt at democratic socialist politics without interference from superpowers.
You do consent often enough.
At least in Germany, there are at least two companies (Schufa and Experian) who will analyze your account data/money transfers to calculate a score.
Technically, this is legal because they claim to have a legitimate interest in the data and you do have to tick a checkbox.
Actually, the Pico is also an arm device, just the M0 variant which admittedly barely counts as a computer.
It’s the same crap like with blockchain.
People have no idea how sophisticated modern IT systems already are, and if you glue fancy words on solved problems, people will cheer you for being super innovative.
I did this with my sensors running in Pi picos.
There was some wonkyness with some of the electrical stuff and since I have no idea how to debug that, I just restarted them every 24 hours and at start “drained” all pins by repeatedly reading from them.
I’m reasonably sure, this setup is cursed enough to kill an electrical engineer on sight, but it kind of works good-ish enough.
I feel like there’s a very fine balance for the effort required to publish a package.
Too easy and you get npm.
Too hard and you get an empty repo.
I feel like Java is actually doing a relatively good job here. Most packages are at least documented a bit, though obviously many are outdated.