who came up with JavaScript language syntax?

[Rob R. Ainscough]

What sick saddistic person came up with the JavaScript language syntax? And
was it the same person (or group of people) that came up with the HTML
syntax??

OMG, has no one noticed this hopeless poor choice of language syntax? And
why-o-why is it case sensitive? Is it just a carry over from light weight
parsers? If we can't get out of this nightmare because of compatibility
sake -- where and how is this going to progress to a point of efficiency in
the development cycle?

Does ASP.NET 2.0 remove the need for JavaScript ?

[Gabriel Magaña]

You should read up on the history of JavaScript, it's basically a
long-runnign pissing match between people who thought they knew better than
each other... I'm just thankful it does not look anything like VB (of the
VB6 and before kind)

"Rob R. Ainscough" <ro*****@pacbell.net> wrote in message
news:%2******************@TK2MSFTNGP09.phx.gbl...

What sick saddistic person came up with the JavaScript language syntax?
And was it the same person (or group of people) that came up with the HTML
syntax??

OMG, has no one noticed this hopeless poor choice of language syntax? And
why-o-why is it case sensitive? Is it just a carry over from light weight
parsers? If we can't get out of this nightmare because of compatibility
sake -- where and how is this going to progress to a point of efficiency
in the development cycle?

Does ASP.NET 2.0 remove the need for JavaScript ?

[Bruce Barker]

netscape came up with javascript and its syntax.

its case sensitive because c/c++, perl, python, the unix file system, to
name a few are case sensitive. javascript is the lisp engine with a c like
syntax, and i believe a very simple and easy, but powerfull syntax which
includes associative arrays, dynamic object properties, llamada functions,
closure (all stuff c# doesn't get to version 4.0 - well actually c# 4.0 has
incomplete closure support- probably version 5.0 required). whats so hard
about being case sensitive?

it only flaw is the use of === (exact equals) in case statements.

the asp.net 2.0 support of callbacks, and the next releases support of AJAX
makes javascript more important.

html is a simple implementation of SGML gramar, and as a markup langauage is
pretty simple. the w3c browser dom is basically the xml dom, which was
designed to be easy to use from javascript.

note xhtml unlike html is case senstive.

-- bruce (sqlwork.com)
"Rob R. Ainscough" <ro*****@pacbell.net> wrote in message
news:%2******************@TK2MSFTNGP09.phx.gbl...

What sick saddistic person came up with the JavaScript language syntax?
And was it the same person (or group of people) that came up with the HTML
syntax??

OMG, has no one noticed this hopeless poor choice of language syntax? And
why-o-why is it case sensitive? Is it just a carry over from light weight
parsers? If we can't get out of this nightmare because of compatibility
sake -- where and how is this going to progress to a point of efficiency
in the development cycle?

Does ASP.NET 2.0 remove the need for JavaScript ?

[Kevin Spencer]

> OMG, has no one noticed this hopeless poor choice of language syntax?

I confess. It was me. You see, I had a sad childhood, and was denied the
simple pleasures that most people enjoy in life. In order to get revenge on
a world which was so much happier than I, I concocted this evil language,
and foisted it upon an unsuspecting public. Now, *everybody* has to use it,
and my jealousy is satiated! AH-HA-HA-HA-HA-HA-HA!

--

Kevin Spencer
Microsoft MVP
..Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.

"Rob R. Ainscough" <ro*****@pacbell.net> wrote in message
news:%2******************@TK2MSFTNGP09.phx.gbl...

What sick saddistic person came up with the JavaScript language syntax?
And was it the same person (or group of people) that came up with the HTML
syntax??

OMG, has no one noticed this hopeless poor choice of language syntax? And
why-o-why is it case sensitive? Is it just a carry over from light weight
parsers? If we can't get out of this nightmare because of compatibility
sake -- where and how is this going to progress to a point of efficiency
in the development cycle?

Does ASP.NET 2.0 remove the need for JavaScript ?