←back to thread

Material 3 Expressive

(design.google)
335 points meetpateltech | 3 comments | 13 May 25 17:20 UTC | HN request time: 0.607s | source
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 #
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 #
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 #
1. 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 #
2. riffraff ◴[16 May 25 16:58 UTC] No.44007618[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 #
3. johnfn ◴[16 May 25 18:25 UTC] No.44008433[source]▶
That sounds like people who don't know web dev trying to do web dev.