Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #22799 > unrolled thread

Re: JavaScript unfairly blamed?

Started byDoc O'Leary <droleary@8usenet2013.subsume.com>
First post2014-01-26 11:26 -0600
Last post2014-01-26 19:43 +0100
Articles 2 — 2 participants

Back to article view | Back to comp.lang.javascript

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: JavaScript unfairly blamed? Doc O'Leary <droleary@8usenet2013.subsume.com> - 2014-01-26 11:26 -0600
    Re: JavaScript unfairly blamed? Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-01-26 19:43 +0100

#22799 — Re: JavaScript unfairly blamed?

FromDoc O'Leary <droleary@8usenet2013.subsume.com>
Date2014-01-26 11:26 -0600
SubjectRe: JavaScript unfairly blamed?
Message-ID<droleary-A8DAA1.11260426012014@news.eternal-september.org>
In article <DOM-20140126091248@ram.dialup.fu-berlin.de>,
 ram@zedat.fu-berlin.de (Stefan Ram) wrote:

>   Douglas Crockford wrote:
> 
> |The API Of the browser, the Document Object Model (DOM) is
> |quite awful, and JavaScript is unfairly blamed.
> 
>   What's so awful about the DOM?

I don't think much about it but, really, the DOM *is* essentially a 
lowest common denominator representation.  I mean, in what other OO 
design would you mediate almost all object access via something like 
document.getElement...?  Where the HTML hierarchy is flattened to most 
everything being a single type of node?  It is a very generic, 
data-centric representation of a page.

-- 
iPhone apps that matter:    http://appstore.subsume.com/
My personal UDP list: 127.0.0.1, localhost, googlegroups.com, theremailer.net,
    and probably your server, too.

[toc] | [next] | [standalone]


#22804

FromThomas 'PointedEars' Lahn <PointedEars@web.de>
Date2014-01-26 19:43 +0100
Message-ID<1877538.4En7Rhr0HQ@PointedEars.de>
In reply to#22799
Doc O'Leary wrote:

> In article <DOM-20140126091248@ram.dialup.fu-berlin.de>,
>  ram@zedat.fu-berlin.de (Stefan Ram) wrote:

It's attribution _line_, not attribution novel.

>>   Douglas Crockford wrote:
>> 
>> |The API Of the browser, the Document Object Model (DOM) is
>> |quite awful, and JavaScript is unfairly blamed.
>> 
>>   What's so awful about the DOM?
> 
> I don't think much about it but, really, the DOM *is* essentially a
> lowest common denominator representation.  I mean, in what other OO
> design would you mediate almost all object access via something like
> document.getElement...?  Where the HTML hierarchy is flattened to most
> everything being a single type of node?  It is a very generic,
> data-centric representation of a page.

ACK.  Probably because there are no pages.

-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.javascript


csiph-web