Interested in finding platform-specific bugs in your software? Let a class of students who mostly use Windows (don't ask me why) try setting things up and running your tests. I promise you won't get through unscathed. Every project. Every time.
-
-
i’d like to think that we do it to ourselves… most of the docs i see have relative paths with ./ and no concept of cwd(), etc., so ¯\_(ツ)_/¯
-
Which docs?
-
nodejs, webpack… just what i’ve looked at today; almost everything i read is doing it wrong
-
Yep! That's true! But if you push too hard as a Windows user, eventually you'll run into something who switches into rant mode about how Windows is evil and terrible and how they wish they didn't have to support it at all. And people are usually sympathetic :(
-
I've started to tread lightly when bringing up basic portability mistakes to avoid that response, but imagine how it feels for a beginner who (like most people) is trying to learn to program on a Windows laptop.
-
Sorry I had to teach while this conversation went on, great points throughout the thread. This point is what I am most interested in, because this describes my students perfectly. We need something like https://github.com/webcompat/web-bugs … but for platform-assumption bugs in open source env
-
i think not supporting everyone is a sign of an immature product & dev (team); literally takes no more effort, less if you abstract it away
-
i don't think a list of "bad things" is going to move the yardstick, it's more reasonable to open PRs with fixes in docs... would be better
- 2 more replies
New conversation -
-
-
Also the widespread belief that symlinks don't work on Windows so you don't need to bother supporting it (TLDR nope they work on Windows for a lot of people and you should use a symlink-or-copy abstraction anyway)
Thanks. 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.
