It turns out that "Women Who Code Closing - Women Who Code" actually isn't about Women that code a software called "Closing", and Women that code in general.
In fact, what they meant to write was:
The End of an Era: "Women Who Code" Closing – Women Who Code.
I know I'm gonna get downvoted for this, but punctuation matters, and sadly, it has to be said. So here I go.
This is the way. And I might add, Unix desktop. Let's not start bikeshedding between FOSS Unix distributions out of dogmatic reasons (I'm sure you didn't mean to specifically single out "Linux" here, but I wish we would stop opposing "Linux" and other Unixes like BSD, Illumos, etc).
The point is, voting with your data for software that is defending your interests, and respecting your rights.
Yeah, I find the puzzle sliding JavaScript captchas the best as a user. Cognitively better than "training neural networks to recognise protestors", and still fast enough that it doesn't feel like a forced ad. Reliability might however vary a lot between implementations.
Note: this comment is long, because it is important and the idea that "systemd is always better, no matter the situation" is absolutely dangerous for the entire FOSS ecosystem: both diversity and rationality are essential.
Systemd can get more efficient than running hundreds of poorly integrated scripts
In theory yes. In practice, systemd is a huge monolithic single-point-of-failure system, with several bottlenecks and reinventing-the-wheel galore. And openrc is a far cry from "hundreds of poorly integrated scripts".
I think it is crucial we stop having dogmatic "arguments" with argumentum ad populum or arguments of authority, or we will end up recreating a Microsoft-like environment in free software.
Let's stop trying to shoehorn popular solutions into ill suited use cases, just because they are used elsewhere with different limitations.
Systemd might make sense for most people on desktop targets (CPUs with several cores, and several GB of RAM), because convenience and comfort (which systemd excels at, let's be honest) but as we approach "embedded" targets, simpler and smaller is always better.
And no matter how much optimisation you cram into the bigger software, it will just not perform like the simpler software, especially with limited resources.
Now, I take OpenRC as an example here, because it is AFAIR the default in devuan, but it also supports runit, sinit, s6 and shepherd.
And using s6, you just can't say "systemd is flat out better in all cases", that would be simply stupid.
Straight out of uni, know the latest developments while having also studied long established standards and specifications (like POSIX, LSB, SQL, etc), full of energy, and ready to speedrun burning out any %
Senior dev:
Hasn't learned anything substantial in decades, uses outdated specs because "who got the time for that, and legacy stuff works just as well anyway", copy pastes most of their work from stack overflow, is only still employed because of their inside information knowledge and the utter absence of documentation leading to a bus factor of one, and has perfected the art of gaming the system to the point of photoshopping a sloppy IDE screen over their WoW game whenever a picture of them "working" gets taken.
Thank you very much for this post. I'm glad someone did the effort of getting some of those and presenting them from the PoV of a first time experience. I was curious.
However, I'm not sure what you meant with:
BUT when I shared it with others, people in body reported less effectiveness due to thickness of skin and under-dermal stuff, so it's better to test it if you aren't skinny as a skeleton.
At first it sounds like you say that overweight people have trouble using them (which is logical, the device needs to touch the bones), but then you go on saying that it doesn't work for underweight people? I'm confused. Could you please elaborate a little? Thanks 🙂
I had to read word by word to make sense of your drivel. At first, it seemed to be sarcasm, but reading "out their" convinced me otherwise. Lrn2English bruh.
For other readers that will find this comment: I'd have written a logical rebuttal explaining why the concentration of wealth, IP laws, predatory financial institutions, etc. make this flat out impossible; and how fair, true capitalism died under Nixon, but it would here be like casting pearls before swine.
Honestly, if the makefile is well written, I will take that any day. Good makefiles are 😙👌.
They are extremely rare, tho...
I guess the solution would be a declarative language that compiles to makefiles. So that people don't have to know the nitty gritty of writing good makefiles, and can just maintain a file of their dependencies and settings...
¹ Repudiation in SimpleX Chat will include client-server protocol from v5.7 or v5.8. Currently it is implemented but not enabled yet, as its support requires releasing the relay protocol that breaks backward compatibility.
² Post-quantum cryptography is available in beta version, as opt-in only for direct conversations. See below how it will be rolled-out further.
Some columns are marked with a yellow checkmark:
when messages are padded, but not to a fixed size.
when repudiation does not include client-server connection. In case of Cwtch it appears that the presence of cryptographic signatures compromises repudiation (deniability), but it needs to be clarified.
when 2-factor key exchange is optional (via security code verification).
when post-quantum cryptography is only added to the initial key agreement and does not protect break-in recovery.
Thanks.