This is what I took away from the reading. It's basically a shift/employee management platform. The only reason we're even discussing HIPAA is because health care industry adjacent.
If you replaced nurses with gig workers and uber for nurses with something like WeWork this would just be like every other leak we talk about on HN.
What do you think about Rust for Rustaceans? I read it and there are very niche and useful information there about Rust that I didn't see anywhere. It's a solid book but for a book about programming there are so few real code examples that it can come off dry. I just bought Rust atomic and locks and it seems exercise based, so I'm excited to finish it. The first chapter seems promising
You are right about it not being a beginner friendly book. Hence why I placed it lower in the order of books to study.
Yeah Rust atomics and locks is essential if you truly want to understand low-level concurrency. But you might have to also refer to the C++ std::atomics reference [1] to get a complete idea. It took me a while to grasp those concepts.
"Programming Rust" by Jim Blandy et al was the book that really helped me to understand why many of the design decisions behind the implementation of Rust were made.
I found it more approachable than some of the other Rust books and highly recommend it as a first Rust book.
Unfortunately, I haven't read Programming Rust. The list includes just the books I used to learn Rust. But will definitely give Blandy's book a read. Thanks for the recommendation!
The Rust Programming Language does a great job imho. It got me up to speed by reading it before bed for a month. I’d never written C/C++ before, just a lot of Python. It starts out really simply by explaining the type system and the borrow checker. Take it from there and do a couple of side projects, I’d say.
Why do people say Rust follows the tradition of C++? Rust follows very different design decisions than C++ like a different approach to backwards compatibility, it does not tack on one feature on top of another, it is memory safe etc that are very different from C++. If you are just comparing the size of language, there are other complex languages out there like D, Ada etc
> Why do people say Rust follows the tradition of C++?
They mean the domain that Rust is in.
Before Rust there was only C or C++ for real time programming. C++ was an experiment (wildly successful IMO when I left it in 2001) trying to address the shortcomings of C. It turned out that too much of everything was in C++, long compile times, a manual several inches thick, huge executables. Some experiments turned out not to be a good idea (exceptions, multiple inheritance, inheritance from concrete classes....)
Rust is a successor in that sense. It draws on the lessons of C++ and functional programming.
I hope I live long enough to see the next language in this sequence that learns form the mistakes of Rust (there are a few, and it will take some more years to find them all)
Some of C++'s warts are still available in Rust, though, such as long compile times. Additionally it encourages using a lot of dependencies, too, just like npm does.
Anyways, I dislike C++, it is too bloated and I would rather just use C.
It was no experiment at all, it was Bjarne Stroustroup way to never ever repeat his downgrade experience from Simula to BCPL, after he started working at Bell Labs and was originally going to have to write a distributed systems infrastructure in C.
Also there have been alternatives to C and C++, even if they tend to be ignored by most folks.
The one big (and IMHO most problematic) thing that Rust and C++ have in common is the desire to implement important core features via the stdlib instead of new language syntax. Also both C++ and Rust use RAII for 'garbage collection' and the 'zero-cost-abstraction promise' is the same, with the same downsides (low debug-mode runtime performance and high release-mode build times).
While I don’t disagree that there’s a similar desire regarding libraries vs syntax, Rust is also more willing to make things first class language features if there’s a benefit. Enums vs std::variant, for example.
And it's a balance act, both approaches to language design have merit.
That being said, I can't work with std::variant, and God knows I tried to like it. Rust's enums look a lot nicer by comparison, haven't had enough experience to run into potential rough edges which I'm sure are there.
For me the defining feature of C++ are its move semantics. It permeates every corner of your C++ code and affects every decision you make as a C++ developer.
Rust's defining feature is its borrow checker, which solves a similar problem as move semantics, but is more powerful and has saner defaults.
Zig doesn't promise language or stdlib stability yet, but in reality the changes are quite manageable. And it's already good enough for some high-profile real-world projects like Bun (https://bun.sh/), Tigerbeetle (https://tigerbeetle.com/) or Ghostty (https://ghostty.org/).
In the end, language stability isn't as important as it used to be, people are quite used to fixing their code when upgrading dependencies to a new major version for instance.
It remains to be seen if any of those projects will be around in a couple of years.
I haven't yet seen something that would make me have to consider Zig, regardless of my personal opinion, like other languages that have grown to become unavoidable.
An ISP is closer to the post office than a pastebin site. A pastebin site is closer to a factory that produces and ships content to all that order it, and thus responsible for what they ship.
It's unfortunate that things are the way they are, but I'm not sure there's a better option. If you give an inch, abusers will take a mile.
I think AI is well suited to this role, especially with new models being cable of learning and updating their weights as they go without needing retraining/finetuning.
They offer packages but if you're on a point release distro you'll want to build it from source.
On my Debian box, I build the podman release target in a chroot, extract the archive in /opt/, and use stow to install/uninstall the package. You'll also want the latest crun, but which I also place in stow and install with stow.
I think nginx is great if your enterprise and want to squeeze the most utility out of your boxes. The issue is there's a large disconnect between nginx and Nginx plus, and you quickly end up making cursed configs to do basic things if you're using the former. It's literally what drove me to seek out alternatives and settle on caddy years ago.
If you're US based, there's tons of data broker sites, and you can glue together the information for free as various brokers leak various bits (E.g. Some leak the address, others leak emails, others leak phone numbers). And that's by design for SEO reasons, they want you to be able to google someone with the information you have, so they can sell you the information you don't have.
Some straight up list it all, and instead of selling people's information to other people, they sell removals to the informations owner. Presumably this is a loop hole to whatever legislation made most sites have a "Do Not Sell My Info" opt out.
What you do is look up a data broker opt out guide, and that gives you a handy list of data brokers to search. E.g.
I recently revived my parents HP all in one from 2008, sporting a t5850 core duo.
It's surprising usable, but I found out that recent versions windows don't support sse4.1 (Microsoft has provided escape hatches to upgrade old hw to Win11, but requiring sse4.2 is a hard requirement now), so Windows 10 is the final version of windows this machine will get. I suspect in few years I'll probably move it to Linux, but for browsing and document editing it's a wonderfully competent machine.
Second hand from other members of the dev team, apparently Nintendo lawyers approached the lead dev at his home with a Cease and Desist. Apparently they reached an agreement, as his fork went private and the Ryujinx organization went private.
So basically they got to the dev that controlled its online presence, and pressured him into removing it and abandoning the project. Naturally this scared off the other devs. So it's dead in the sense that no one is maintaining it and it was deplatformed.
While nothing is stopping anyone from continuing the project, the community is fragmented (there's a bunch of mirrors/forks but no primary fork), and there was zero knowledge transfer - anyone picking this up has to build their experience with both the code base and switch internals from scratch.
But really, this isn't about overruling software, it's about overruling yourself.
Past self has implemented a mandate that future self get up at this time. Future self is a sleepy, lazy, point of sale that can't be trusted.
Sample size of 1. I used to "wake up" and turn off my alarm and have zero recollection of it. I got the most annoying mechanical clock and packed it in a box that I had to unpack before I could turn it off. It got louder as I removed the packaging. The prolonged activity in order to shut off the alarm is ultimately what helped me fully wake up.
If you replaced nurses with gig workers and uber for nurses with something like WeWork this would just be like every other leak we talk about on HN.
reply