this post was submitted on 02 Apr 2024
143 points (98.6% liked)

Programming

17492 readers
37 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

I was talking to my manager the other day, discussing the languages we are using at $dayjob. He kind of offhandedly said that he thinks TypeScript is a temporary fad and soon everything will go back to using JavaScript. He doesn't like that it's made by Microsoft either.

I'm not a frontend developer so I don't really know, but my general impression is that everything is moving more and more towards TypeScript, not away from it. But maybe I'm wrong?

Does anyone who actually works with TypeScript have any impression about this?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] aluminium@lemmy.world 1 points 7 months ago* (last edited 7 months ago) (2 children)

Unpopular opinion perhaps, but I rather have a language that allows me to implement hacky solutions than one that requires me to completely scrap and rearchitect everything.

I for example once had to overwrite a dozen or so of prototype methods in a JS class because the library a we were using just fell apart when doing certain things inside a Shadow DOM - it was a library that was released long before that feature. And completely rewriting huge chunks of code that interacted with that library would have wasted 100s of hours and the end result might have been really akward as well since many other systems are architected around how that one library worked. So instead it was a matter of patching in a few checks and workarounds for shadow dom elements.

And since its extremely well documented why we decided to to that, what these hacks do I don't see an issue with that. Obviously this shouldn't be the modus operandi everytime but its always good to have the option i.m.o. to dig yourself out of a hole.

[โ€“] 0x1C3B00DA@fedia.io 1 points 7 months ago

I would argue that overriding methods on a prototype is not a hack. It's equivalent to overriding super methods in Java classes, but using javascript's prototype-based inheritance instead of class-based inheritance.

But I agree with your main point about choosing a language that lets the developer implement their solutions freely.