6 ms·

JavaScript isn’t the hero we wanted, but TypeScript is the hero we need.

by dfee 6y ago

desert_boi 6y ago
with ESLint and Prettier on top.
- slimsag 6y ago
  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.
  - eckza 6y ago
    My god, I love Elm.
  - acid__ 6y ago
    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.
    - Kovah 6y ago
      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.
  - felbane 6y ago
    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...
vorpalhex 6y ago
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).
- jolux 6y ago
  > 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”?
- rumanator 6y ago
  > 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?

JavaScript isn’t the hero we wanted, but TypeScript is the hero we need.

by dfee 6y ago

JavaScript isn’t the hero we wanted, but TypeScript is the hero we need.

desert_boi 6y ago

with ESLint and Prettier on top.

slimsag 6y ago
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.
- eckza 6y ago
  My god, I love Elm.
- acid__ 6y ago
  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.
  - Kovah 6y ago
    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.
- felbane 6y ago
  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...

vorpalhex 6y ago

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).

jolux 6y ago
> 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”?
rumanator 6y ago
> 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?