One reason why javascript is actually bad from your own personal experience

>one reason why javascript is actually bad from your own personal experience
>you dont need the tip
i'm waiting

having both undefined and null is like having the worst sort of cancer you can possibly imagine

>php exists
>people uses javascript

After using it proffesionally for a while all of the weird quirks and bad behaviours sort of fade away

async might be a pain to deal with some times but it's always pretty easy to solve

So about which part do you want to something?
The language itself?
The browser environment?
The community?
I can't work over the implementations, as they are usually in good quality, unlike, say, Python.

>php does what javascript does

>shit exist
>people use piss

if (foo() === true) {
....
}

real js code I wrote today

50mb sites.
Javascript on desktop applications.
www.alex.js

I meant alexjs.com

top zuz

>50mb sites
I am the guy making those currently. You know why? Because I don't care, it's just a job. I come to work, spend my 8 h writing shit code and get my paycheck at the end of the month.

If your site doesn't work with basic HTML I just wont use it.

== vs ===. Only retarded languages have both.

You might as well just kill yourself right now.

I don't give a shit in all honesty

==
reassigning nan and null

what the fuck

100 scripts is an outrageous amount for one webpage

I don't see the problem if function foo() returns a boolean.

...

>if
it's weakly typed, who knows what it might return

RTFM

JS is great if you know how to use it properly. And it's the fastest growing technology right now.

>You know why? Because I don't care
If you cared, you wouldn't be stuck writing javascript.

Wow that's a nice jpg name good job

These things are pretty retarded imho:
var null = ...;
var undefined = ...;

I really like language but this is beyond retarded.