At least the password manager I use has solid encryption. I can control where the file lives and what file permissions it has. For instance, I can keep it on a USB stick that I only insert when I need a password and then remove the stick afterwards.
I do not remotely whatsoever trust Microsoft or Windows to keep their Recall database secure and offline. Attackers will know exactly where the file is, unlike with my password manager. There's no shortage of Windows privilege escalation exploits to gain TrustedInstaller status to read any file on the system.
IMO the NYT goes too far with its copyright/trademark claims. A few months ago several small-time amateur hobbyist Wordle-clone GitHub repositories were deleted due to NYT DMCA takedowns.
Considering I read this headline as "Wordle in legal row with geography spinoff, Wordle" ... I think this is an entirely valid trademark dispute. Yes, NYT goes too far with copyright/trademark claims, but this one seems like an issue where reasonable minds could disagree.
While Higher Order Perl had a lot of neat tricks, they were quite useless in production because they would slow things down significantly with all the subcalls.
Becouse that's like functional programming work :) It is liked by Academia peoples and those that can't be bothered by implementation design.
But in reality it is how reality works: more complicated things consume execution time: a is Int.range(1..3) IS NOT THE SAME AS: "load 1 to register A" - it contains 'if' or few on every single use. Or function call(s).
We need CPU's that support such things natively (or via cooprocesor or something, with atomics and full transactions :) ) or need to accept slow code or layer like OS for "rich types" and "type safety"...
This isn't actually running DOOM. It's basically just taking DOOM "screenshots" and rendering them with the cells. It also takes 70 minutes to render a single screenshot and then 8 hours to clear the display.
Call me a pedant, but this bugs (heh) me every time someone comes out with "we ran doom on X!" when they're really just using X as a display. Same thing with the pregnancy test a few years back.
The whole "it runs doom" thing is meant to be about actually running the game engine, not getting something to display the output of another computer actually running it.
Take a look at LibreWolf. It "standardizes" all fingerprintable variables (canvas size, fonts, etc) so that you look like anybody else with a default config.
The C specification mandates that new keywords use _Keyword naming conventions to ensure backwards compatability by not overriding potentially existing identifiers in codebases. That is why the C specification has reserved identifiers that begin with an underscore and either an uppercase letter or another underscore.
Typically, a <stdkeyword.h> header is included that contain macros to provide the lowercased variants. I.E., this is how _Bool was implemented; <stdbool.h> provides the lowercased `bool` variant.
C23 is scheduled to promote bool, alignof & co. to keywords, so the concern for using _Xxx keywords is recognized by the committee. They introduce _Xxx keywords, sometimes alias them to lowercase versions with macros and let this age. Then, some time after, they switch to the "primary spelling", which is how the lowercase versions are referred to.
You can't easily lowercase _Type and _Var, so practically speaking it will take years before these features could be suitable for wide-spread adoption. Hence my original comment - given the friction, is it worth expanding the language this way at all then?
_Bool etc. came with convenience macros defined from <stdbool.h> and so on, but _Generic never did, suggesting that the underscored version was meant to stay forever that way. (Otherwise it should have been named as something like _Generic_switch and later renamed to generic_switch...) Maybe _Type and _Var are similarily intended.
As someone who is keeping Windows 10 and skipping over Windows 11, I'm wondering if my Windows 10 key will be usable to freely upgrade to Windows 12. Assuming Windows 12 is worth installing...
I do not remotely whatsoever trust Microsoft or Windows to keep their Recall database secure and offline. Attackers will know exactly where the file is, unlike with my password manager. There's no shortage of Windows privilege escalation exploits to gain TrustedInstaller status to read any file on the system.