This is regional within the US and obviously differs by person even then. Just remember that the people you are talking to may be the kind of people that need articles like the above to teach them how to talk to people. Their defenses go up when someone approaches them and while they are well practiced at appearing relaxed, they are not. Conversations are short because its emotionally difficult to stay in a heightened awareness state while someone is trying to pull you out of it. But you can certainly provide offramps

Still not a great rendition of this thought, but closer.

Nobody cares about emoji except the poor folks who have to login to it everyday, and it makes their lives a smidgen better. Lets chill on the criticism of emojis.

In this case, the people of Venezuela are desperate to get rid of their socialist government. It has, predictably and inevitably, led them directly to poverty, starvation, and violent repression.

I have a lot of reservations about the way in which Trump is operating and in this case, the legality of every aspect of how he is doing this operation in Venezuela. Despite all those reservations, this is a rare situation where this action benefits everyone and the world.

This should have said reads, not writes. Columnar storage takes significantly more effort to handle writes because it must do many more IOs across the different columns, potentially more de/compression cycles, etc.

W.r.t. query speeds on your columnar storage engine, you will obviously have much better writes that row oriented storage engines. This limits your write capabilities though. Any effort you put into restoring write speeds necessitates an extra step to the maintain the columnar stores - which puts you back into the group of databases naintaining indices that you criticize above.

I think modern databases are bringing new ideas on how to accelerate both write and query speeds simultaneously with tradeoffs around CAP.

But after reading the article I find myself asking if that's really true? I'm doubting it now. Certainly, the Floppy disk icon is clear to computer users who experienced at least a few years of the 90's or early 2000's. That's becoming less and less a percentage of computer users. For most users, that floppy disk has receded into being just a nonrepresentative shape associated to save.

I think it's that the blog post convinced me to reject nonrepresentative shapes as icons. You can't look at the extremely illustrative menu filled with icons that clearly describe window management actions or text formatting actions - where the icon itself conveys clearly, if abstractly, exactly how reality will look after you take the action - and tell me that a menu filled with random nonillustrative shapes has even a similar experience. I can't shake the idea that the menu icon needs to be more than just a logo or branding - it needs to be self-explaining.

The floppy disk did exactly the above when floppy disks were where the data was actually saved. But in 2025, we have to accept that it no longer illustrates anything. Today its just a nonrepresentative shape.

It also makes me think about the classic Save icon: the floppy disk. That was certainly descriptive at its origination, but is it still so? In the age of natively storing documents in the cloud or copying to a USB drive, it seems like we might want more than one save menu or an appropriate icon for where the file resides on the single Save menu item. Microsoft Office has the Autosave toggle switch that serves some of this purpose, but it could definitely be better.

I also think about the Zune UI where sometimes a menu consisted only of the icons. How do you enable unique menu designs like Zune without icons for everything?

Especially for bread where saturation percentage is important, weight/mass measurements is absolutely necedsary.

That depends on whether OP is buying/renting AMD gpu machines.