We still have to provide a way for people that don’t have (smart) phones, but I would absolutely implement asking the phone instead of a 3rd party when available.
We don’t gain anything from asking a 3rd party. In fact it costs money per request.
It is, but it’s difficult. I am down visiting New Zealand and 3 times I have flown domestically here and there no ID check. I buy a ticket online, check in online, and scan a barcode at the gate. Is New Zealand an exception, or do a lot of countries not require an ID for domestic flights, and the US is the exception?
I don't think this is specifically a react problem. The problem is that people don't want to learn what modern CSS can do, or write it themselves (see Tailwind), and most new frameworks make it easy to just sidestep that with div soup.
Some of us _like_ CSS, and try to use as much of it when possible, but I feel like we are few and far between. I use react to manage the state of my app, but that doesn't mean I have to make a 27 div component to style an input.
The big problem is trying to convince the rest of the team that they should learn and use CSS.
I couldn't quite go for the 60%, but I have friends with the UHK60 and I really liked it as a keyboard.
I popped for the 80 as soon as the shipping times caught up to real time. It's a fantastic keyboard. I haven't gotten any of the clusters for it yet, but I'm very happy with my purchase.
No. The entire point of these is to funnel the traffic onto and off the highway with out crossing any oncoming traffic, and to reduce the total number of traffic crossings overall.
My outcome was the shutdown of Apollo, rather than the blackout. I no longer read Reddit on my phone. (Except for a link or two clicked from something else, but even then I go to `old.reddit` instead to read the comments). That was really where I wasted the most time on it.
It’s kind of a relief. I think I was too “lazy” to stop on my own because Apollo was so comfortable to use.