Daniel Glazman
glazman.org · Personal blog · on HN since 2010
Daniel Glazman, a web standards figure and CSS working group co-chair, writes about the open web, CSS parsing and browser tooling.
What HN saysHN links it for his call to action on WebKit and vendor prefixes, his JSCSSP CSS parser, and his Quaxe project.
22HN people shared it
6linked it in comments
21stories submitted
182story points
8 years agolast shared
2010people per year2026
Most-shared posts
- 1The Open Web Needs You Now3 people · 107 points · first shared 2012 · 60 comments on HN
- 2Daniel Glazman: WebExtensions v3 considered harmful2 people · 24 points · first shared 2019 · discussion on HN
- 3Announcing WebBook Level 1, a new Web-based format for electronic books2 people · 8 points · first shared 2018 · discussion on HN
- 4Inventory and Strategy2 people · 4 points · first shared 2016 · discussion on HN
- 5Call for Action: The Open Web needs you now2 people · 2 points · first shared 2012 · discussion on HN
- 6Announcing Quaxe, native desktop and mobile apps from html5 and Haxe2 people · 2 points · first shared 2014 · discussion on HN
- 7IBooks Author analysis by the co-chairman of the CSS Working Group1 people · 13 points · first shared 2012 · 5 comments on HN
- 8The open web needs you *now* (Webkit the new IE6?)1 people · 7 points · first shared 2012 · 6 comments on HN
- 9Google, BlueGriffon.org and blacklists1 people · 3 points · first shared 2016 · 1 comments on HN
- 10Daniel Glazman joins Samsung Open Source Group1 people · 3 points · first shared 2013 · discussion on HN
- 11Blaming CSS WG is too easy1 people · 3 points · first shared 2012 · discussion on HN
- 12All words ending in -ism are bullshitism1 people · 1 points · first shared 2014 · discussion on HN
- 13This paragraph should not be green because document is parsed as xml1 people · 1 points · first shared 2011 · discussion on HN
- 14Mozilla Office1 people · 1 points · first shared 2010 · discussion on HN
- 15A few facts about France for 2012 american tourists1 people · 1 points · first shared 2012 · discussion on HN
What HN people wrote when they linked it
paulirish · 2011-09-18
Nice work. I like how it all stays declarative in the CSS too.
I would recommend outsourcing your parsing though. It's a tough job and things like CSS hacks can really take your regexes for a loop.
I'd recommend trying out http://glazman.org/JSCSSP/ or https://github.com/nzakas/parser-lib/tree/master/src/css which Nicholas uses for CSSLint.
larsiusprime · 2015-06-03
Quaxe looks like exactly that: http://www.glazman.org/weblog/dotclear/index.php?post/AnnouncingQuaxe
There was a big talk about it at WWX 2015 just a few days ago. Looks very promising.
ntakasaki · 2014-08-04
http://www.webmonkey.com/2012/02/webkit-isnt-breaking-the-web-you-are/
Co-Chairmain of the web standards group:
http://www.glazman.org/weblog/dotclear/index.php?post/2012/02/09/CALL-…
Mozilla on the issue.
http://alistapart.com/article/the-vendor-prefix-predicament-alas-eric-…
recoiledsnake · 2013-03-06
>The same problem doesn't pose (for now) on mthe mobile space, since there are multiple different browsers competing - even if in different OSs each - which means the web devs are forced to remain more or less on spec.
Webkit is pretty much the defacto spec on mobile.
http://www.glazman.org/weblog/dotclear/index.php?post/2012/02/09/CALL-…
lwhi · 2012-02-10
These links [1][2] provide some reasoning behind not using vendor extensions. The second is referenced in the article we're commenting on. I find it difficult to understand why much vitriol needs to be expended.
[1] http://www.quirksmode.org/blog/archives/2010/03/css_vendor_pref.html
[2] http://www.glazman.org/weblog/dotclear/index.php?post/2012/02/09/CALL-…
mbrubeck · 2010-05-01
Daniel Glazman (W3C CSS Working Group co-chair) gives a few more examples from a CSS point of view: http://www.glazman.org/weblog/dotclear/index.php?post/2010/04/30/Innov…
Yet another example is "viewport" meta tag, which Mobile Safari introduced, Android later adopted, and which we (Mozilla) are now adding to mobile Firefox. There's no spec for this anywhere; it will probably be implemented in half a dozen mobile browser engines before even a draft spec is written.
Now, it's clear from all these examples that Sachin and Joe's description of the situation are factually wrong. But that doesn't mean they don't have a point. The problems they feel with web development may indeed exist, but with some other cause than the one they imagined.