My point was that JS is so much like C++/C#/Java that you do not really need to learn anything new. If you know any of those languages you can already hack JS.

Ok, but that wasn't my point. I am not under the impression that it would be difficult to learn javascript. The apparent assumption that all developers already know javascript is what is telling.

As to your point, I don't remember the last time I had to think about using '==' or '===' in C++. Semantics differences are huge, I don't care about curly braces and semicolons.

> My point was that JS is so much like C++/C#/Java that you do not really need to learn anything new.

Except Javascript is a prototype based language and the others you mentioned are all object based....but hey they all terminate statements with ; so must be identical I guess.

Of course, the semicolons. Neither assembly nor python use semicolons, so by my logic they must be identical too?

Control flow, method invocations, variables, arrays, boolean logic operators, and general syntax are similar enough that you can look at the JS code and figure out what it is doing.

So I guess by that argument you'd put PHP in that family? ;)

Besides the fact that js is an interpreted dynamic language while the others are statically typed

Syntax yes, semantics no. It is dangerous to lump all those languages together because they look similar.

Compared to web development, those communities you mentioned are very closed to most people. With Javascript, there's no special equipment needed, and you can pretty much just pick it up and go...there's tons of freely-available knowledge in blogs, and open source code to read/get involved with.

Where's the github for assembly line firmware code? I would be very interested in learning more about other non-web-development domains, but it seems like unless you get hired right out of school to program something like cars or satellites, you're pretty much shut out forever.

There are plenty of repositories with code for micro-controllers and non-web related projects, but again, that's not the point. The single quote that "pretty much everyone knows javascript" was the focus of my comment.

Sure, maybe the author meant "pretty much everyone [who we think will be interested in our site] knows javascipt", but that's not what they said, and I don't understand that attitude at all. It's unnecessarily exclusionary, especially when their plan is to host content in a similar way to HN.

Maybe another take on the idea could be to allow anyone to join who could sign in a with a github account that had had at least one accepted pull request on any repository. Easily hacked I guess, but perhaps that would solve the "just Javascript" problem while still serving to boost the average level of tech cred of submitters/commenters.

Surely there would be a way to check this through github's api once there was a username to check against. It sounds like a good idea and it might encourage supporting open source software while avoiding those issues.

But then I guess the downside would be fewer people contributing to your own site.