David Gerard@awful.systems to NotAwfulTech@awful.systemsEnglish · 1 year agoFirefox has apparently caught up in speed with Chrome again this seasonnews.ycombinator.comexternal-linkmessage-square8fedilinkarrow-up13arrow-down10
arrow-up13arrow-down1external-linkFirefox has apparently caught up in speed with Chrome again this seasonnews.ycombinator.comDavid Gerard@awful.systems to NotAwfulTech@awful.systemsEnglish · 1 year agomessage-square8fedilink
minus-squarebobtreehugger@awful.systemslinkfedilinkEnglisharrow-up1·1 year agoYeah, supporting every css feature in the world is a tall order. I would love if: Servo supported a small but useful subset of css features (e.g. just grid and flexbox for layout) Servo was embeddable like a WebView or electron. Then you could use the supported subset and not have to worry about supporting every crazy feature, and hopefully get a faster lighter WebView for it. But even that’s a lot of work.
minus-squareself@awful.systemsMlinkfedilinkEnglisharrow-up1·1 year agoI was thinking along those lines too. I’d love to use servo for projects where I know exactly what I’m going to render, or even as a docs viewer where imperfect rendering is ok
Yeah, supporting every css feature in the world is a tall order. I would love if:
Servo supported a small but useful subset of css features (e.g. just grid and flexbox for layout)
Servo was embeddable like a WebView or electron.
Then you could use the supported subset and not have to worry about supporting every crazy feature, and hopefully get a faster lighter WebView for it.
But even that’s a lot of work.
I was thinking along those lines too. I’d love to use servo for projects where I know exactly what I’m going to render, or even as a docs viewer where imperfect rendering is ok