←back to thread

Material 3 Expressive

(design.google)
333 points meetpateltech | 3 comments | 13 May 25 17:20 UTC | HN request time: 0.001s | 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 #
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 #
1. eastbound ◴[16 May 25 15:46 UTC] No.44006830[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 #
2. dcre ◴[16 May 25 17:26 UTC] No.44007902[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!
3. tshaddox ◴[16 May 25 18:23 UTC] No.44008420[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.