I switched to Windows 18 months ago and continue to be happy. Only complaint is devs gratuitously ignoring windows support.
-
-
Example: WSL is closer to Linux than OSX is. But people are morally unwilling to add WSL workarounds. Why?
-
Can you give an examples of WSL workarounds required? I thought it'd be largely POSIX compliant, which is a reasonable target IMO
-
WSL shouldn't be targeting POSIX per se - it should be targeting Linux. Workarounds for stuff that works on Linux proper are bugs in WSL.
-
Except that people do workarounds en masse for POSIX inconsistencies in OSX. You can say "not my problem", or you can do what pepole ...
-
do in OSX and slap a bandaid on it while the upstream bug gets addressed. At least WSL's "radar" is Github Issues.
-
OSX doesn't have the explicit goal of targeting full compatibility with someone else though. WSL bugs == SmartOS LX Zone bugs == bugs.
-
Luckily, the WSL team is super receptive to cases which prove different (as the LX team is), and get them fixed and released quickly.
-
OSX claims to be a "certified Unix" but has bugs. But this is a deflection. Regardless, pragmatics say we should work around bugs.
End of conversation
New conversation -
-
-
People target POSIX, Linux or MacOS (occasionally BSD or Windows, too). People who know what they are doing know what they are targeting.
-
That's just not true. Almost every real system targets epoll/kqueue, which are non-standard interfaces.
-
For the longest time, people said they couldn't support Windows because there was no equiv of epoll/kqueue. False: IOCP can shim it.
-
Epoll and kqueue aren't even particularly similar. OSX has old-school (90s) signals, Linux has signalfd. Real apps use signals.
-
People target OSX-specific linker behavior (namespaced symbols) by accident all the time, also cargo cult Linux incantations.
-
These same people often don't bother to learn how the Windows linker work, even "people who know what they're doing"
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.