Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] When parsing speed matters (was Re: [xml-dev] No XML Binaries? Buy Hardware)

From: "James Fuller" <james.fuller.2007@-----.--->
To: "Len Bullard" <cbullard@------.--->
Date: 3/5/2007 10:49:00 PM
On 3/5/07, Len Bullard <cbullard@h...> wrote:
> SL is taking care of that with a marketing budget and a zealot at CNet.  XML
> is dull.  It needs to become more animated. :-)  As I said to Rob, people

xml is boring, which is a testimony to its adoption

> post to their interests in XML.  The vast majority of people on XML-Dev
> happen to be database/document wonks which is historically where markup has
> thrived.  I migrated away from that and lo and behold, XML turns out to be a
> marginal choice for some data intensive applications because speed really
> does matter and so does verbosity where it impacts that if it does.  The
> case for binaries in graphics pipelines is said to be secure.  I'm waiting
> to see the results of the working group.

xml importance has to be at the mythical semantic layer......

> If XML hardware can speed up the pipes, that is worth doing, but so far, I
> don't see that happening unless the game console folks decide to do it.  The
> current specialty tasks don't seem to apply from what I can make of this
> thread, and a game environment won't be ubiquitous enough soon enough to
> make XML board commoditization of any value there.  Still, anyone who deals
> with the effects of lag on real-time web-distributed simulations is looking
> for any advance or advantage they can find now that online sims are a fast
> growing business.

agreed, though surely hardware advance will push this future, not software.

> The realization that HTML browsers are slowing down the web is dawning on
> the people who create persistent games.  If the HTML browser is getting in
> the way of faster rendering, that is worth doing away with altogether.  If
> 3D games are the wave of the future for social networks and business online
> work, then HTML starts becoming more marginalized in the GUI.  It takes
> awhile to build up, but eventually someone releases a client that is a good
> 3D GUI but doesn't use HTML for anything significant.

ok, you are starting to open my eyes to this....though people tend to
understand in incremental steps...the problem is that I cant 'see'
going from the 4 hours I just spent making a slightly complicated 2D
html search form validate and return results properly using html, to
coding a full blooded 3d GUI/interface....perhaps I dont have enough
imagination...though I certainely can imagine pain; and I tend to
avoid it.

so 'where are the baby steps'...is there some vestigal markup language
here to lead us to 3d...I doubt it...it will be some 'fad' that brings
us there first (we will call it.....web 3.0 e.g the 3d web...get it,
get it...ugg).

give me some pointers where a perl / sometimes java programmer would
go as a first stop and I will perhaps fill that last slot of time I
still have free for 2007 to 'learn all about 3d'.

cheers, Jim Fuller


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent