175
Why do they keep making new languages
(lemmy.stonansh.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Aug 2023
175 points (94.0% liked)
Programming
17671 readers
84 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 2 years ago
MODERATORS
Because people don't want to admit that JavaScript will be the only programming language in the future and that resistance is futile.
Yeah but javascript has 473 popular frameworks and counting, and the churn is immense. Your codebase becomes out of date before you've finished writing it.
And the debugging?! I'll try to finish writing this paragraph despite the uncontrollable twitching. Let's just say that javascript is the kind of language that looks at your car with a missing left front wheel and says "let's go", while your IDE whispers "Yes, but maybe just don't turn right. Certainly don't turn right fast, unless you want to of course."
Who said you need to use a framework? vanilla-js.com Yes, debugging is a pain and the language fails in many aspects and I also hate it but I also realized it is the future and everything else will fade away.
I can't believe I'm about to say this, but if JavaScript is the future, then I'm going to stick to my old fashioned COBOL.
Gotta admit, I love how cheeky that is.
I'm somewhat on the fence about this. Having the frameworks provide some of the functionalities built-in was pretty nice. Having some of that structural opinion to work off of meant I'm not wasting time just figuring out how to architect the whole thing from scratch. At the same time, I would prefer to stick with vanilla, so it's less overhead and perhaps, the debugging would be more straight-forward. Trying to decipher React's large error messages was irritating at best.
That's not really the case anymore, it was back at around 2015 for a few years when nodejs blew up and we realized that JS is capable of much more than we initially thought.
We threw a thousand different things to the wall and a few frameworks stuck. Today the ecosystem is pretty stable, especially of you choose a popular framework like React or Angular.
Exactly right.
Ahaha fair point :D
Ngl I thought you were meme-ing and was sad to see you downvoted.
That's kind of the "problem" of JS. We can do memes like that but the truth is that it is taking over everything.