Where were Gruber’s posts about Dye so obviously being a problem before his exit?
His podcast with Louie Mantia in July was pretty clear with it, though it also suggests why he’s given significant criticism of the design direction, but mostly just has quips and shade thrown at Alan Dye on the blog:
> I get to ask Alan Dye about [the shadows on Apple Watch faces]. And he was like, oh, we render a shadow? And I was like, oh, you never even looked. I just instantly realised he’d never really even looked at it. Like, somebody at Apple has, but Alan Dye didn't. […] It just suddenly came to me, oh, he doesn't do the job I thought he did.
>Comments shouldn't have been allowed basically everywhere in CSS (compare to HTML, which basically only allows them where content goes), because it makes them basically unrepresentable in the object model, which in turn makes building editing directly on top of the object model impossible
HTML comments are basically just a HTML tag that isn't rendered. Tools that 'compile' the HTML code into a document tree, including browsers, preserve comments as nodes without any extra effort.
CSS comments can go anywhere:
Tools that transform/parse CSS can either: 1. Strip comments before parsing, meaning anything based on the parsed version will lose the comments. 2. Dedicate a disproportionate amount of complexity to retaining the comments, and still not really have a good way to handle them through edits/transformations.