zuprau

Early iPhone/iPad games were really creative with this before everyone just settled on making candy crush games.

In that case I also see "large" PRs, but I point the reviewer to "file X and then 4999 copies of file Y." When doing large no-change refactors, I submit standalone PRs and merge them quickly because no one will review 1k identical changed lines (e.g. if I change the location of /lib/ imported 600 times in the project)

> React's biggest lasting contributions. Describing UI in a declarative way

I feel that AngularJS (v1) did that years before React, and maybe even other MVC frameworks before that.

I can't think of anything React brought in that earlier frameworks didn't already have in a form or another. Maybe hooks? Arguably the worst and least performant part of React.

It only popularized "HTML-in-JS" but that has always been possible via strings or file imports. Even template pre-compilation was part of Backbone or Ember (I don't remember which)

I’d hate to work there. I’d rather review small chunks and merge often than review 5k lines that could be built on a shaky foundation/idea

Seems logical, but as a user, I can already choose the size of the content of the screen, I don't want you to choose it for me. So we all agreed that "16px text" is ok and we started designing the world around that.

As a practical example: my iPhone lets me chose between "native" and "scaled up" sizing. This affects the whole OS including the browser. Where does your "cm" measurement fit in that? Do you want to override my (user) choice?

Additionally, every browser lets me scale the content up and down between 50% and 200%, so "cm" is broken once more.

"pixels" haven't been "pixels" for a very long time, and that's ok, they're now just a logical unit.

I might be wrong, but they're more like a browser’s "service worker" than a Node app.[0] The fact that they have to manually add "compatibility" with Node modules like `utils`[1] seems to support this.

[0]: https://blog.cloudflare.com/node-js-support-cloudflare-worke...

[1]: https://blog.cloudflare.com/workers-node-js-asynclocalstorag...

> no one in Venice is talking about raising the city

I see a lot of results: https://www.google.it/search?q=sollevare+venezia

People have been talking about this for decades, but it doesn't seem to be very popular now, especially since MOSE appears to be working at the moment.

There's even reportage by Le Iene https://www.iene.mediaset.it/2019/news/mose-alziamo-venezia-...

Was it Coca Cola or Pepsi? The last time my family and I sat down for our usual blind test dinner everyone agreed Pepsi tasted better.

The outrage Facebook feasts on is not directed at Facebook. That is just a byproduct.

Here Mozilla decided to place a nice target on their backs asking for money.

This isn’t a bug, so the resolution is expected. What I don’t understand is how Mozilla thought this would work out.

Hot take: Firefox has jumped the shark long ago and people should stop using it.

Funny that it actually happens in a lot of locations with tourists. Also Chinese restaurants in the US often have a “real Chinese” menu and a regular menu in English.

But what you’re arguing doesn’t make sense. As a restaurant owner, I can change online menu prices on the fly. 4th of July? Don’t mind me if I +20% that bad boy.

That just isn’t possible with paper.

iPhones can only do what Apple allows developers to do, which isn’t much.

A random payment provider can’t use NFC on the iPhone, but they can use the camera. So here we are. QR payments are super popular all over Asia (and yes they suck, but you can blame Apple)

Wrong. You know it never ends up being 100kb, and when it reaches 1MB (it always does) then you get the real issues.

It’s because of your thinking that we got bloated webpages.

> using a separate PIN/passcode at application-level provides a separate (master) password which would be used for all your passwords (in case your AppleID password gets compromised).

That already happens exactly as you mentioned.

You need a secondary encryption password for encrypted iCloud data as well. Having access to your Apple account isn't enough.

https://support.apple.com/en-ph/HT202303#:~:text=Apple%20wil...

> somebody who has never worked as a professional UI/UX designer

Such as the Nielsen Norman Group.

> "Do not use modal dialogs for nonessential information that is not related to the current user flow."

> From https://www.nngroup.com/articles/modal-nonmodal-dialog/

Nonessential information such as, let's say, "details."

I'd say that this minisite is exactly on point.

Preach.

You don't even necessarily need to place it in a new page, probably you can just expand it inline.

Most modals are just lazy.

"Where should I put this piece of UI/information?"

"Just place it above everything else."

With SPAs you don't even have an excuse that "a full-page reload will take longer" because you can change the whole page/layout instantly.

> relatively new security feature

Maybe I'm misunderstanding the feature, but I've been auto-filling login forms since I was using IE7 with RoboForm. Other than using Touch ID to trigger the auto-fill instead of 1 click, I don't see any improvements in iOS/macOS Safari.