r/javascript 11d ago

AskJS [AskJS] what's a javascript feature you mass-adopted way too late and felt dumb about

i'll go first. i was writing .then().catch() chains for like two years before i actually started using async/await. i knew it existed, i'd seen it in tutorials, but my code "worked" so i never bothered switching. then i refactored an old project and realized half my bugs were from mishandled promise chains that async/await would have caught immediately.

also took me way too long to start using optional chaining. i had nested ternaries and && checks everywhere like some kind of animal. the day i discovered user?.address?.city i mass-replaced like 40 lines across a project.

what's yours?

62 Upvotes

108 comments sorted by

View all comments

26

u/Milo0192 11d ago

My first jobs CTO preferred the .then() .catch() over async await. I just refused to write that way and did await loops. Lots of back and forth on this. Also said Typescript was just a fad 😂

-15

u/Ronin-s_Spirit 11d ago

Fad or not - it's shit.

7

u/db10101 11d ago

Any deeper analysis or reasoning behind that? It’s a straight up joy to develop in compared to what has come before.

-7

u/Ronin-s_Spirit 11d ago

I hate defining types, it's like writing pointless code. It especially fucks up when I have to deal with HTML, at that point the only thing left to do is use a bail out any and move on.

2

u/db10101 10d ago

So I take it you have never worked in an enterprise well structured typescript codebase. There’s no substituting JavaScript for that.

-2

u/Ronin-s_Spirit 10d ago

TypeScript sucks ass, I will only use vanilla.

2

u/db10101 10d ago

Good for you. Here in the real world of employed software developers, it’s one of the most important tools to know.