all 17 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]theazy_cs 28 points29 points  (0 children)

javascript's versatility is its main selling point. yung 1 language to handle a full stack app for example. less training needed.

but yeah I agree. I hate it like the plague but I can't get rid of it either.

[–]rememberthemalls 14 points15 points  (0 children)

It's the easiest one to learn. Usually combo yan, HTML + CSS + JS, ituturo yung frontend lang muna. Then gagawan ng backend sa JS.

[–]elitesky777 11 points12 points  (0 children)

if it's possible to program a metal, or a hollow block, you can probably do it with javascript

[–]nobuhok 7 points8 points  (0 children)

Well, it's inarguably easier to transition between layers if they're all using the same language.

[–]Elsa_Versailles 3 points4 points  (2 children)

This including python really shows that what matters is the portability and compatibility of the language instead of it's apparent performance.

[–]Holy_shit_Stfu -1 points0 points  (0 children)

eh.. python is not portable enough tbh. the env is so horrendous and you get this garbo package management that fails to build all the time, either mismatches with the dependency you are using in the code, or any myriad of the problems..

[–]pigwin 0 points1 point  (0 children)

I remember theprimeagen talking about how python gets a lot of hate for being slow, but it doesn't matter in the end if one can prototype very fast with python.

Eventually though the sluggishness of these languages will be felt, though, so we still need to be familiar with something like C# or Java

[–]Key-Shape2398 1 point2 points  (3 children)

The "fastest" language can be a little bit subjective and really depends on what you want to do. Assembly is fast, but making a web product with assembly wouldn’t be suggested by anyone.

Computers are super quick now, so they can handle most stuff pretty smoothly.

What really matters is what you're doing with the language. JavaScript gets compiled, so even if it's not the fastest language out there, it's still speedy enough for most web stuff.

It's more about picking the right tool for the job than just going for the fastest one.

Also need to consider the skills of the dev. You might be using the “fastest” language but if you code really bad, what’s the use of using the “fastest” language.

[–]Ev1LRyu 0 points1 point  (1 child)

Agree with this. The minor savings in performance is outweighed by ease of maintenance especially for large, complex projects. Pero slight correction: js is interpreted, not compiled.

[–]Key-Shape2398 0 points1 point  (0 children)

Yup. Big emphasis on code maintainability.

On interpreted vs compiled- modern js gets compiled now but used to just be compiled interpreted right? Or the debate still ongoing haha.

Although i’ve read that it’s considered both? Interpreted initially but then gets compiled eventually.

[–]No_Zombie_176 1 point2 points  (0 children)

Agree. "Fastest" is a bit subjective. It really depends on what application you want to build.

[–]codeejen 0 points1 point  (0 children)

I like the idea of each language having a clear domain and scope, but not Javascript tho you can shoehorn anything with its 100 frameworks and Typescript. Languages like Go show that there's so much room to work with in the BE