I could also say the same, including the Wayland origin story. I'm pretty new to Niri — I only started playing with it about a month ago — but it's just absolutely that little bit more than Sway I didn't know I needed.
Completely agreed. My Rust origin story wasn't about memory safety, fearless concurrency, a modern type system, or anything else like that. Not that I didn't care about those things — I did — but none of them were what convinced me to start learning Rust.
What did convince me was being able to prototype things for the C project I was working on while having access to a standard library that included basic data structures, synchronisation primitives, and I/O handling in a way that used best practices from recent decades. Everything else was just a bonus that I got to learn and use as I went.
Truth be told, I wouldn't mind crowdfunding an alternate stdlib for C for that reason. Everyone has a wishlist of patterns discovered after K&R bestowed upon us System V, that mesh perfectly well with C's philosophy and very minimal environments, and make modern programming much easier when you're dealing with lots of dependencies. (e.g. bounded strings/small strings, arena allocation, error chaining/coalescing, etc..).
An old, old Internet protocol that was used to get information on a user, and could be used by users to post updates from their .plan files. Essentially plaintext social media for people with Internet connections in the 80s and (early-ish) 90s.
Reimplementing it (well, the CLI program, `finger`) also happens to be the final exercise of Haskell Programming from First Principles, after 1200 pages of glorious buildup from the lambda calculus forward, in case that sells anyone on trying it ;)
I had that "oh crap, I'm old" moment when my initial reaction was "what? You've never heard of finger?!" and then I remembered I last used it in the late 90s.
I'm glad your reaction was to assist the young folks. :)
Expensify was a pretty well known case of this several years ago — their marketing was all about their advanced scanning technology, and it turned out they were using Mechanical Turk in many cases with little concern for PII (or corporate security) concerns.
(I have no idea if this is still the case, for the record.)
It's not a global toggle, but Asus definitely has options to make things more stock-Androidy — you can basically turn the Settings app back into something resembling the stock version, and a bunch of their other UI enhancements and changes are also optional.
A long time Android user wouldn't have mistaken my Zenfone 9 for a Pixel at any more than a cursory glance, but you can get it pretty close, particularly in terms of feel.
Agreed! I have a 2021 CX-5, and it's not just the infotainment controls (which are great, and work really well with Android Auto), but also just having real buttons — some with indicator lights, even — for all the heating/cooling/demisting controls.
I've rented several other cars in the last couple of years that have been touchscreen only (or, at the very least, very heavily biased towards touchscreens), and the amount of extra time needed to orient where you're pressing is honestly kind of terrifying when you need to, say, demist a windscreen quickly.
The worst I've come across for this was taking the MG4 for a test drive. The whole thing felt like it consisted of programmer art (mismatched, inconsistent, ugly etc). I quickly found the windscreen misting up on a cold evening - and had to stop to figure out enough of the interface to find the correct button.
Same. I gradually learned Rust while I was working in a job where I wrote C on a day-to-day basis, and after a while I realised that Rust was making me a better C developer by forcing me to think more systematically about ownership and lifetimes than I really had to that point. It significantly changed how I designed and structured my code, even in other languages.
Not to say I couldn't have gotten the same education from another language, but something about Rust clicked for me that others didn't.
reply