Wow - 8 down votes and it still reached the popular links. Maybe DZone needs to re-think their algorithm for what "popular" really means.
On the topic of the article though, you can't ignore Google Chrome. The article goes on about the JS interpreter supplied with WebKit, but fails to mention that Chrome uses the V8 JS engine instead. Simply from a testing and QA point of view, if Chrome gets big enough, it can not be ignored.
The idea behind this is interesting. I'm not sure what is the state of WebKit, but currently applications can be developed on top of XULRunner and Gecko using JavaScript and this is something interesting because it is easier to develop UIs using HTML/CSS. After all, the current fashion in desktop UIs is to use declarative language + separate styling of the elements. I have to try this out:)
Comments
nick.read replied ago:
Wow - 8 down votes and it still reached the popular links. Maybe DZone needs to re-think their algorithm for what "popular" really means.
On the topic of the article though, you can't ignore Google Chrome. The article goes on about the JS interpreter supplied with WebKit, but fails to mention that Chrome uses the V8 JS engine instead. Simply from a testing and QA point of view, if Chrome gets big enough, it can not be ignored.
drmr replied ago:
The idea behind this is interesting. I'm not sure what is the state of WebKit, but currently applications can be developed on top of XULRunner and Gecko using JavaScript and this is something interesting because it is easier to develop UIs using HTML/CSS. After all, the current fashion in desktop UIs is to use declarative language + separate styling of the elements. I have to try this out:)
Voters For This Link (8)
Voters Against This Link (12)