Here’s the original report: https://securelist.com/stripedfly-perennially-flying-under-the-radar/110903/

It doesn’t specifically attribute this to the NSA, and it’s very hard to definitively say who created what malware anyways.

That being said, if you read through the report, the details on this really scream “state actor” most probably. The level of modularity, the infrastructure of the C2 server, and the detailed & flexible spying capabilities all point to some government agency more than anything else.

Just wanted to give props to this super informative comment. Thanks for the write up and relevant links!

WASM’s biggest holdback is that it cannot directly access the DOM. Until then, JS will still have a prominent place in building anything rendered in a browser.

But have you heard of Rust? Rust has zero-cost abstractions! Zero cost!

I agree! I don’t think 3?”stuff”:”empty” should work at all because I think it’s an insane way to type a ternary :) I’m also very open to admitting that it’s just my own strongly worded opinion.

I think that in most cases, syntactically significant whitespace is a horrible idea - the one exception being that you should have space between operators/identifiers/etc. I don’t care how much, and 4 spaces should have no more special meaning than 1, but I do think that using a space to indicate “this thing is a different thing than the thing before it” is important.

No problem! It is a lot of information at once but I’ve been having a great time playing it so I’d really recommend it to anyone who thinks it could be interesting.

It’s not just because of nonsense, it’s more that it doesn’t really matter what you do - the only thing stopping someone with physical access to your machine is their level of determination.

At some point, there’s no stopping the laws of physics. Your data is physically stored there. You can do a lot to make it really difficult to access it, but the best you can do is full disk encryption with a sufficiently strong key, and only store that key on external hardware that isn’t accessible to the attacker.

Even then, you better make sure that your encryption key wasn’t hanging around cached anywhere in memory before you shut down your computer.

The choice between Linux and Windows is not just about ideologically choosing open vs closed source software.

If you don’t want to use closed source software, don’t use VS Code - but if you want to use Linux, and you want to use VS Code, those two choices are totally compatible and perfectly valid

I’m super excited to see what the final release looks like for Blazor web apps. Clearly there’s a lot of hard work going into unifying server/WASM rendering and I’m ready to get my hands on it.

“Dependency injection” is just a term for providing a function or method with its dependencies rather than making the function go and gather them itself.

It’s (typically) done through parameters, but it’s still more specific than just invoking a function. It describes how that function was written and the reasoning for certain parameters. To the other commenter’s point, you’ll have a hard time communicating about your code with other developers if you refuse to use the term dependency injection just because you don’t like OOP.

In my experience, inheritance is really handy in the right situation. But far more often, inheritance is just a quick way to code yourself into a corner or just a waste of mental energy in the wrong place.

Any production project, especially with that sort of rigor, should be sticking to the LTS releases. IMO there is no project that should be on 7 with no plans to upgrade to 8 after it’s released.

If a version upgrade is out of scope, then it should’ve been built on 6 to begin with.