n0n0n4t0r

I wonder if in the EU, if you refuse everything, you're protected or screwed. Juridically, you should be okay, but is it rational to trust them to respect the law when breaking it is probably more profitable?

I see a lot of discussions about government level spying, this is a legitimate debate, but it mustn't obscure the "boring" security threat storing the results of ps aux poses! This is security 101 to never store this kind of information. I mean a bad actor now just has to (gain) access to these files!

I mean besides the theorical high level threat, there is a very practical one maybe sufficient for suing the company if it was a western one (I don't work in legal, I don't know what I'm saying)

Thank you for the clarification!

One could argue that the moon is orbiting the sun. The fact that it's orbit is a little wobbly because of interferes from the earth is a rounding detail, no?

With wsl (or docker desktop), for non production tooling, I don't think it's relevant anymore.

(I'm not saying it's on par with linux, I'm just saying it's usable)

How a friend of mine created a super fast csv parser by playing with branchless programming and SIMD to avoid the CPU serialized computation bottleneck

Funnily, "data security" encompass both protecting it from undesired access (and stealing) but also from loss/corruption.

So they do a terrible job from a data security point of view;)

Exactly what I was thinking: a modern privacy first proposal may be better suited with starting from chromium, even if it hurts feelings

There is also the coopling issue: when your code depend of another part of your own code, it may be broken by this inner dependecy. If the code is not intégration tested enough, then rarely used features may be broken without you noticing, thus the roting expression. Modern standards help protect against this with the test pyramid.