mumblingdrunk

4 ms·

1. 1.▲
   by mumblingdrunk 2y ago

   All CPUs commit in order and except precisely, because most other options are insane, or would drive you to it. However: single thread commit order =/= observability order. Observability order of memory operations --- which are the on
2. 2.▲
   by mumblingdrunk 3y ago

   This is why I switched to Helix. The configuration is practically non-existent, and it has default configs for all the language servers I could ever want to interact with. I just put the language server binary in my path and I'm read
3. 3.▲
   by mumblingdrunk 3y ago

   I never got the impression that the developers had an attitude. The discussion I've seen has been mostly people making demands or saying Helix will fail if it doesn't support AI tool integration right now, but none of the devs ar
4. 4.▲
   by mumblingdrunk 3y ago

   > Many are allergic to basic scripting, don't bother to learn how their tools work, and have an elitist attitude towards other design responsibilities (ex. layout, verification). In my very limited experience, most people don't
5. 5.▲
   by mumblingdrunk 3y ago

   This is just true for a whole lot of the industry tooling. Xilinx Vivado is a bloated piece of crap that'll crash all the time unless you have half a terabyte of RAM. Same goes for lots of other EE-tooling in general. The L and B in
6. 6.▲
   by mumblingdrunk 3y ago

   This reminds me of an article I read a while ago https://alastairreid.github.io/mrs-at-scale/ MRSs would enable much more of the formal verification parts to be generated.
7. 7.▲
   by mumblingdrunk 3y ago

   I can also highly recommend a visit to The National Museum of Computing. https://www.tnmoc.org/ While you're there, take a stroll around Bletchley Park as well. Last time I checked, you get a discount when visiting bo
8. 8.▲
   by mumblingdrunk 4y ago

   I'm not fighting your claim that the borrow checker has perfectly reasonable situations it can't deal with. That's why 'unsafe' exists. I've already said that. You're adding other claims and statements tha
9. 9.▲
   by mumblingdrunk 4y ago

   It seems you are slightly misunderstanding the point of 'unsafe' as a concept. And no, memory safety is a huge deal, it is just that the borrow checker cannot verify the soundness of certain code, meaning you have to provide the
10. 10.▲
    by mumblingdrunk 4y ago

    You don't have access to the C standard library in the Linux kernel either, so what is your point? Ime., the core library of Rust is much nicer to work with than the absolute bare bones landscape that is C when compiled with -nostd.