It seems to be getting better though. For example... https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown
412 karma · joined May 9, 2023
It seems to be getting better though. For example... https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown
Yep. As a developer, running a pihole, I don't see any ads and I wouldn't click even if I did.
I thought the tl;dr; of the article was going to be along the lines of "if you're selling a "developer tool", don't bother buying ads because "developers" (i.e. your customers) are likely going to lengths to not see these ads in the first place.
The premise that one of the myriad of other tools that already exist to get a reminder to connect with someone you care about are somehow so insufficient, and that if only I had this new CRM app for personal relationships that I'd finally be able to cultivate those relationships like I've always wanted, is just so preposterous sounding to me that I felt I had to comment.
Wait... you didn't get the memo? They did, and renamed the language in the process... it's called Rust. ;)
My peanut gallery observation is that a very bright person named Andrew set out on a journey of hard work to come up with a new language. Along the way he (and others) solved many tough ancillary problems related to the toolchain of this new language and how it should provide a useful path for interoperability and migration from code written in other languages.
The toolchain innovations were noticed, embraced, and leveraged by users of other languages as it made their lives easier in contexts where they weren't even using the Zig language.
Now, for Andrew to make even more innovative progress on his endeavor, he needs to undo some of the toolchain innovation and remove complexity that was initially used to bootstrap his endeavor. Removing complexity (from language) is one of the admired traits of this bright person, and here they are applying that good trait again to move the whole project forward.
But 'lo! Other users of the toolchain innovation will be affected... some would say they even appear "entitled" to these innovations... as if their collective need somehow outweighs Andrew's right to direct his energies to his project in the way he decides.
This whole thing smells like a story I read once... I think it was called "The Fountainhead".
Until we figure out a nice metric for "removing complexity" and then rewarding for it, it's not likely to change, IMO.
> "the very existence of this discussion validates the need for this book."
Or it could also mean that some folks involved in this discussion haven't yet read the chapter[1] in "The Book" that explains when to panic and when not to[2]?[1] https://doc.rust-lang.org/stable/book/ch09-00-error-handling... [2] https://doc.rust-lang.org/stable/book/ch09-03-to-panic-or-no...
I claim this is far worse than panic in this case... you've now introduced a code path variant that folks above think is "legitimate" or caused by some input or something in the environment that could be changed to make it go away... but that's not the case here... the only thing that can be fixed is the code in question to not be in this region if the array length is 2 or less. It's a plain old "bug" and the only cure (other than more cowbell) is to modify source and recompile.
e.g. https://www.lurklurk.org/effective-rust/panic.html
"Another sensible use of panic!, even in library code, is in situations where it's very rare to encounter errors, and you don't want users to have to litter their code with .unwrap() calls."
The litmus test for panic! vs. Result<T,E> is not rarity of occurrence, it's whether the condition represents a programming bug or a recoverable error. A good treatise on this topic here: https://joeduffyblog.com/2016/02/07/the-error-model/#bugs-ar...Except for Rust... it's awesome. ;)
...and Generative AI... put that in all the things, now.
(More seriously, it's good to be reminded of Brooks' work.)
I looked for the author's (whoever they are) proposed solution and it's this:
"This is because many of the FFI bugs surveyed are fundamentally cross-language issues. Instead, we propose that both C and Rust must conform to a shared, formally-based domain-specific language, which provides a safe-by-construction abstraction over the FFI boundary."
Such a thing is a "new thing", and isn't going to retroactively apply to the legacy C code written before this new thing... so how does that help?
(Full disclosure: I'm a professional programmer who has written in C, C++, C# for many years, and now I choose to write new things in Rust.)
I use a pi-hole and uBlock Origin, but am always up to learn more...
Ugh. Now I need to decide if ChatGPT hallucinated something in this summary, or if its otherwise factual.
I generally liked mailing lists back in the day when people took the time to craft very specific questions and responded with succinct answers. The results seemed more easily searchable to find relevant threads, which I would feel good about reading in detail, or skipping entirely.
I dunno... maybe there are just way more people asking questions or participating nowadays (regardless of whether it's in a forum, Discord, or Github), so the volume of information is naturally way up, or maybe it's our cultural shift to "more of everything in less time" (so people aren't averse to searching first and posting after not finding vs. asking something previously answered), but the end result for me is a feeling of trying to find the interesting conversations in a party held in a packed stadium vs. a party held in someone's living room.
But correlation does not imply causation, right? I don't understand how it follows from noting our incarceration rate being higher than another place with less crime, and then reaching the seeming conclusion that the answer, therefore, is to stop putting people in jail.
I would have loved to read mention of "testing" or "regression tests" in the author's summary of learnings. "Be careful" and "monitor bandwidth" don't really resonate with me as a sign the author gets it yet.