Cart
[Home] [By Thread] [By Date] [Recent Entries]
1/29/2002 7:09:21 PM, Ramesh Gupta <ramesh@e...> wrote: >eNode is pleased to announce a powerful and flexible markup language for >describing user interfaces of web applications with real functionality. > >The language is designed to describe complex user interfaces and related >collections of objects as completely as possible using an XML-based syntax. This is interesting, but I'm not quite sure what to make of it. "A declarative XML-based language for developing Java applications" is a capsule description that seems to cover it. The vision described on the web page sounds a bit like the use case for Curl, but it leverages more of the "Web" (broadly defined, please don't flame me!) infrastructure such as XML and Java. But unlike Curl and DHTML it doesn't run in the browser, but can be used to access objects/data over the Web ... Help me out here with the "vision thing." And how do you expect developers to distribute their infastructure for their XALT applications if thay don't run in the browser? Also, Google has very little information on eNode.com; can you say any more about the company, its resources, its backers ...? This could be another historic showdown between "worse is better" (dynamic HTML) and "better is better" (Curl or eNode/XALT with their presumably better visuals, performance, exploitation of the desktop CPU, etc.). I'm getting old and crotchety and have vowed to never again bet against "worse is better" in the marketplace, but I'm hoping to be wrong one of these times. I would tend (after a very cursory reading) tend to believe that the eNode approach is more likely to succeed than Curl because it leverages all the lessons that Sun has learned about making client-side Java work better, leverages XML and the DOM, and can more plausibly claim to be standards-based. Anyway, this is all just an invitation to discuss these issues; I have no strong opinons or vested interests here.
|
