[RyanZAG]

Windows 10 is really recent though.

That said, since I like controversy: I'm happier to see Microsoft buy Github than I would be to see Google or Facebook buy it.

And also! A big shoutout to Linus for helping to make source control distributed and open, which means swapping between git providers (for the code at least) is simple, easy and impossible to block. The amount of good Linus has done for the world is incredible.

[mpartel]

Another recent example: lockdown of ARM-based Windows machines, preventing the installation of other operating systems.

[badsectoracula]

I really dislike how you get downvoted (your message is faded out) here. Do people really applaud removal of control of their own devices?

[Wurdan]

I think it's because Microsoft's reason for doing this is plausible and not as anti-competitive as that comment makes it seem - locking down the boot process has serious security benefits.

[mpartel]

I admit I may be ignorant, but could you spell out the security benefits of going from "locked down but user-openable" to "not user-openable"?

(edit: specifically benefits that couldn't be effectively addressed by making it a little difficult and scary to open that lockdown?)

[nailer]

If it's openable it's not locked down. If I can't trust the kernel then every level above it is tainted (this is assuming you can trust the CPU and firmware, but at least ARM is better than Intel here).

[mpartel]

OK, let me be more accurate: "user-openable" in the sense that the user is free to choose to trust any OS vendor they want. What's the unmitigatable harm?

[guardian5x]

You mean like Android or iOS?

[mpartel]

Like iOS yes, and some, but not all, Android manufacturers/phones.

"Others do it too" is not a very good justification in my mind.

[guardian5x]

"Others do it too" is not a good justification of course. But his comment also fails to to explain how Microsoft is somehow more evil than the industry standard.

[mpartel]

Bootloader lockdown was practically unheard of for the PC/laptop form factor before Microsoft started doing it for ARM laptops. And and it's not even really standard for phones. Plenty of Android phones have unlockable bootloaders (see LineageOS).

I don't think whether one is more evil than Apple/iOS in this regard is a good benchmark.

[hobofan]

You mean unlike most other desktop/laptop OEMs/manufacturers?

(which would be the more apt point of reference)

[raesene9]

Lockdown of consumer grade devices isn't really a new experience (e.g. iOS devices).

There's a trade-off to be had between security/reliability and flexibility.

If MS were selling those devices as general purpose computers and then refusing to allow other OS installation, I think that would be dishonest, however as far as I'm aware they're not making such claims.

[mpartel]

I don't see the tradeoff honestly. Sure, make it a little difficult, show a big red scary warning, perhaps even require the use of a screwdriver to discourage "casual" users from being misled into compromising their machine's security.

But ultimately true ownership, recyclability/reusability (Linux on aging hardware..), and hardware-independent OS competition are norms with significant benefits that we shouldn't give up lightly.

[raesene9]

Those may be norms for IT professionals, but the needs of IT professionals are very different from those of standard users.

Realistically most people (numerically) don't want a computer, they want a thing that lets them communicate, create and consume content.

Lockdown isn't a problem for them, and walled gardens like iOS are generally the best way for them to stay secure.

If you provide a method to escape the sandbox, it is likely that attackers will work out how to exploit that. For example try going to facebook.com and open the developers tools. They've had to put a warning in there to stop people from "self-XSS" ...

[mpartel]

That's why I'm entirely OK with making it scary and a little difficult.

And it's not just IT professionals, but also their friends and family, especially those that can't afford to or don't want to get a new device that often. I think this is a pretty significant set of people.

[raesene9]

So are you not ok with the concept that some people don't need that option and, as long as the vendor is clear about what is and isn't possible, having some devices that are more locked down that others is acceptable?

[badsectoracula]

> If MS were selling those devices as general purpose computers

They are computers, regardless of what sort of dress they wear, and users should have control over their own computing devices.

[cube2222]

Well yes, Windows 10, finally a practically usable Windows in my opinion. Finally working, with a lot of polish and Dev tools available. (Like wsl)

[beagle3]

It was pushed down the throat of customers, using dark patterns and “better ask forgiveness than permission” ethics. It also took away choice from the vast majority of users, and started sending opaque and vaguely described telemetry.

The problem with Microsoft wasn’t that their software sucks (some does, some is great).

It is that they have been bullying users and companies for the past 30 years. Many people point to a “new Microsoft”, and the win10 rollout is a stark counter example to that claim.

[cube2222]

Yea, the telemetry one was kind of shady at the beginning, when it got turned on again after every update. That's changed a while ago though, and you can actually look through all the telemetry you're sending.

[krageon]

And you still cannot properly turn it off. Weird and invasive things still happen with large updates (bundled so you cannot pick and choose which changes are appropriate for you, such as security fixes only). The whole OS is a few quality of life changes that make it palatable to most people to deal with all of their frankly offensively invasive practices.

[setquk]

I don't buy the usability argument of WSL. The thing isn't anywhere near a useful Linux environment other than for some noddy stuff that cygwin can already handle. Try running a background process, a service, use a serial port or drag some half decent performance out of it and you'll see.

It is ultimately backed with NTFS and NT's buffer cache. Running a VM is still several orders of magnitude more productive. And you can't fix NTFS and NT now. It's impossible.

[rcarmo]

Serial ports work fine with my Arduinos. I regularly flash stuff using ESP tools from WSL.

[setquk]

Is this a recent change with 1803?

I was attempting to use AVR-gcc toolchain and some SCPI over serial stuff with WSL unsuccessfully.

[cube2222]

That's… completely false. At least for me. You should really stop and think before accusing people to have noob workloads.

Even cronjobs work… The performance is sometimes better than on native linux, as a few of the syscalls are better implemented on windows. The file performance is abysmal, but that only hurts if you're using npm (and there you're in a world of pain already anyways).

The only thing lacking, is that some debuggers don't work, which is a pity, but then I just start a docker container and mount it on my filesystem.

I am using services on it too actually, everything works as expected. I can actually create windows bat files to redirect to linux binaries, which lets me do for example OCaml development, with the linux toolchain, on a system that actually works reliably. (my experience is, that as of windows 10, desktop linux environments crash way more often than windows ones)

[setquk]

Grep 150,000 source files on Linux and on WSL and come back to me. That's a pretty standard console load. It kills git operations, package managers, compilers, the lot. ALL the tools I use it for. Well USED it for.

Real data:

linux -> 1.3 seconds, all from buffer cache on a cranky old 10 year old HP desktop with 8 gig of RAM and bottom end SSD.

wsl -> over a minute on a 12 core i7 with high end m2 SSD, every time.

This is because of NTFS's awful performance on small files. The whole of Unix is file based and uses huge numbers of small files, as does source code generally so this is an end game scenario for the platform. It simply sucks!

This goes back to when we had SVN which would take 6-7 minutes to check a repo out onto NTFS versus 20-30 seconds onto ext4 on the same rust disks. SVN was treated like cancer by the organisation for what is fundamentally a platform limitation.

[burntsushi]

As the maintainer of ripgrep, I pay attention to these sort of things. I will say that I noticed a similar performance problem in my tests as well, but further investigation revealed that Window's antimalware process was severely throttling file reads. Once I disabled that, performance on Windows is nowhere near an order of magnitude worse than Linux.

[setquk]

Thanks for commenting. I have disabled windows defender on the machine and tweaked the filesystem with fsutil and it is still running at over 40 seconds on the same workload.

[cube2222]

Source code files are small... but hardly a lot though. I've usually been doing extensive search on big files, and ripgrep is great for that (and available for windows).

[nailer]

I just use `git grep` which isn't as fast as ripgrep (https://github.com/BurntSushi/ripgrep), but is still damn fast (on Windows).

[setquk]

  $ find ~/src | wc -l
  242341

Maybe, maybe not.

[executesorder66]

> practically usable Windows

- forced updates (and forced restarts that go along with that)

- OS level advertisements (even though you are still paying for the OS)

- impossible to configure privacy settings

That alone makes it one of the shittiest OS's ever released.

[dfcowell]

Realistically, out of all of the BigCorps who could have bought it (and who have deep enough pockets to sustain its bleeding,) Microsoft is one of the best of a bad bunch.

I'm not quite as cynical as the author of the OP when it comes to Microsoft's recent apparent change of direction, but who knows, that may just be naivety speaking.

[cecja]

the best out of a bad bunch... what does this even mean. They are killing a neutral force in the market space there is nothing good coming from it.

[dfcowell]

It seems like the alternative was GitHub running out of cash, so the main good coming from it is that GitHub will continue to exist.

[SmellyGeekBoy]

Better integration with Microsoft's existing ecosystem would be a good outcome (for developers working in that ecosystem) as well as more investment in general. As others have stated, VSTS is excellent so they definitely know what they are doing in this space.

"Nothing good coming from it" seems a bit of a stretch when we don't even know the terms of the deal yet - or indeed whether it's actually happening at all!

[raesene9]

I think MS made mis-steps on the Windows 10 privacy setup for sure, although they've largely fixed it in later releases with improved visibility of Privacy options and better docs on how to disable most of the telemetry stuff.

Personally I like Windows 10 as a general purpose client OS, WSL is great and stability for me across a number of devices has been very good.

[badsectoracula]

> and better docs on how to disable most of the telemetry stuff.

How about disabling all of the "phone home" stuff, telemetry or whatever else? There is still only two options "Basic" and "Full" options without any "None" option and really most of the relevant options are scattered all over the place, making it a chore to disable them (and you need to redo that stuff every big update). This is either extremely dumb (which i doubt) or done with malicious intent so that people will miss stuff and/or get tired of them.

Unless they provide the means to completely stop all communication with their servers with a single switch, there is no reason to give them any benefit of the doubt.

[ekianjo]

Yeah but they reset your privacy settings with every update. Thats what we call dark patterns.