You should not trust those builds. Everything you need to know is documented here: https://learn.microsoft.com/en-us/windows/privacy/manage-connections-from-windows-operating-system-components-to-microsoft-services
Windows 10/11 Enterprise is recommended as that’s the version where Microsoft can’t fuck up.
No, that’s a myth. Registry edits may revert in some cases yes, but group policy is different as it designed exactly to configure machines in a stable way.
Group policy may be beyond the general skill level, which makes the constant Linux suggestions even more laughable.
Ahaha yeah, I’ve said that SO MANY times. People have issues setting a few toggles on a point-and-click UI but then it is okay to suddenly move to a entirely different OS that most likely won’t have the software they’re used to and requires terminal skills to deal with most things. Laughable indeed.
Completely bullshit, garbage clickbait title.
Windows 10 is near EoL, however that’s for Home/Pro/Enterprise versions, you can move to one of those for more time:
To be fair I don’t really believe that Microsoft will kill it when they say they will. And even if they do it, porting security updates from those LTSC versions into the regular ones might be doable.
Now on Windows 11:
You can just disable copilot and all the other garbage using group policy, now that hard and you’ll end up with essentially Windows 10. https://www.xda-developers.com/how-disable-microsoft-copilot/
There’s comments in the specs and a bunch of parsers that actually inore //
Exactly that’s a job for the parser / consumer.
No, I’m kind of serious, the comment situation is already solved in JSON… about the rest yeah, Yaml might be easier but the different isn’t that much. Non tech people can’t edit Yaml properly either so.
There’s a lot of JSON parsers that don’t mind to see comments there, just ignore them. And there’s also the “_comment” / “$comment” thing.
Yes, they could’ve just used JSON. Totally pointless waste of time.
I dint know many OO languages that don’t have a useless toString on string types
Okay, fair enough. Guess I never found about it because I never had to do it… JS also allows for "test string".toString() directly, not sure how it goes in other languages.
Today I found out that this is valid JS:
const someString = "test string";
console.log(someString.toString());
At least he is honest about who he / the platform supports, not some shady algorithm pending to one side, or some tv channel being left while another is right lol
No shit, but then even Obama used Twitter to win the elections. What’s new?
tax payer subsidies
It’s not subsidies, it is tax breaks if companies go there. A very different thing.
So what, people need cloud services and Netherlands did the same and became one of the top spot for datacenters in Europe and nobody is bitching around.
3,2,1… more spyware coming to Firefox.
It depends on the type of application and size. For your typical business app / backoffice with tons of fields on the same page and real time data reactivity makes sense, otherwise it doesn’t.
The nixCraft headline is stupid, just because you are running on IPv6 without any NAT doesn’t mean your router doesn’t block incoming IPv6 traffic to hosts on the network - this is actually the default in 99.9999% of devices.