Most active commenters

    ←back to thread

    Material 3 Expressive

    (design.google)
    333 points meetpateltech | 14 comments | 13 May 25 17:20 UTC | HN request time: 0.001s | source | bottom
    Show context
    bflesch ◴[16 May 25 11:38 UTC] No.44004143[source]▶
    How did these clowns manage to make my mouse cursor laggy? It is incomprehensible for me to live in such a big bubble with such a big paycheck and then spend zero brainpower on systems without graphics acceleration.

    This is extremely bad engineering and these engineers should be called out for it. It takes a special kind of person to deliver this and be proud of it.

    Once they made their millions at Google these engineers will be our landlords, angel investors, you name it. The level of ignorance is unfathomable. Very sad.

    replies(42): >>44004209 #>>44004297 #>>44004309 #>>44004310 #>>44004330 #>>44004378 #>>44004468 #>>44004549 #>>44004638 #>>44004825 #>>44004861 #>>44004919 #>>44005080 #>>44005120 #>>44005144 #>>44005713 #>>44005761 #>>44005939 #>>44006054 #>>44006202 #>>44006222 #>>44006355 #>>44006362 #>>44006397 #>>44006542 #>>44006933 #>>44007513 #>>44007884 #>>44008050 #>>44008069 #>>44008126 #>>44008380 #>>44008411 #>>44008487 #>>44008805 #>>44008857 #>>44008864 #>>44009031 #>>44009167 #>>44009897 #>>44010290 #>>44010679 #
    1. kiliancs ◴[16 May 25 12:48 UTC] No.44004825[source]▶
    They also seemingly went out of their way to prevent ctrl/cmd+click on several anchor elements in pages like https://m3.material.io/components.
    replies(1): >>44005709 #
    2. edoceo ◴[16 May 25 14:07 UTC] No.44005709[source]▶
    Arrreg!! So many of these React (et al) sites, with poorly re-built elements and break the built-in functionality! The A tag works perfect! But no, we need three or four nested divs, components, and many lines of JS to end up with something worse.

    Is React the driver? Do devs just not know? Is management pushing garbage?

    replies(4): >>44006213 #>>44006527 #>>44008370 #>>44008419 #
    3. dcre ◴[16 May 25 14:52 UTC] No.44006213[source]▶
    If you render an <a> in React (or Angular, which I think they're using here), it's just an <a>! You have to do extra work to fuck it up!
    replies(4): >>44006525 #>>44006716 #>>44006830 #>>44010044 #
    4. agos ◴[16 May 25 15:18 UTC] No.44006525{3}[source]▶
    Indeed. And all the routing libraries also render <a>s by default
    5. diggan ◴[16 May 25 15:18 UTC] No.44006527[source]▶
    > Is React the driver? Do devs just not know? Is management pushing garbage?

    I'd say developers who aren't web developers trying to do web dev seems to be the cause of this. Understanding the platform you're developing for is pretty much table stakes for any developer, and not understanding when to use <a> is pretty much the most basic mistake you can make. Literally the first things you learn in web development is about linking to other pages, yet somehow still people fuck up putting a <a> into a webpage properly. Boggles my mind.

    React makes it as easy as any other library/framework, but if you don't think about what ends up in the DOM, and why certain things have to be a specific way (often for accessibility and user experience), then you'll screw up even big and expensive projects like this apparently. 2x boggling since this project is literally all about user experience yet they get the most fundamental part of the web wrong.

    replies(1): >>44007618 #
    6. wapeoifjaweofji ◴[16 May 25 15:35 UTC] No.44006716{3}[source]▶
    I'll generally excuse things like laziness and incompetence, because I understand that not everyone is good at their jobs.

    But this:

    > You have to do extra work to fuck it up!

    resonates so hard. I get so angry at people who take extra time out of their day to put so much effort into making things worse. So many things on the internet are fine, but people spend so much on making them worse. Who is this good for? Not me, and likely not the person who wasted their time ruining functional things.

    7. eastbound ◴[16 May 25 15:46 UTC] No.44006830{3}[source]▶
    It doesn’t do the internal navigation.

    And since React doesn’t have built-in support for pushState (Yes I know React Router, but it really wants a hash router), you really need extra work for an internal router. And therefore, every beginner dev does it manually and slightly inconsistently.

    So yes, React is absolutely the driver, same as Java is guilty for Guava existing, because it should have been built-in and perfect.

    replies(2): >>44007902 #>>44008420 #
    8. riffraff ◴[16 May 25 16:58 UTC] No.44007618{3}[source]▶
    > I'd say developers who aren't web developers trying to do web dev seems to be the cause of this.

    Hard disagree. I've seen a ton of decent web developers (i.e. people who can use modern CSS, layouts, and modern web stacks) reinventing buttons and links and forgetting about accessibility.

    It's a completely orthogonal thing to the dev background.

    replies(1): >>44008433 #
    9. dcre ◴[16 May 25 17:26 UTC] No.44007902{4}[source]▶
    In this case we are not talking about beginner devs (to their credit, the React docs are pushing people toward frameworks now) — these are literally the developers of a framework, fucking it up in their own docs!
    10. tshaddox ◴[16 May 25 18:18 UTC] No.44008370[source]▶
    With every client-side routing framework or library I know of, the trivial happy path will involve using their provided link component which performs client-side navigations on click but also renders an underlying anchor tag with href (and works with cmd-click, middle-click etc.).

    You really have to go out of your way to break this, and I don't think client-side routers deserve any blame for this. Anyone who is ignorant or careless enough to ship broken links using a client-side router would be just as likely to break anchor tags with their own hand-rolled JavaScript.

    11. johnfn ◴[16 May 25 18:23 UTC] No.44008419[source]▶
    One of my pet peeves is people blaming things on React that have nothing to do with React. I see this quite frequently on Hacker News. Using an a tag or not has nothing to do with React.
    12. tshaddox ◴[16 May 25 18:23 UTC] No.44008420{4}[source]▶
    > Yes I know React Router, but it really wants a hash router

    This doesn't sound right. The history API has been widely supported by all major browsers (including mobile) since 2013. React was also first released in 2013. Did React Router ever ship a version without a HistoryRouter.

    13. johnfn ◴[16 May 25 18:25 UTC] No.44008433{4}[source]▶
    That sounds like people who don't know web dev trying to do web dev.
    14. cmgriffing ◴[16 May 25 21:45 UTC] No.44010044{3}[source]▶
    I was digging into the cursor effect just to see why it's so laggy for some people and noticed that this is actually a Next.js site.

    That is news to me that Google is using Nextjs for anything.