News for hackers. Stuff that matters.
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”?