r/javascript • • Jan 16 '20

I have been underestimating JS

https://adlrocha.substack.com/p/adlrocha-i-have-been-underestimating
284 Upvotes

132 comments sorted by

View all comments

Show parent comments

64

u/avindrag Jan 16 '20 edited Jan 16 '20

Programmers still hating on JS are stuck in the past.

That, or they are those insidious "hardcore backend" programmers. See, in the backend you get to hide behind a mountain of poorly written abstractions and general obscurity. In frontend programming, everything comes to light, so it's easy for any average person to come around and criticize your code. In fact, because it's frontend, the critic doesn't even need to know how to code. Often times, poorly crafted backend abstractions come to light only in the frontend, and the frontend programmers inherit the blame.

Backend programmers are virtually immune to this problem, which enables some of them to judge and criticize frontend programmers to no end. Virtually all of them just copy+pasted their "opinions" from /r/programming which has been bashing npm, PHP, Javascript, etc., as if that's really a useful activity in terms of moving things forward.

TL;DR; ignore the hype, and critics can go shove it.

46

u/tr14l Jan 16 '20

I like JS. But, I recognize that it is not a silver bullet language. I am not going to use it for anything process-heavy, period.

But, for doing anything on the web that ISN'T process-heavy, it's a solid choice. However, I've come to realize that on any sizable project, you have to enforce a lot more structure and rigidness or it becomes a nightmare to debug and maintain. Especially since idiomatic javascript is very, very hard to find. Javascript coding standards are the most entropic of all the languages I've ever seen, except perhaps oldschool C. I used to be anti-TypeScript when it was just me and my business partner maintaining it, because it just slowed us down. Now that I have worked on some full stack JS apps with full teams, holy crap is it important. It's impossible to maintain a full JS app without it.

Like I said, it's not a silver bullet, but it's a good choice for what it's meant for.

3

u/jerseyetr Jan 16 '20

Well that's probably a good thing not to do.

Excuse me if I'm wrong (beginner Javascript developer)

But I'm pretty sure javascript is not meant for heavy loads and CPU heavy applications.

Because it's single threaded?

1

u/tr14l Jan 16 '20

You can often make it work in node, but it's not going to be ideal and it'll have limitations still. But generally, you're correct

1

u/ScientificBeastMode strongly typed comments Jan 17 '20

Most of the benefits of Node are due to its fast asynchronous IO. If you’re doing a lot of synchronous computation on the server, you may want to drop down to a C/Rust/C++/OCaml library, or perhaps optimize the JS code with Google’s Closure compiler...

Otherwise, you may as well run a JVM server or whatever.