But probably also stuff like signalfd and significant divergences in Darwin's GCC. Or maybe you just got used to them.
-
-
I don’t understand your stance here. I’m telling you even -with- all the differences between Linux and OSX it’s easier to write ...
1 reply 0 retweets 0 likes -
Systems that target both of them than it is to include windows, and your response is that I’m not using the right different parts?
1 reply 0 retweets 0 likes -
Or that I’m just used to/unaware of the differences?
1 reply 0 retweets 0 likes -
No. I'm saying people have worked very hard to make it easy to support OSX/Linux and not very hard to add on Windows.
1 reply 0 retweets 0 likes -
If you write a Rust program using the Rust stdlib and are even a little careful, chances are it works fine on Windows.
1 reply 0 retweets 0 likes -
Node: sort of true, but still a lot of gotchas (like scripts in package.json implicitly depending on bash)
1 reply 0 retweets 0 likes -
Writing core infra: very, very hard. Most core-core libs have forks for OSX/Linux but dropped Windows on the floor.
1 reply 0 retweets 0 likes -
My stance is: let's stop dropping windows on the floor. Care more about stuff like "scripts" accidental dependence at a platform level.
1 reply 0 retweets 0 likes -
I'm not asking you to personally bear the burden. I'm asking us all to demand more from core infra. And I think it pays for itself ...
1 reply 0 retweets 0 likes
at that level by increasing the amount of available contributors. But again, this is something that works from the top. ...
-
-
I'm not asking you personally to eat your veggies.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.