Yes, I agree completely, but we don’t have a bunch of Assembly diehards working on Linux, so the parallel - while accurate - feels out of scope.
Ultimately, it comes down to thoughtful transitions over a reasonable period of time.
Yes, I agree completely, but we don’t have a bunch of Assembly diehards working on Linux, so the parallel - while accurate - feels out of scope.
Ultimately, it comes down to thoughtful transitions over a reasonable period of time.
I still understand the argument of the C greybeard to Rust knowledge gap though. Objectivity, it’s hard to argue for a spidey sense that took years or decades to develop vs a deterministic and strict compiler, but developer (and reviewer) experience often seems to be rooted in personal comfort* more than in language features.
That said, we all have to deal with transitions and learning consistently leads to better outcomes. The argument is sound, but the pragmatic dynamics may take some time.
*”personal comfort“ doesn’t mean the language or tools are somehow objectively comfortable, but that people feel good, confident, productive, and happy working with them. Just yesterday I was thinking that I like the Gir “is hard” - it stimulates my brain on a daily basis. Different people get that in different ways.
We really all need to get along and accept each others’ opinions. Even if some people are completely wrong and think mutable by default it OK. Hehe.
A Project Manager just earned their wings.
Thanks, I was confused about why the helix editor might need screen sharing. Haha.
This is a dangerous metaphor. Remove the old wall and it turns out the new beautiful wall was leaning against and supported by it.
I get what you mean, it’s just that the metaphor could support both perspectives.
We know kids can take parents’ cards, right? And that people can look younger than they are? Never mind privacy concerns, the best-case scenario doesn’t look good.
I came here to laugh, not to cry!
I’d say I feel seen, but it’s really dark in here.
My take on a summary: like C/C++, Rust can be relevant in a variety of use-cases and one could conceivably build a long-term career on it, while adjusting to market/technology interests.
Seems like a reasonable prediction?
This is super interesting. I’ll admit I wasn’t even aware of this effort. Even real-time usage of Windows relies on a parallel kernel.
This sounds like it’ll create a lot of cool opportunities and reduce friction.
I’d say it’s a lot more convenient to write bad C than bad Rust. To put it another way, Rust shifts frustration left and can be disheartening for some people.