Fortunately not a whole of of data and for sure with a little bit like that there wasn't anything important, confidential or embarrassing in there. Looking forward to Microsoft's itemised list of what was taken, as well as their GDPR related filing.
Pentests where people actually get out of bed to do stuff (read code, read API docs etc) and then try to really hack your system are rare. Pentests where people go through the motions, send you report with a few unimportant bits highlit while patting you on the back for your exemplary security so you can check the box on whatever audit you're going through are common.
The extraordinary claim that Ukrainian shelling of positions in Donbas is why Russia invaded Ukraine is what requires extraordinary evidence. And we already know that claim is nonsense so spare me.
I've invented plenty of stuff that 100's of millions of people use every day. Whether I get credit or not doesn't really matter to me. It paid for more than half my life (and those of a lot of people around me) and it made the world a little bit better (and sometimes a little bit worse).
Inventions are a dime a dozen, if you care that much about the credit or the money then you should go try to patent your invention, and if you don't then that's fine too but there is no such thing as CC-BY for inventions (though, technically you could patent something and then put the patent in the public domain 'Manfred' style).
If you are aware of SAP breaking the GDPR and it's being swept under the carpet or if enforcement is lackluster given the scope of the problem then please supply some evidence. That SAP is large doesn't matter, what matters is if they are breaking the law.
Infrastructure needs maintenance, culpability only makes sense if there are enough funds for such maintenance and if there is an organization level compatible with the kind and scope of the work. I wouldn't make any assumptions about that in the case of Lybia.
Russia has given each and every excuse that you could possibly come up with in 2014 and again in 2022. If you're a defense industry consultant I'd expect you to be more than conversant with the run-up to the second episode of this war and not to swallow such things hook, line and sinker.
Note that nowhere in that article does it say that the Ukrainian side did that. For all we know this was a provocation, as Russia is won't to do. Alternative explanations have been present many times and none of them have stuck.
Also note that there was an endless build-up prior to the second phase of this invasion which had absolutely nothing to do with that particular incident even if it was done by the Ukrainian side, which I highly doubt given the fact that it was one of the pretexts used.
Finally: in that region there have been many actions by either side and no matter what: the Ukrainians are well within their right to kick out an invader, the myth of the separatists has been debunked solidly, until the little green men showed up there was no meaningful separatist activity.
Interesting. I routinely have 100's of tabs open on a 10+ year old thinkbook with 16G in it (they were only sold with 8 at the time but replacing the two 4G modules with 8G modules worked, 16G does not seem to work).
Firefox has an about:performance gizmo that can tell you which tabs are misbehaving, this has already led to me blacklisting some sites completely, others just to close when not in use. Especially image carrousels can be very resource hungry.
If you aggressively (and I mean really aggressively) block any and all ads you'll find that you can use that 15+ year old machine just fine on the web. The bloat is mostly in the marketing and advertising part of the web, not in the content part.
Python software simply rots while you're not watching it. Either you make it a full time occupation, every time some library gets an 'upgrade' (with a ton of breaking changes) you get to rewrite your code, sometimes in non-obvious and intrusive ways. And every time the language changes in some breaking way you get to spend (lots of) time on debugging hard to track down problems because the codebases they occur in are large enough to mask the problems that would have come out if the same situation had occurred during development.
And that's before we get into the various ways in which python versions and library versions can interfere with each other. You couldn't have made a much bigger mess if you tried. And I actually like the core language. But so many projects I wrote in python just stopped working. I remember having a pretty critical chunk of pygame code written for a CAD system that just stopped working after an upgrade and there was no way it was ever going to run again without rewriting it. That's the sort of thing that really puts me of an I remember it long after. Machine learning code is still so much in flux that it doesn't matter. But hardware abstraction layers such as pygame should be long lived and stable between versions. And that really is just one example.
Anyway, I think asking 'That other languages don't' doesn't really matter. But Haskell (see TFA) is one language that always tried hard not to be successful so breaking changes would be permitted (which is fair). Python tries both to be popular and to allow for major stuff to be broken every now and then and that is very rough on those that have large codebases in production.
By contrast, COBOL, FORTRAN, LISP, ERLANG, C and C++ code from ages ago still compiles, maybe you'll have to set a flag or two but they're pretty careful about stuff like that.
But it won't stop there. Why would it stop at some arbitrarily defined boundary? The savings associated with no longer having to pay programmers the amounts of money that they believe they are worth (high enough to result in collusion between employers) are just too tempting.
2->3 has been a complete disaster, anything older than a few weeks tends to randomly break with some kind of dependency issue, sometimes requiring multiple installations of python on the same machine which will bite each other in hard to predict ways. Python is a wonderful idea but I've yet to be able to write something in python and call it 'finished' because it never ever continues to work in the longer term. Highly frustrating and in my opinion unnecessary.
That certainly helps.