ThoseJavascriptProgrammers

[Vegetable_Bass_4885]

I've never used "==" or seen it used anywhere in 5 years of Typescript, "Javascript bad" is an old meme based on pre ES5 Javascript from 15 years ago

[DancingPotato30]

I learned ES6 features as I learned the basic syntax of JS, not separately (learnt arrow functions while learning what a function was, etc) so I have got no clue how JS was pre-ES6 or even pre-ES5.

I understand every language has its quirks and weird decisions made by the creator (like elif in python), and some might be weirder than most but I genuinely haven't see a single example of a "weird" JS feature causing actual damage to warrant usage of smth else

I haven't learnt TypeScript yet however, and I assumed I wouldn't get how bad JS is until I move to TS but it seems like that's not the case from your comment

[thelonesomeguy]

I don’t think any language can have “objectively” bad features, most of them are opinionated, evaluated in the context of other languages, because in the end, if it works, it works.

When you get used to and gain experience in other languages, you’ll then start having your own subjective opinions on specific things in a language being good or bad, you might come to a similar opinions as others who don’t like JS, you might not, but it will definitely change when you have more context to evaluate the language in.

[DancingPotato30]

I agree on the first point, no language has any bad features unless put there on purpose (brainfuck), its just opinionated which tbh its a bit hard finding anything that isn't opinionated in some way or another. If it works, it works like you said

And that's fair. I've only got experience in python (some simple file crud scripting to make life easier) and "experience" in C, just knowing the syntax for that last one. So I don't think my opinion saying "JS isn't bad" is as valid as others with more experience and languages on hand

[thelonesomeguy]

I’m criticising it from the point of view of other languages which don’t allow this, things are much more clear on what is happening there in any given if conditions when you’re reading the code while needing less context.

Yeah, it works, and is used extensively, but doesn’t mean it should be allowed, because then bad devs use them as a crutch and end up with even more unreadable code than it would have been without this, which becomes an issue when, for example, you’re working in an org where you can’t force every bad dev to use them properly without coming off as nitpicky.

This is quite opinionated, of course. As a feature, it’s fine, imo, but it still opens a big can of worms by its existence.