8
kiki
300d

Google being google

Comments
  • 3
    I'll save this for later when I get asked again why I think that HTML and CSS is not a good tool to build UI for apps. Thanks.
  • 2
    Seems like clownery with the new fad of encoding icons as fonts.
  • 0
    @CoreFusionX you mean something like font-awesome? That’s old. But it doesn’t look like it.
  • 2
    @Lensflare

    Google has his own spin on it with material fonts.

    Yeah, it's probably older than I think. I only update my frontend knowledge when I'm absolutely forced to.
  • 5
    Btw, the overlapping orgy of vertical "arrow down" is supposed to be the arrow right icons.
    So they hacked their down arrow icons into right arrow icons by rotating them 90 degrees. This is complete dogshit in terms of accessibility. Fucking disgusting!
  • 2
    Looks good to me. Approved for release.
  • 3
    I would more readily believe that this is in fact your adblocker being an adblocker
  • 0
    it seems that your browser blocked images or javascript or some network resource or something. It's not really google's fault. Those words should be replace with icons, in normal browser.
  • 1
    @daniel-wu fonts didn’t load. That’s it.
  • 0
    You must've hit the X button before the page finished loading.
  • 1
    @Sid2006 no. Fonts don’t load sometimes. You have to account for that. Not everyone has fiber internet. In lighthouse, google say woke facts like “1366x768 is still the most popular resolution”, but they themselves didn’t optimize their own ui for slower connections.
  • 2
    @Lensflare This looks like docs so it's more text with fancy nav than an app.

    Also, you can and should use SVG for these buttons, abusing fonts for graphical elements is a recipe for glitches.
  • 0
    @kiki I don't speak frontend so I don't know. Just refresh the page sorts it out most of the time. It isn't such a hassle for me.

    If you have slow internet then no frontend technology can help you with that anyway.
  • 2
    @Sid2006 if you're homeless just buy a house.

    I speak frontend, and what Lorentz said is right. Use inline svgs, they aren't external resources, so when the page loads, they load. they're literally html tags.
  • 1
    @kiki I actually would recommend external SVGs and either HTTP2 push or preload links. A good CMS should be programmable to include links to all icons that appear on the page. SVG is a pretty verbose format so it should not be copied all over the HTML and downloaded 50 times, and the core issue with fonts is that they download the entire icon pack even if you just use the two icons visible here.
  • 0
    I'm also very excited about Lit, as the optimal solution IMO would be to include the SVG inline but only once and that's basically what templates do.
  • 2
    @lorentz CMS thing is good for sure if you need that, but if you don't, you do an SVG library definition at the beginning of your doc and then use <use> tags to avoid verbosity ramifications
  • 2
  • 1
    @lorentz you seem to know what you're talking about when it comes to frontend. It was a pleasure to teach you a thing you didn't know 😌
Add Comment