......

I mostly use strong typed languages but I understand JavaScript, it's not so hard to use.

What I don't understand is this war between specific languages/OS/whatever shit...we work with tools, those are just tools for us.

Brainfuck: that's a real challenge for me.

There are quite a few WTF things built into javascript, but overall it's not nearly as bad as people make it out to be.

@Glinkis Agree. Not all in JS was bad, it just had it's own quirks like every language.

@Unai oh yeah, do you like a single page websites taking 1gb of ram... Do you?

There is a reason the Tech Giants use Google's Dart, Microsoft's Typescript and Facebook's Flow. There is a reason Google is switching out Python for Go, that Mozilla is replacing C with Rust, and that Facebook used HHVM before PHP7.

The reason is that strong typing scales.

Weak typing is great for quick prototyping, but requires full test coverage to even resemble a stable state... and tests can be kind of weak and crumbly by themselves.

Javascript is a good language to know and use.

For web frontends you have no other options anyway (disregarding wasm), and for every other domain it's the "second best language", the swiss army knife.

But it certainly has flaws, and the lack of a typing system is one of them.

@abhishek9650 Of course I do

@abhishek9650 this happens when you use a browser that hogs RAM and has nothing to do with JS 😁 if your single page website actually requires this much ram that's a coding and efficiency issue not a language one

@bittersweet I don't necessarily agree with this but I see the point. However, TypeScript that you mentioned is great for people who want strongly typed JS (since it's transpiled) and although I use JS on many of my stacks I would never write prod code without typescript. For Python there's MyPy to do a type check, which is pretty nice. JS also works on every platform w/ a huge community, so I think using TypeScript is better than just dumping JS. On a similar note, data science is mostly done in Python right now and that won't be changing anytime soon since it is so well tailored to it. The use of these 2 langs has only grown in the last decade and I think we'll keep seeing a snowball growth (more people join = more dev = better frameworks/modules = more people join)

@woodworks I agree that JS will keep growing — I just wish that instead of adding more transpiling into an already overcrowded toolchain, an effort was made to standardize JS typechecking.

Not necessarily mandatory full static typing (which adds a lot of overhead if you use polymorphism/generics), but a standard syntax for hints/checks is a must for a future ES spec in my opinion.

As long as devs will rip js out of their natural environment (ie Webbrowsers) devs will hate the hell out of it.
JS is best in doing stuff with markup in webbrowsers. When doing such stuff, it's pretty good imo

It does have specific purpose and functionality. That has been grievously perverted by a bunch of kids with a bottle of crazy glue.

@bittersweet I definitely agree, I feel like so many frameworks already have their own flavor of type hinting (like components in react or schema in mongoose) but it's not enough, not standard, and not low level enough... Hopefully a new ES standard will be implemented

@Astatos Heh, and I would have argued for the opposite! Javascript is a fine language, it's the browser which ruins it.

From an old Hacker Test:
000E Ever change the value of 4?
000F ... Unintentionally?
0010 ... In a language other than Fortran?

Considering the existence of JSFuck, I'd guess at it being possible.