There's quite a lot of developers at stodgy Fortune 500 non-tech companies that are sort of forced to use Windows for development. Either explicitly, or though poor enterprise support (vpn connectivity, local admin restrictions, difficult path to purchase a Mac, etc).
It's one reason things like Gitbash, WSL, Docker Desktop, etc, are very popular.
"Quite a lot"? There are more developers at Fortune 500 than FAANG for sure.
In that sort of company it’d take 2 years to get approval to install it anyway. If you submit the paperwork now there’ll probably be a windows port by the time it’s approved.
But given that the majority of developers are web developers[1], how can that be the case?
[1] including, unsurprisingly, the respondents to that survey https://survey.stackoverflow.co/2022/#developer-roles-dev-ty...
https://medium.com/codex/jetbrains-django-developer-survey-r...
In case you are seeking anecdotal evidence: does your company employ offshore devs? Try and ask them what do they use. Outside of the few countries where most people can afford Macs, things are different.
yes, you are right, they definitely were allowed to check more than one item, we can see that the total sum of all options gives us a total of more than 100%, so that must have been the case.
But even then, it's hard to overlook the fact that the first three options in the list are related to web development, and with quite high percentages.
It's naive to assume that Windows isn't prolific. There's probably no good way to quantify numbers, but it's a major player still and likely always will be. WSL certainly helped keep that a reality.
I don't see how rimraf is related in any way. If you want to remove folders by calling a shell command (with full knowledge of all potential security and portability risks), your code is going to be platform dependent - it's not Node's responsibility to reimplement bash and/or GNU coreutils to make it magically work. Therefore, you need a Node re-implementation of the same functionality, either in the standard library or as a package.
And besides, rimraf has been unnecessary for a couple of years now, as Node's standard library includes a direct replacement: https://nodejs.org/docs/latest/api/fs.html#fsrmsyncpath-opti....
I kind of have to as of late, because due to corporate security policy I get around a minute of internet access from WSL and then the antivirus steps in and blocks it.
https://github.com/sakai135/wsl-vpnkit/commit/94a85aaf4db365...
* What IDEs/editors I have access to
* What image editing tools I have access to
* How easy it is to get my server’s backend running on my local machineas a dev environment
The last one is most relevant to this conversation. If I’m working on a bun-based project, not being able to run a local dev copy on Windows easily is a nontrivial obstacle.
One of the reason WSL exists is to solve this problem.
(assuming bun doesn't work on native windows but works under wsl)
It's possible to create command line tools that work across Windows and UNIX-oids, and I appreciate this, but it's a lot of additional work (even 'cross-platform' solutions like Python don't fully wrap this stuff, even though they do their best).
FWIW, I have been remarkably impressed with Rust for this. The stdlib and package ecosystem are unusually good at building abstractions that work across *nix and Windows, and so the average command line tool written in Rust usually has good Windows support.
Of course, the additional work hasn't really gone away - it's just been relegated to libraries unusually effectively :)
Things like "www-authenticate: Negotiate" in an SSO environment, people pasting rich text into web forms, handling environments with private certificate authorities, and so on.
Safari often has bugs and rendering issue which aren't present on Chromium or Firefox and need fallback.
I have bad luck with Macs, getting dev tools properly installed seems as hard as on Windows and everything falls apart a few times a year. The OS also seems to break itself and crawl to a halt sometimes (>1 minute to open settings). Linux distros were stable only if I can stayed on the happy path (single monitor, integrated graphics, don't try to sleep/hibernate) with close to default config. Windows can seemingly tolerate a lot more fiddling, at least since 7.