AXR: A better(?) alternative to HTML+CSS
1–10 of 65 posts
Re: AXR: A better(?) alternative to HTML+CSS
#2I don't think AXR is the solution to rendering engines not keeping the same pace. It's hard to have competition and at the same time wish I didn't have to check my CSS in Trident, Gecko, Presto and Webkit.
Re: AXR: A better(?) alternative to HTML+CSS
#3I don't think XML is any better than HTML for presentation. In fact, HAML is way better, and much more powerful. In the same way I don't see why to use HSS when we have SASS/SCSS, Jade, Less...
Re: AXR: A better(?) alternative to HTML+CSS
#4Won't we have the same problem once it's implemented in browsers? They implement different things, in different ways. And XML does induce a lot of overhead compared to other ways to share data. I'm not against changing the way we code, but it has to be well thought out.
Re: AXR: A better(?) alternative to HTML+CSS
#5Show me the CODE! Where is it???
If you are trying to revolutionize and disrupt existing languages/syntaxes, show how yours is better! Side-by-side on the front page is best. Look at CoffeeScript's site.
Re: AXR: A better(?) alternative to HTML+CSS
#6Show me the CODE! Where is it??? If you are trying to revolutionize and disrupt existing languages/syntaxes, show how yours is better! Side-by-side on the front page is best. Look at CoffeeScript's site.
The presentation on the front page has comparisons.
Re: AXR: A better(?) alternative to HTML+CSS
#7Show me the CODE! Where is it??? If you are trying to revolutionize and disrupt existing languages/syntaxes, show how yours is better! Side-by-side on the front page is best. Look at CoffeeScript's site.
The presentation on the front page has comparisons.
I had to scroll 12 slides until I reached the first snippet.
Re: AXR: A better(?) alternative to HTML+CSS
#8Won't we have the same problem once it's implemented in browsers? They implement different things, in different ways. And XML does induce a lot of overhead compared to other ways to share data. I'm not against changing the way we code, but it has to be well thought out.
Won't we have the same problem once it's implemented in browsers?
Indeed. This faces an uphill battle to get critical mass and once browser makers decide to support it natively there's going to be pressure to roll it into the standards process.
Re: AXR: A better(?) alternative to HTML+CSS
#9I don't think XML is any better than HTML for presentation. In fact, HAML is way better, and much more powerful. In the same way I don't see why to use HSS when we have SASS/SCSS, Jade, Less...
These abstract metalanguages are still somewhat limited by the underlying base of HTML and CSS. Some things simply can't be accomplished with CSS, no matter how many SASS macros you write (e.g. reparent an element), or you'll just end up with lot of code to do tasks which would be simple with HSS.
I believe that point of AXR is to replace this underlying base, with something more suitable for web applications. You could still use a metalanguage on top of it (maybe with some tweaking) - you can write XML using HAML anyway.
Re: AXR: A better(?) alternative to HTML+CSS
#10I don't understand why they are implementing the prototype in C++. If you built it in JavaScript, any modern browser could load their alternative markup and render it through some sort of fallback (I would expect HTML5+CSS+Canvas+SVG all put together provide enough functionality to render content expressed in their new language(s)).
Building it in C++ basically guarantees that nobody will be able to use it, ever, because it provides no support for older browsers and no support for older HTML-oriented technology like search engine spiders.