Hacker News Reader

Comment by matzipan | Hacker News Reader

Fortunately, our team is made up of both designers and programmers. In fact, our lead programmer is also our lead designer (small team).

It is true, you can make really awesome apps with HTML5/CSS. We, ourselves, are doing the same thing.

We are bringing to attention some new concepts that we think have not been taken into acount into HTML simply because HTML features have just been stacked together and it HTML simply evolved into something it was not intended to.

On the other hand, the HTML5 completion date has been announced as 2020. Do you really think HTML5 will still suit the needs of the web then? It should probably be HTML7.

View on HN

> HTML5 completion date has been announced as 2020

CSS2.1 became a W3C Recommendation on 7 June 2011. People have been using the HTML5 doctype for years now, never mind quite a few of the features. Arguing that the W3C is slow to standardise things is preaching to the choir, but CSS3 or HTML5 not being standards has had no impact on the ecosystem that's been using -moz-border-radius since Firefox 1.0. (that's 8 years ago. There are web designers that aren't twice that age out there).

Also, sorry to be that person, but isn't SASS/SCSS (edit: and calc()) "good enough"™. The problem with XML files not rendering nicely in the browser is not anywhere near as important to developers as XML not supporting a way of plugging in JavaScript as HTML does with <script>.

Edit: And lastly, what's wrong with XSL? It's got XPath, which as much as people love to dump on it, is not that bad. And you get HTML with all the bells and whistles as an output.

>using -moz-border-radius since Firefox 1.0. (that's 8 years ago. There are web designers that aren't twice that age out there).

...web designers who had no idea -moz-border-radius existed until recently. Thanks, W3Schools!

Well, the XML is just the template AXR uses to generate it's object model. Everything that happens after there is not upto XML anymore. It is all about HSS goodness.

The 2022 date is no longer relevant, see: http://wiki.whatwg.org/wiki/FAQ#What.27s_this_I_hear_about_2...

Whilst there may very well be many advantages to your approach, please don't misrepresent the competition.

Haven't heard the news. I guess they recieved a lot of bad feedback on that.

Yeah, but do you really feel like this W3C standardising process is really benefiting anybody? I know creating a standard involves a lot of work, but I don't like it.

SASS/SCSS has nothing to do with HSS. SASS compiles intro regular CSS. HSS is standalone and can only be run in AXR supporting environments.

HSS could be compiled into CSS.

LESS stays LESS until it's compiled by a javascript shiv into CSS.

If you're going to build out a browser plugin, you're going to have to plug into the built-in styling system to translate your HSS into CSS or some internal representation of CSS. Unless you write your own browser from scratch, they are all built internally to support CSS and will require drastic internal change (beyond what a plugin can do) to natively support something like HSS without translating to CSS.

No sane browser vendor would do such a deep integration of CSS. Doing such a thing would be bad software design.

The AXR Prototype was designed to be the same core implemented through lots of different wrappers (desktop, browser, you name it), much like webkit.

We are planning to fork a popular browser in order to prove this is actually do-able. We have discovered it's not as hard as it seems.

Reply on news.ycombinator.com