Just to be clear, I am not saying that to fix the windows problem every developer needs to thinks about portability all the time.
-
-
You might be thinking that this kind of wacky behavior is just further evidence that Windows is a lost cause, but the truth is that the problem was caused by people believing (and disseminating) a false belief that you don't need path abstractions.
Show this thread -
That's just one example. Other examples (largely historical) that I have noticed in my career include: * Windows has no support for symlinks * Windows has no support for anything like inotify
Show this thread -
My favorite example of something we did in Ember CLI to better support Windows is creating the symlink-or-copy utility (kudos to
@stefanpenner for that one). It uses symlinks where available (often true on Windows!) and falls back to copying when needed.Show this thread -
* We didn't have to give up good performance just to support windows * We didn't fall into the common trap of supporting symlinks on *nix and not on Windows (the "make it work but don't optimize it" trap) * The abstraction largely eliminates the cognitive load from portability
Show this thread -
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 -
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.