> > embrace, extend, extinguish strategy with WSL

> They are EEEing their product - Windows?

No, Linux obviously.

First they like and integrate Linux into their own products. Azure, WSL and others.

Then, they provide extensions that are closed-source on top of those.

With the goal to extinguish the original project so they have more control over the direction.

If it was that easy to kill Linux it would have happened already. Chad Linux, open source free software, withstanding the full might of the multi billion dollar juggernaut Microsoft.

They're still doing their best to kill Linux on the desktop.

Notice how, as much as .net core is cross-platform, the desktop UI side of MAUI is absolutely not, and left 'to the community'.

They do not want to enable desktop developers under Linux, as they know that a decent environment would likely remove any need for Windows in that space.

WSL has been out for at least five years now and it’s still just a fancy kernel adapter without feature parity. I might begin to worry once things like containers actually work properly. Until then, I don’t think Microsoft has fully embraced Linux much less extended it.

I did just now learn that systemd was finally added to WSL. Originally that was never going to be added and back in the days of WSL 1 I remember the WSL writing blog posts about that being ridiculous. Who knows, proper container support might be added soon.

Containers do work in WSL2, although you hit Hyper-V bugs if you spin up very many of them. WSL2 is the basis of Docker Desktop and similar apps.

Microsoft has also already added proprietary extensions to WSL2, like the integration with the VSCode remote development plugin and DirectX passthrough for machine learning and maybe other things (there's a DirectX driver on Linux which is usable only on WSL guests).

We're at the embrace stage right now, that's why you see it getting integrated.

And if you run WSL, you usually end up with a special kernel, it's not just the upstream one without changes.

Both my Arch and Ubuntu WSL is on kernel `Linux desktop 5.15.90.1-microsoft-standard-WSL2` rather the ones the distributions ship with by default if installed normally. This is the one they ship via Windows Update which you end up using on WSL: https://github.com/microsoft/WSL2-Linux-Kernel

Watch them slowly make it different than the upstream one, without contributing patches upstream.

I mean google uses VSCode internally as their officially supported IDE… i’d say they’re doing pretty well.

Because of products created before VSCode

What do you mean?

They are doing well because of products and market share they held before using vscode. So it's unrelated success.

I meant, VSCode is pretty successful if it can get Google to switch over to using it.

No it's based on theia

> Vs Code? wtf? there's a lot of other IDEs/editors and many would argue that they are better

VS Code is hugely dominant in terms of IDEs used by developers per the StackOverflow survey. It commands more than double the percentage of the next most used… and the second place is Visual Studio.

https://survey.stackoverflow.co/2022/#most-popular-technolog...

VSCode is just the lowest common denominator IDE that works decently with most languages and platforms, I use it a lot but would not think twice about switching to something else (as I have many times in my career). I don’t think it really has any “moat”

Lol. Except the huge library of plugins, tight copilot integration and majority market share

and Remote Development extensions

Those numbers are a bit misleading because they split up the JetBrains products, making JetBrains look like a smaller market than it actually is. If you add up all their tools, they hit 94% to VS Code's 74%. Obviously there are a lot of people using multiple JetBrains tools and that bloats that number, but the huge difference demonstrates how flawed SO's numbers are for gauging market share.

Also, I suspect that most people who mark a JetBrains IDE also mark a secondary editor that's lighter weight, but it's hard to tell how that all breaks down with the way they present the data. I spend about 90% of my work day in WebStorm and occasionally move over to VSCode for loading a large directory that I don't want to index. When I filled out the survey, due to they way they worded it, I marked both tools.

Add Comment lolinder 11 days ago | parent | context | on: GitHub code search is generally available

Those numbers are a bit misleading because they split up the JetBrains products, making JetBrains look like a smaller market than it actually is. If you add up all their tools, they hit 94% to VS Code's 74%. Obviously there are a lot of people using multiple JetBrains tools and that bloats that number, but the huge difference demonstrates how flawed SO's numbers are for gauging market share. Also, I suspect that most people who mark a JetBrains IDE also mark a secondary editor that's lighter weight, but it's hard to tell how that all breaks down with the way they present the data. I spend about 90% of my work day in WebStorm and occasionally move over to VSCode for loading a large directory that I don't want to index. When I filled out the survey, due to they way they worded it, I marked both tools.

If you haven't already, would you mind reading about HN's approach to comments and site guidelines?

Add Comment lolinder 11 days ago | parent | context | on: GitHub code search is generally available

Those numbers are a bit misleading because they split up the JetBrains products, making JetBrains look like a smaller market than it actually is. If you add up all their tools, they hit 94% to VS Code's 74%. Obviously there are a lot of people using multiple JetBrains tools and that bloats that number, but the huge difference demonstrates how flawed SO's numbers are for gauging market share. Also, I suspect that most people who mark a JetBrains IDE also mark a secondary editor that's lighter weight, but it's hard to tell how that all breaks down with the way they present the data. I spend about 90% of my work day in WebStorm and occasionally move over to VSCode for loading a large directory that I don't want to index. When I filled out the survey, due to they way they worded it, I marked both tools.

If you haven't already, would you mind reading about HN's approach to comments and site guidelines?