HN user

Zagitta

347 karma
Posts7
Comments63
View on HN
[dead] 11 months ago

Calling it slop is generous, it's straight up hallucinations

As someone who has a garmin watch and switched from android to iOS I can tell you it's exactly as crippled as the article spells out. So if anything garmin has a healthy smartwatch business in spite of apple trying their hardest to choke competition.

Maybe Rust needs another type of reference that's exclusive write only? Right now there's RO (&T) and exclusive RW (&mut T) but WO is missing.

Having a WO reference would allow these read_buf APIs to express they only write and never read so the uninitialized memory is safe to pass directly.

Rewriting Rust 2 years ago

And in a similar vein have they audited the runtimes of all the languages they use? Because those a dependencies too and in many ways even more critical than libraries.

It seems like a really strange choice to me that they made the arm and riscv cores mutually exclusive in each core complex since this just wastes die space on the core you're not using which in turn drives up the cost.

I feel like it would've been preferable if they either went all in on riscv or at least made it so all 4 cores could be used at the same time.

But if I were to guess the performance of the riscv cores probably doesn't match the ARM cores so they weren't confident enough in shipping a pure riscv SoC like espressif does.

Any other guesses as to why they might've gone this route?

I think you missed the point of Jon's talk, it was in large to highlight some deficiencies that currently exist in the language but are actively being worked on.

As he mentioned the current situation with return position impl trait + 'a was surprising even to some of the core rustc developers so it's not like they intended for it to be like that.

The cat is already out of the bag.

There's no meaningful way to limit access to any of this when it's purely software based and the hardware required to run it are commodities.

It's nothing like chemical weapons were the reagents can be controlled as they're hard to come by or synthesise in a amateur lab.

Was Rust Worth It? 3 years ago

"Programming in Rust is like being in an emotionally abusive relationship. Rust screams at you all day, every day, often about things that you would have considered perfectly normal in another life. Eventually, you get used to the tantrums. They become routine. You learn to walk the tightrope to avoid triggering the compiler’s temper. And just like in real life, those behavior changes stick with you forever."

This is a pretty negative and unfortunate take on rust that I cannot recognize after having spent the past 2 years professionally writing backend rust. I did write c++ before that so it's likely that it takes some experience with the pain of an unhelpful (and in some cases downright hostile) to fully understand and appreciate the so called "yelling" rust does.

From my perspective every lifetime complaint the compiler has is a deeply appreciated hint that not only saves you countless hours of debugging down the line but also makes me feel confident/safe in the code which you never could achieve in a c++ codebase without making defensive copies everywhere.

Being able to lend/borrow data without fear truely is rust's greatest strength and something people coming from GC languages have a hard time appreciating.