It implies to people that *Windows is harder* but really it's just a third distinct thing to target.
-
-
Replying to @wycats
In this context, for most, “Unix” means OS X + Linux. They ARE more similar to eachother than windows, by a lot. Biggest delta: path strings
2 replies 0 retweets 1 like -
Replying to @izs
1: Yes, I think paths are a big deal. path.join is more or less good enough. Everyone going around convincing each other that it's not
2 replies 0 retweets 3 likes -
2: actually very important ("windows supports `/` yo" "uhhh not with verbatim paths") has been a huge huge regression.
4 replies 0 retweets 1 like -
3: But I think you're underestimating epoll/kqueue shimming, compiler/linker shimming, OpenSSL/crypto shimming, etc.
2 replies 0 retweets 1 like -
4: OSX and Linux share a path model (but not exactly a file system model), but they diverge a huge amount in general.
2 replies 0 retweets 0 likes -
5: the reason most people don't perceive that is that a lot of "Unix" libraries are actually just "shimming the union of OSX and Linux"
1 reply 0 retweets 2 likes -
6: epoll and kqueue are a good enough exemplar of this phenomenon to drive a discussion about this, but there's way more.
2 replies 0 retweets 0 likes -
7: OSX+Linux=Unix causes people to believe it's morally virtuous to write abstractions that cover "Unix" but not Windows. Usually a mistake.
2 replies 0 retweets 0 likes -
Replying to @wycats
I’ve written a lot of programs and libs that handle paths and/or signals. Idk about “moral”, but certainly it is cheaper and easier.
1 reply 0 retweets 0 likes
OSX and Linux have completely different practical signal models. The reason you perceive them as the same is because shims already exist.
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.