The worst thing about the Javascript ecosystem is Typescript.
It was painful watching an experienced dev waste hours tinkering with code, not to craft software features, but to get rid of complaints from Typescript about mismatched types. Then watching as they sit looking aghast at their runtime type errors, in disbelief because transpile-time type safety should have saved them. And the sheer volume of code written... I'd rather they spent the time thinking about what happens at runtime, and thinking about writing well-composed, maintainable code that's self-documenting... Not jumping through syntactical or semantic hoops trying to satisfy some tyrannical software tool with its uphelpful, nonsensical error messages written by people who really shouldn't have been put in a position where they have to write error messages to help other devs.
As I've said elsewhere, my devs are high worth individuals. I pay them a lot. I want high productivity, so the customer's money is spent on crafting the features of their software solutions, not tinkering with the tooling. We develop things once and reuse massively. Typescript would just get in the way of all this. The way we do what we do is to employ properly educated devs who know how to use Javascript expertly to create exquisite business application software, and keep everyone up to date with current best practises and communicating well. Appropriate tools like IDE, linters and formatters look out for us and watch our backs. Code reviews are opportunities to learn and teach. In this way Javascript is made friend, not enemy.
Of course I'll get flamed for this by the True Believers, but I don't care. I do what I do backed up by decades of experience with commercial success. You should carrying on doing what you do and go in peace.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The worst thing about the Javascript ecosystem is Typescript.
It was painful watching an experienced dev waste hours tinkering with code, not to craft software features, but to get rid of complaints from Typescript about mismatched types. Then watching as they sit looking aghast at their runtime type errors, in disbelief because transpile-time type safety should have saved them. And the sheer volume of code written... I'd rather they spent the time thinking about what happens at runtime, and thinking about writing well-composed, maintainable code that's self-documenting... Not jumping through syntactical or semantic hoops trying to satisfy some tyrannical software tool with its uphelpful, nonsensical error messages written by people who really shouldn't have been put in a position where they have to write error messages to help other devs.
As I've said elsewhere, my devs are high worth individuals. I pay them a lot. I want high productivity, so the customer's money is spent on crafting the features of their software solutions, not tinkering with the tooling. We develop things once and reuse massively. Typescript would just get in the way of all this. The way we do what we do is to employ properly educated devs who know how to use Javascript expertly to create exquisite business application software, and keep everyone up to date with current best practises and communicating well. Appropriate tools like IDE, linters and formatters look out for us and watch our backs. Code reviews are opportunities to learn and teach. In this way Javascript is made friend, not enemy.
Of course I'll get flamed for this by the True Believers, but I don't care. I do what I do backed up by decades of experience with commercial success. You should carrying on doing what you do and go in peace.