I think it’s especially great for smaller apps/sites or prototyping. Setup is quick if you’re already comfortable with CLI tools and configs. Or if you just want to get started immediately with no setup, just add a script into your site and when it needs to go into production later you can still do the setup process for a robust build.

It helps to avoid the specificity problem. You don’t have to manage a complicated class system, you just set styles directly on the elements. Yes this is pretty much what everyone agreed in the past was the worst thing to do but that was before things like CSS variables existed (which Tailwind uses excessively) that lets you control details like color and fonts from a single point. So you don’t have to go through every component to change the brand color.

At work we don’t use Tailwind often but in our React apps we mostly use Theme-UI which lets us write regular CSS on each element in a nice JSON format instead of the class name hell that is Tailwind. This is my preferred way.

You can reduce animations and transparency, enhance contrast (though not every application supports it) and turn everything grayscale but you can’t change the overall style and layout of the OS.

That emoji annoys me more than I would like

This is where „… or anything that might be an issue in the future“ comes in.

My experience is that nobody cares about privacy, moral issues or anything that might be an issue in the future. They only care about convenience, distraction and whatever their peer group is doing. So the “attention” this is getting is never going to reach the spineless mass audience.

I wish I could get everyone to use it but many of my friends are having trouble with notifications not working reliably for Signal. Or sometimes messages are simply not sent immediately, even if both sides are online. This is not helping to get people over. Also no one but me really cares about all the reasons why I would like to get rid of Whatsapp, especially if they would have a lesser experience.

So far the Spigen Smart Fold 2 Magfit Wallet which I don’t like because it’s too bulky and heavy, only fits 2 cards realistically and you can’t get them out easily without unfolding the kickstand. So I don’t use it.

And the Twelve South Butterfly. It’s beautiful and nice for travel. The night stand configuration is not very stable due to the weak outer magnet but once you learn to be a bit more careful with it it’s ok.

Nevertheless I plan on buying some solid stands for bedside and home office but haven’t decided yet.

Otherwise I don’t really know what else to buy. Don’t trust it as a bike mount and don’t need it in the car.

I have Maps installed but never use it. I have Chat installed for that one weird friend who only has Google Chat because she says all her friends are there.

Does it have a 30-pin connector?

Yep, most smart home stuff I would not recommend buying for the regular prices.

But why would they? They can’t put anything meaningful on a tiny device like this that is powered by HDMI. TV+ is available on Smart TVs. What kind of niche audience would this have?

Just improve the Home app please. It’s still on Matter 1.1.

Even if it’s not a big deal, it’s a form over function decision and I was hoping Apple is over that by now.

That’s another reason, yes

Sony gave up on the VR2 before it was even released. No promotion, hard to even find the games in the store, no free VR games in PS+, barely any investment in developers and exclusives. I don’t understand why anyone would expect a better outcome.

Legendary talk

I would prefer Apple making routers again.

It does make sense when you mix. You get the benefit of instant rendering and dynamic content all in one. And web dev becomes even more complicated…

There is no latency on static pages. They are rendered once as regular HTML and then saved on the server to be immediately ready for the user. The server is only processing that initial data fetching and rendering once per site. If needed, it can be retriggered. This is great for blogs and other regular pages.

Server pages on the other hand will do the initial fetch request every time but once the site is there, no data is missing and everything is there. It’s not for everyone. Regular dynamic pages still make sense. For every method there are use cases.

Disclaimer: I’m speaking from my experience with Next.js which did the same thing long before and React now aims to make that easier. But I’m not sure if React has the distinction between static and server. It’s all new and I haven’t had a project to test it on yet.