Congrats for knowing what's important to you (time and peace of mind, from what I read), and acting on it.
I work as a consultant, but for the same reasons: I choose to work only a few days a week, take the salary loss, and spend more time with my young kids. A time will come where I'll start working more, which will also unlock more meaningful work – but for now that's a choice I'm happy to make.
As noted by the other investigating organization (La Quadrature du Net), the problem is worse than just the question of the algorithm implementation.
The problem is that the CNAF deliberately targets small unintentional errors rather than large-scale intentional fraud.
Why that? Because fraud is harder to detect and to prove (you have to provide evidence it was intentional).
So smaller and poorer families are disproportionately affected by the controls, because the algorithm was designed to do so. No computational adjustment can fix that: it is the initial intent that is broken.
Kazuaki Morita was a programmer on Mario Bros., Zelda NES, Zelda SNES, Zelda Game Boy, Zelda 64, where he did the bosses and fishing game; among many others.
He was often assigned the most challenging programming tasks. His coding style is so specific that it even shows in disassembled or decompiled code ("Ha, this file is classic Morita").
I did this with every first committer to https://github.com/zladx/LADX-Disassembly : giving commit rights immediately (so that they can merge their first PR themselves).
I did wonders to foster a community of contributors, and get more patches coming. The CI ensures nothing breaks, and there never was any trust incident.
Author here! Most of the engine documentation was figured out by many romhackers over the years; I merely started the efforts to write a comprehensive overview.
If you're interested in projects taking advantage of this knowledge, the Daid's LADX Randomizer [0] is awesome. It includes a ton of assembly tweaks that makes the engine more flexible, and add many options to the game.
And Link’s Awakening Redux [1] is a good example of life-improvement game tweaks made using the disassembly.
To find someone on Mastodon, I would either enter their nickname in the search bar (no need for the domain, it will search on all instances) – or simply click on their profile on a post I like. Just like a centralized network. This tool just exists to do this automatically and in bulk.
It seems to me that finding someone on a federation is as easy as on centralized systems. Do you have a use case in mind where centralization makes it easier to find someone?
I used Scalingo for Rails apps a while ago, and was quite impressed by the quality of the platform. Very Heroku-like. Maybe not as polished, but still doing the PaaS job pretty well (git push, and you're done).
I was expecting someone to post a comment along the lines of "Pixelmator is great for picture editing on macOS"; it is one of the best Mac editors.
But I'm also delighted to see your username pop up :) I used quite a few of your wallpapers back in 2002, when I was making desktop customization packs for Windows XP, and I have fond memories of them.
Indeed – although I guess WSL made unix tools slightly easier to use nowadays.
But even without executing the Makefile, simply reading it can tell new developers which language-specific command needs to be run to build the project (and then the command can be copy-pasted and run manually).
I like nothing more than dropping into a new project, and, rather than figuring out the commands to make it run, see that it has a Makefile with a handful of targets for common tasks.
To be fair, they probably ship one of the best and most optimized Electron app out there.
I still don’t like Electron, but Discord is doing a good job with it. Even their React-Native mobile apps feel decently snappy (where usually large React-Native apps are buggy and slow as fuck).
IMHO, Signal main advantage is that you can sell it to your parents and friends like "WhatsApp, but safe".
It tries to have feature-parity to WhatsApp; looks the same, works the same. All this while researching innovations on cryptography that doesn't compromise user experience too much.
In my experience, doing exactly what WhatsApp does (but safer) makes it an easy sell to people around me.
Tl;dr: CSS conical gradients, overflow detector in the DevTools, and Webrender for macOS and older Windows.
I was wondering why Firefox felt speedier than usual ; turns out the combination of the new Warp JS optimiser and Webrender does wonders on my MacBook.
Nicholas Nethercote is, of course, the author of the "How to speed up the Rust compiler" series of articles [1], which I found fascinating. He spent quite some time at Mozilla optimizing rustc internals.
Kudos for his work, and for making Rust compilation faster for all of us.
It seems Mobilizon invested a great deal in the usability of this tool.
(Not specifically the visual design, but the ease of use and the matching of user needs).
I've seen projects advertising decentralization as the main selling point. Mobilizon seems to also push strong on the user experience, and I'm glad they do.
I work as a consultant, but for the same reasons: I choose to work only a few days a week, take the salary loss, and spend more time with my young kids. A time will come where I'll start working more, which will also unlock more meaningful work – but for now that's a choice I'm happy to make.