Earlier quoted context omitted.
At that point sir you would have no job. Your job is logic safety
That's why I test the code and solve the logical issues? The joke was that the language would be smart enough to catch the less obvious stupid mistakes instead of obvious to solve type bugs.
Just Say No to JavaScript
61–70 of 86 posts
Re: Just Say No to JavaScript
#62Re: Just Say No to JavaScript
#63This kind of rant, culminating in a hackneyed "created in a week" insult, usually comes from backend developers who jumped into frontend work thinking it was a silly little thing that could be mastered in under an hour, discovered that it was a whole separate field, and still failed to adjust their priors. This time it comes from a "former Delphi product manager" turned clickbait writer. I just hope that my visit wit…
Re: Just Say No to JavaScript
#64Earlier quoted context omitted.
he suggests using typescript, how do you know he didn't use typescript to generate the JavaScript that was used?
not relevant to the inconsistency
Re: Just Say No to JavaScript
#65Re: Just Say No to JavaScript
#66Types are definitely useful in the fight to 'make invalid states impossible', but this rather overstates the case. They go only a very little way in documenting intent.
Re: Just Say No to JavaScript
#67JavaScript is a very capable language. It has better functional programming support than Java and Python. It has fewer footguns that C++. You can start with a scrappy prototype then gradually add type-checking later. Of the mainstream languages, it's actually one of the better ones!
Sources - or just an opinion stated as fact?
Re: Just Say No to JavaScript
#68I was disappointed to read this is just a "Use TypeScript" instead. Look, you can hot glue and tape all the types you want, but it is still JavaScript. No amount of compiler-enforced comments is changing that.
> it is still JavaScript Yes, it's still one of the most performant languages around, so that's a good thing right?
Re: Just Say No to JavaScript
#69Re: Just Say No to JavaScript
#70This is a plea to use TypeScript instead of JS. Why not. Strong typing is certainly great. But the reason I don't use TypeScript isn't any of those listed: it's because it needs a compilation step, and I don't want that.
That's such a weird requirement, maybe because I'm used to writing Go code in my day job. I work on some React webapps on the side and there's no way I would miss on TS, typing is just the only way to write code that you can actually refactor. Granted you get some of TypeScript safety for free thanks to `// @ts-check` and friends, but it's the bare minimum.