How long would it take us to recognize the web browser is too much flawed as an application platform?
IMHO all of we should strive to let HTML (and perhaps HTTP) behind and create a sound platform for internet application distribution,
one where I don't have to spend so many hours suffering for a old IE/firefox/ bug or the poor support of javascript programming tools,
one where I don't have to worry about security policies tinkered from a platform designed for content, not applications.
You could say that it would never catch up because of the widespread adoption of browsers (did you notice the name? browser!),
but then we are condemned to suffering ridioulous 'innovations' (AJAX ? come on! smart terminals were a long time ago,
a secure web browser?! why should I bother more about it than my OS security? After all, is my application platform ).
It's just a matter of when do we want to do it, because you just can't continue stretch it's limits ad infinitum.
We have payed too much for the sweetness of application distribution offered by the web. It just doesn't make sense anymore.
Integrated data formats unify the proprietary toolkits. Backbase stores all of its layout and event passing information in its own XML format; JackBe uses JavaScript to store data. The open source toolkits have some amount of unification, but they are often more open and cacophonous. True cohesion isn't common except perhaps in the case of Google; its format is fairly inscrutible because it was translated from Java.
among other calamities, i mean, confused thoughts.
In what sense Backbase, JackBe and Tibco are integrated if each one of them has it's own propietary UI definition language?
In the other hand, I can tell you that JackBe is not the way to go, at least you are giving up using other libraries, e.g. Protoype, which breaks the JBTable. And believe me, JackBe widgets are not worth the bucks.
Slashdot Mirror
How long would it take us to recognize the web browser is too much flawed as an application platform?
IMHO all of we should strive to let HTML (and perhaps HTTP) behind and create a sound platform for internet application distribution,
one where I don't have to spend so many hours suffering for a old IE/firefox/ bug or the poor support of javascript programming tools,
one where I don't have to worry about security policies tinkered from a platform designed for content, not applications.
You could say that it would never catch up because of the widespread adoption of browsers (did you notice the name? browser!),
but then we are condemned to suffering ridioulous 'innovations' (AJAX ? come on! smart terminals were a long time ago,
a secure web browser?! why should I bother more about it than my OS security? After all, is my application platform ).
It's just a matter of when do we want to do it, because you just can't continue stretch it's limits ad infinitum.
We have payed too much for the sweetness of application distribution offered by the web. It just doesn't make sense anymore.
The complete stuff has two partsu rce=NLC-SR2006-08-01?source=NLC-SR2006-08-01
http://www.infoworld.com/reports/31SRajax.html?so
The missing part is titled "Proprietary AJAX toolkits: The other side of the coin", where he writes
Integrated data formats unify the proprietary toolkits. Backbase stores all of its layout and event passing information in its own XML format; JackBe uses JavaScript to store data. The open source toolkits have some amount of unification, but they are often more open and cacophonous. True cohesion isn't common except perhaps in the case of Google; its format is fairly inscrutible because it was translated from Java.
among other calamities, i mean, confused thoughts. In what sense Backbase, JackBe and Tibco are integrated if each one of them has it's own propietary UI definition language?
In the other hand, I can tell you that JackBe is not the way to go, at least you are giving up using other libraries, e.g. Protoype, which breaks the JBTable. And believe me, JackBe widgets are not worth the bucks.