Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

State of CSS

web.dev

Post reply on HN
Print view View original

231–234 of 234 posts

Re: State of CSS

#231

Post by Beltalowda »

abareplace wrote: post #230
Beltalowda wrote: post #206

Earlier quoted context omitted.

I used CSS tooling like LessCSS and SASS for years before switching back to regular CSS because I too wanted to simplify the build process (i.e. by not having one), and I found I didn't really miss the nesting so much. Mostly I solved it by writing things fairly concisely as: #menu { display: flex; justify-content: space-between; orange; border-bottom: 1px solid red; background-color: orange; color: #111; } #menu >a…

orange after space-between should be deleted

Oops! Well, can't edit it now; too late for that. And doesn't really matter: it was just illustrative of the style.

Re: State of CSS

#232

Post by woojoo666 »

alwillis wrote: post #229
woojoo666 wrote: post #225

Earlier quoted context omitted.

> Both WebM [1] and WebP [2] have been supported by Safari for nearly two years now. Which was incredibly late. For example, Firefox had it since v28 [1], which was 8 years ago. Firefox has also supported AV1 for 3 years already. And obviously Chrome supported both for longer [1]: https://caniuse.com/webm [2]: https://caniuse.com/av1

Which was incredibly late So we’re doing this? Instead of acknowledging your statement was incorrect, now it’s about how supposedly late Apple was in supporting the formats you said they didn’t support. And no disrespect to Firefox, but them having WebP support 8 years ago (and AV1 support 3 years ago) in the big picture doesn’t matter that much outside of the web developer/HN/geek echo chamber and the single digit p…

> So we’re doing this? Instead of acknowledging your statement was incorrect, now it’s about how supposedly late Apple was in supporting the formats you said they didn’t support.

I think you should re-read my comment. Fyi I already knew that Safari now supports vp9 webm. As a web dev I keep up with this stuff. In my comment I said that they are so behind.

There's another list of Safari's failures here: https://httptoolkit.tech/blog/safari-is-killing-the-web/. In fact from the article

> According to Can I Use's metrics, Safari is lacking about 10% behind Firefox and 15% behind Chrome in feature support.

And if these were only features that Google cared about, then Safari wouldn't be behind Firefox. But they are.

And in terms of webm/webp support, imo this stuff does matter. Webm/webp is much more efficient than gifs for audioless video content. But if a startup is moving fast and they see Safari doesn't support webp, they simply aren't going to use it. They're not going to bother storing two formats for everything. So now everybody's page load speed is impacted.

Re: State of CSS

#233

Post by joe-user »

woojoo666 wrote: post #232
alwillis wrote: post #229

Earlier quoted context omitted.

Which was incredibly late So we’re doing this? Instead of acknowledging your statement was incorrect, now it’s about how supposedly late Apple was in supporting the formats you said they didn’t support. And no disrespect to Firefox, but them having WebP support 8 years ago (and AV1 support 3 years ago) in the big picture doesn’t matter that much outside of the web developer/HN/geek echo chamber and the single digit p…

> So we’re doing this? Instead of acknowledging your statement was incorrect, now it’s about how supposedly late Apple was in supporting the formats you said they didn’t support. I think you should re-read my comment. Fyi I already knew that Safari now supports vp9 webm. As a web dev I keep up with this stuff. In my comment I said that they are so behind . There's another list of Safari's failures here: https://httpt…

> I think you should re-read my comment. Fyi I already knew that Safari now supports vp9 webm. As a web dev I keep up with this stuff. In my comment I said that they are so behind.

Your comment:

> Safari is so behind in terms of lack of support for free media formats/codecs like webm, webp, and av1. You can't even switch browsers to view them, since it's all webkit

Maybe you do keep up with this stuff, and you did say they are so behind, but you also said "You can't even switch browsers to view them", which is not true.

Re: State of CSS

#234

Post by woojoo666 »

joe-user wrote: post #233
woojoo666 wrote: post #232

Earlier quoted context omitted.

> So we’re doing this? Instead of acknowledging your statement was incorrect, now it’s about how supposedly late Apple was in supporting the formats you said they didn’t support. I think you should re-read my comment. Fyi I already knew that Safari now supports vp9 webm. As a web dev I keep up with this stuff. In my comment I said that they are so behind . There's another list of Safari's failures here: https://httpt…

> I think you should re-read my comment. Fyi I already knew that Safari now supports vp9 webm. As a web dev I keep up with this stuff. In my comment I said that they are so behind. Your comment: > Safari is so behind in terms of lack of support for free media formats/codecs like webm, webp, and av1. You can't even switch browsers to view them, since it's all webkit Maybe you do keep up with this stuff, and you did sa…

Ok I see, sorry I forgot to clarify that I was talking about iOS and iPadOS for that statement
Post reply on HN