"any value, several, or no value". Any in JS is literally that tho, sans "Never" iirc

Edit: oops, I was wrong. Any MAY be a never. Typescript allows it

Those are called set and you want to be able to operate on those set secretly. Here is an old paper that could point out to many more stuff

https://www.cs.cmu.edu/~leak/papers/set-tech-full.pdf

I think canva was in need of desktop program and rather than developing one from scratch, they straight up buy affinity and slap their main selling point of the web version of canva (AI art)

I'll propose the opposite. Aesthetic is one of the most deciding factors IMHO, the underlying hardware could theoretically be reverse engineered. And beside, how often someone change their keyboard layout.

A shame that people misusing analytic and telemetry. They do provide very useful information for developer when shit goes wrong. But the same data is also very valuable for profiling the person using the program

Hot damn, that's a ton of unrelated project to them and they still do it. Good for them

Hmmm, that article seems to suggest one device is owned by one person. How would it handle multiple person using a single device, or a person having multiple device?

Named clockwise. Sleep with head facing counter clockwise.

Classic cats

Well, printed page can still preserve branding. Idk how ink efficient it will be tho. I know damn sure the report to the higher up at my old companies is using fancy 100gsm paper with quality print settings.

Until you realize that valve engineering team has a mostly flat structure. So even their time to ship can be cut down because there's not a lot of middle manager

Ahh see, off-side rules is another shit that should die already (whitespace as indentation/scope)

What cryptographic method would allow the issuer (government) and requiring party (some service) both be blind to the pseudonym and identity?

Those murim novels/manhwa weren't lying?

I think proof of personhood, no matter how it is done, is problematic either way. So many things can go wrong. The issue stems from the question where/how to obtain said proof besides a government / institution backed document. Institution will always be problematic one way or another. Look at how TLS certificate mafia operate. Only a few "trusted" companies can make it to be the root of trust by default on billions of devices. If you want to use a selfie then there is an issue of ease of forgery. Let's face it, even many ID verification services out there struggle with it. Not to mention forging a photo realistic image nowadays is quite easy with generative AI. Overcome the issue of how said proof can be obtained then I am interested.

Yeah, you can use CRDT for offline as well. But IMHO, it is much too complicated for something that can be resolved by last write wins. Especially for an ERP where most of the time spent on OLTP as opposed to OLAP. For OLAP, then yes, probably CRDT when offline would be better too

If you need real-time, you can read about CRDT (Conflict-free Replicated Data Type). But for offline, you cannot ignore conflict so one way or another, you would need to ask user which data to keep or warn ahead of time that the latest write win while maintaining an audit log on the server. That's what I do for my in-house ERP. The client has a local copy of the data and is free to edit anytime.

We are moving to shorter certificate lifetimes because this reduces the risk of key compromise and mis-issuance. As a nonprofit we see it as part of our mission to make this change to advance security for everyone using the Web globally.

IMHO, the problem with deno was trying to be too different. That is it. De facto standard tooling and existing knowledge about server side JS/TS goes out of the windows. Don't get me wrong, it does force NodeJS to be more innovative but those friction is too big of a cost compared to myriad of example using NodeJS. So when Bun is trying to be 1-1 drop in replacement with added frail, everyone loves that

Yeah, but Nix and every other solution you mentioned has their own tradeoff and ease of use friction between developer and devops. Containers have good ergonomics for both that it reduces friction to achieve ci/cd

My two cent is put the PKGBUILD version itself. That is, if the build script is version 1, then just put that. If the PKGBUILD are updated in the future, bump it up as usual