Most of the time it's a desire to please and there's a hesitance to tell users: "if you want to use this tool then conform to its standards and conventions".
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Can't imagine someone wanting a non-English folder structure :)
-
Do you want localization for every single tool? CLI commands and flags, error messages too?
- 1 more reply
New conversation -
-
-
This is extremely pervasive in the JavaScript ecosystem. Perhaps a direct response to so many of the 90s/00s programming trends of convention > configuration.
-
90s and 00s were configuration-heavy. The Java ecosystem was similar to JS today in this regard. Ruby on Rails came in as an answer to that with stromg conventions.
End of conversation
New conversation -
-
-
Why? In project A I want it to be 'test', project B 'tests', project C '__tests__', project D 'specs'. Makes tons of sense!

-
I loved my Ruby on Rails days where I could drop in on a project and know exactly where things are.
- 1 more reply
New conversation -
-
-
I always said that webpack is an operating system
. Indeed, it is a double edged sword: it's greatest strength and weakness.
But thanks to the efforts of the @webpack team, nowadays it has sensible defaults and it isn't as tough to manage as a few years ago.
End of conversation
New conversation -
-
-
the convention used to be having separate test and source directory, now it's collocated test files. If tools dont adapt they will be enforcing a convention that's no longer widely aggreed.
-
Oh, me and a lot of people still have separate folders...
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.
he/him 