I put unix in quotes ("for this" referring to interop). Was responding to someone who said "interop with Unix"
-
-
People target nothing specific. They just add workarounds for platforms they feel morally willing to work with.
2 replies 0 retweets 6 likes -
Replying to @wycats @mj_langford
People target POSIX, Linux or MacOS (occasionally BSD or Windows, too). People who know what they are doing know what they are targeting.
1 reply 0 retweets 0 likes -
Replying to @jen20 @mj_langford
That's just not true. Almost every real system targets epoll/kqueue, which are non-standard interfaces.
3 replies 2 retweets 5 likes -
For the longest time, people said they couldn't support Windows because there was no equiv of epoll/kqueue. False: IOCP can shim it.
2 replies 0 retweets 0 likes -
Replying to @wycats @mj_langford
That may be true, but it was always a garbage argument. We have event ports, there are lots of ways to support all models.
1 reply 0 retweets 0 likes -
Replying to @jen20 @mj_langford
Right. Exactly. I'm saying that Linux+OSX=Unix is actually causing the exact confusion you were worried about.
1 reply 0 retweets 0 likes -
Replying to @wycats @mj_langford
I don't use UNIX to mean that. You shouldn't either. Writing portable code is not hard. Fucked if I'm going to test it on Windows though.
1 reply 0 retweets 0 likes -
I did _so much_ interoperability work at HashiCorp (not least for Windows) that I'm prepared to say this unequivocally: Windows is harder.
2 replies 0 retweets 0 likes -
Also - who likes and retweets their own replies. WTF.
1 reply 0 retweets 0 likes
I didn't mean to like it. Mistake. I RTed it so I didn't have to repeat the tweetstorm from the top.
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.