Re: Javascript: Time Traveller From the Year 1962!

[prev] [thread] [next] [lurker] [Date index for 2005/04/10]

From: David Champion
Subject: Re: Javascript: Time Traveller From the Year 1962!
Date: 08:36 on 10 Apr 2005
* On 2005.04.09, in <20050410031801.GB3231@xxxxxxxx.xxxxxxx.xxx>,
*	"Michael G Schwern" <schwern@xxxxx.xxx> wrote:
> 
> I think we're caught in an endless argument here due to the fact that we're
> using "language" differently.  You mean the grammar stripped of all libraries
> and auxillary widgets.  I'm including the libraries and all the auxillary
> widgets and in Javascript's case, the web widgets.  Let's move away 
> from that for a moment because I'm sick of this argument.

What you describe is an implementation of a language.


> The particular JavaScript "hosting environment" which I care about, which is 
> to say a web browser, does have a standard for JavaScript already.  They've

They have a standard binding betweeen JavaScript, a language, and the
native DOM. That's what ECMAScript provides.


> already defined hundreds of functions.  They already have a way to load and 
> eval JavaScript files.  So take that LAST STEP and add an import() method
> to the "hosting environment".  That's all I'm saying.

The hosting environment needs to do that.


> I don't give a crap about the core language, I'm not an embedded systems
> programmer, don't know a damn thing about it and can't comment on it.  All
> I know is high level languages.

You're an embedded systems programmer the moment you start developing in
JavaScript for deployment in web browsers, because web browsers embed
JavaScript. So... humbly I suggest that you should consider giving a
crap.


> PS  What is the term for "the Javascript language plus all the crap needed 
> to use it in a web page?"  I thought that was referred to as the DOM.  DHMTL
> maybe?

DHTML, perhaps, if there is such a term, though as a purist I'd tend
to favor "Javascript hosted by a web browser". As I understand it --
and note that I hate the web, and don't exactly keep up -- the DOM
refers to the structure for representing and manipulating the document
elements within the browser (the "hosting environment"). DHTML specifies
the relationship between HTML and the DOM (how parsed HTML maps into
the DOM) and how they may interact programmatically or through the
user event loop -- which is by way of ECMA bindings when the scripting
language is JavaScript.

-- 
 -D.                          "Neque  porro  quisquam  est qui  dolorem
 dgc@xxxxxxxx.xxx             ipsum quia  dolor  sit amet, consectetur,
 NSIT->ENSS                   adipisci  velit."
 "Quia dolor sit."            -- Cicero, De Finibus Bonorum et Malorum.
There's stuff above here

Generated at 12:00 on 12 Apr 2005 by mariachi 0.52