Could not agree more. Too many -- WAY too many -- "features" from Javascript and functional languages have been jammed into C#, and the language has suffered for it. Every time I see "var blah" in C# code I cringe at how lazy you must be to not use strong typing when declaring a variable.
Same goes for "astink / await". If you need asynchronous multi-threaded code, use the damned Thread Parallel Libraries that Microsoft provided over a decade ago. Being forced to have every damned thing you write in C# wrapped with astink is just one giant code smell.
Yes, I'm old. Thank ghod I'll be retiring very soon, because as far as I'm concerned the tooling and languages I've used over the past 50 years have taken one step forward and at least three steps back in the past five years...
If you take it in the context of the industry, I think async/await is the more imperative friendly option. It let's you write code sequentially without callbacks. And the performance gains are definitely worth it. I'll have to respectfully disagree
about:config, type ".ml." in the search (no quote marks), set everything to false / zero / blank.
I don't want anything even vaguely related to spicy autocomplete on any of my machines, and I go to great lengths to kill anything that even resembles it with fire.
If only it were garbage in, garbage out - that would be solvable by better training data.
But it's much worse than that, because even if you'd only feed it good stuff, the output would still deteriorate.
pointing index finger at imaginary baloon: pfffffffffft
Congrats on being a parrot in the "oh noes, taken over by bots!" securitah echo chamber.
W7 is just fine. Daily driver on multiple machines, never been "taken over" or turned into a crypto miner or a hub for a bot network, never had a single virus or other issues.
