Comments on: Dare’s $100

by: Dan

Mon, 20 Mar 2006 15:22:58 +0000

I'd love to have something this as an option over the JS SAX interface:

The ElementTree iterparse Function

It will be standard python soon so the Iron Python folks should get right on it ;-)

by: Robert Sayre

Mon, 20 Mar 2006 14:42:33 +0000

Right. I want other ways to use XML that aren’t DOM, and I don’t see what this has to with JSON.

by: Harry Fuecks

Mon, 20 Mar 2006 13:43:56 +0000

I don’t understand the argument. Most people use JSON, so we should live with DOM forever?

Sorry - was being too terse. In verbose form that should have read;

Hardly anyone is using XML in AJAX[. Instead they're using ] JSON and other approaches...

So we're in agreement – approaches like JSON and similar (e.g. Google suggest simply returns some Javascript which, when evaled, executes a local callback function) are preferable as you get immediate access to your data structures, vs. fighting with DOM. There's probably also a performance gain.

by: Robert Sayre

Mon, 20 Mar 2006 13:25:21 +0000

Hardly anyone is using XML in AJAX – JSON and other approaches...

I don't understand the argument. Most people use JSON, so we should live with DOM forever?

by: Harry Fuecks

Mon, 20 Mar 2006 11:00:21 +0000

That $40 on XML and browser seems like money wasted. Hardly anyone is using XML in AJAX – JSON and other approaches (The AJAX response: XML, HTML, or JSON?). The point there is XML's platform independence has no value to a browser, given cross domain restrictions – AJAX is about specific relationships between a Javascript client and a single domain name (i.e. a single server-side platform).

Better take that $40 for fixing browser HTTP auth and supporting logoffs.

In fact looking at Dare's spending plan, it's not pretty.

The next $30 would be better spent on teaching developers the details of HTTP. .NET already has HTTP support. Let's not hide it all behind a bunch of "keep developers dumb" APIs

Then that $20 – how about spending that on introducing some flexible data types instead - the sort that allow you easily represent "ad-hoc" XML structures, for example.

Finally that $10 – well perhaps this could go to adding E4X to IE?