News for hackers. Stuff that matters.
Re:The creeping scourge of tooling config files in project r... by jolux on Wednesday August 05, 2020 @10:01PM (#24067488)
I tend to see a glut of tooling as a sign that a language has serious design flaws, as most important things should be done by the compiler, but I’d rather have JavaScript with proper tooling and types than nothing at all.
Re:The creeping scourge of tooling config files in project r... by dfee on Wednesday August 05, 2020 @10:15PM (#24067568)
JavaScript isn’t the hero we wanted, but TypeScript is the hero we need.
Re:The creeping scourge of tooling config files in project r... by vorpalhex on Thursday August 06, 2020 @10:19AM (#24071090)
JS is a great language for it's intended purposes but I still can't get onboard the TS train. Adding types post-hoc has never improved a codebase that I've seen but it has caused a lot more bad patterns to show up.

Simplicity is a virtue (at least sometimes).

Re:The creeping scourge of tooling config files in project r... by rumanator on Friday August 07, 2020 @08:25AM (#24081088)
> JS is a great language for it's intended purposes

Which part of JS, as a programming language, do you see as great or even adequate when compared with contemporary programming languages?

> Adding types post-hoc has never improved a codebase that I've seen but it has caused a lot more bad patterns to show up.

That assertion makes no sense. I mean, all TypeScript does is impose arbitrary sanity checks on a programming language which is plagued for not having any. Where do you interpret the addition of sanity checks as a source of problems?

Re:The creeping scourge of tooling config files in project r... by jolux on Thursday August 06, 2020 @03:17PM (#24074438)
> Adding types post-hoc has never improved a codebase that I've seen but it has caused a lot more bad patterns to show up.

I mostly meant that I do all my greenfield JS dev using TypeScript. Out of curiosity, what bad patterns have you seen caused by adding types “post-hoc”?

Re:The creeping scourge of tooling config files in project r... by desert_boi on Wednesday August 05, 2020 @11:38PM (#24067928)
with ESLint and Prettier on top.
Re:The creeping scourge of tooling config files in project r... by slimsag on Thursday August 06, 2020 @12:54AM (#24068232)
also don't forget:

- .eslintrc.json to configure ESLint

- .prettierignore because it tries to format package-lock.json

- prettier.config.json

- npm/yarn and package.json + node_modules

- .nvmrc to pin your node version

- storybook

- renovate to update dependencies

- .editorconfig to ignore node_modules

- mocha for testing and .mochaarc.js

- stylelint and .stylelintrc.json + .stylelintignore

And maybe throw in Jest, tsconfig.json, a gulpfile, and some other stuff.

Re:The creeping scourge of tooling config files in project r... by acid__ on Thursday August 06, 2020 @03:28AM (#24068851)
Maybe it’s just because I was raised on this ecosystem, but in my opinion the sheer amount of incredible functionality you get from all this tooling (at the low price of $0!) is worth 10-15 set-and-forgot files that don’t even show up when you type ls.
Re:The creeping scourge of tooling config files in project r... by Kovah on Thursday August 06, 2020 @04:10AM (#24069023)
While I totally agree that the functionality of most tools is really impressive, this doesn't mean that the current standard of dropping 5 new config files into root for a tool is the best way to handle this. There are ways to do better. It seems that the maintainers of those tools just don't care.
Re:The creeping scourge of tooling config files in project r... by felbane on Thursday August 06, 2020 @01:35AM (#24068391)
Your comment makes me extremely happy that I haven't needed to deal with anything written in Node. This would drive me absolutely bonkers.

Hell, I thought Flask's root directory was getting a bit fluttery with .gitignore, .venv, .flaskenv, __pycache__, and requirements.txt...

Re:The creeping scourge of tooling config files in project r... by eckza on Thursday August 06, 2020 @01:54AM (#24068453)
My god, I love Elm.