4 ms·
Seems like a premature optimization at the cost of the user. I don't care how fast it runs if it doesn't do what I want. EDIT: yeah, you probably are right ..
by scotty79 5y ago
Seems like a premature optimization at the cost of the user.
I don't care how fast it runs if it doesn't do what I want.
EDIT: yeah, you probably are right ... I know too little about parsers. Maybe there exists a formal proof that you can't make a fast parser for that syntax without unbounded lookahead.
Maybe they should even create CSS from the start as two part system. Convenient syntax for humans, once written compiled to StyleAssembly comfortable for the browser.
- asddubs 5y agohope all your visitors on old hardware feel the same way
- StephenJGL 5y agoIt's living in the browser and this feature is mostly useful in complex CSS. Most definitely not a premature optimization.
- johnday 5y agoIt still does what you want! This is an issue of syntax, not semantics. Avoiding unbounded lookahead is not "premature" optimisation - if introduced, it would never be possible to remove due to the algorithmic complexity involved.
- deleted 5y ago[deleted]