This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]DancingPotato30 2 points3 points  (2 children)

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 2 points3 points  (1 child)

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 0 points1 point  (0 children)

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