Just to be clear, I am not saying that to fix the windows problem every developer needs to thinks about portability all the time.
-
-
I do not believe that "shaming" everyday developers into supporting Windows is a good idea. People have enough on their plate already, and asking them to think about new requirements all the time doesn't work.
Show this thread -
But I do think there's a lot more we can do at the tooling level and culturally to help people fall into the "pit of success" when it comes to portability and windows support.
Show this thread
End of conversation
New conversation -
-
-
Aren't MS the ones that should be maintaining stuff like this? Otherwise we're doomed to redo it in every language and every time MS update something.
-
Windows is very stable! And I don't necessarily think it's Microsoft's job to write abstractions that work across Windows/OSX/Linux/BSD/etc. for the same reason in reverse.
-
It would certainly make things easier. For example you could write native (C) libraries that abstract over platforms, then use those in all programming languages... but now you need a C compiler and dependency management on Linux (sudo apt install libdep-dev or it wont install)
-
single-platform native libraries were also a huge pain in node at least until recently. For example, fsevents messed with npm's package-lock.json
-
in my experience these native modules tend to introduce random problems with various random developer machine setups, increasing the barrier to entry.
-
I'm saying stuff like libuv (and mio in rust) work better than OS vendors doing it.
-
I can agree with that for sure.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.