There’s also Dart with its similar syntax to JS, strong type and null safety, and ahead of time compilation with hot reload. And yet it only really started getting adoption after being chosen as the language for Flutter.

I’m with you. Those TOUs are unacceptable.

I don’t have an answer for that. I’m on the outside looking in.

Mr Tim Apple is a complicated figure.

Not a lot of options for iOS. There’s Tor browser and Brave that I know of. Brave is surprisingly good, but I don’t do a lot of serious navigation in the phone, and tend to favor private mode so the tracking gets deleted once I close the tab.

It’s a drop in replacement. It’s pre hardened so you may want to relax the settings a bit to get some comfort (at the expense of privacy). But otherwise you’ll feel right at home.

I don’t want Mozilla to be handling my personal data in any way. Anonymized usage statistics? I could be convinced to relinquish that. But that’s it.

The field to add your social media handles has been on the DS-160 for at least a decade. It was optional until something like five years ago. The DS-160 is the visitor visa request form. So I guess Trump already made that change in his previous mandate.

What seems to be changing now is that It’s becoming mandatory for residency visas. And also the willingness of the government to go full nazifascist.

This looks interesting, but it would work so much better as a written article to me.

Got it, thanks.

Hold a sec. Rolling your own RDBMS out of a NoSQL database is insane. But is the opposite feasible? Wouldn’t it be a simple table with two columns: a key and a JSON blob?

Gotcha. Thanks!

Right, RDBMS for object permanence is a pain. It’s meant as efficient data storage and retrieval. But I counter that a huge amount of data problems are of that kind, and using object permanence for general database applications seems very contrived. I’m imagining loading a huge amount of data to memory to filter the things you need, essentially rolling your own DBMS. Am I missing something?

I don’t know if it was you, but thanks for the initiative.

Right, and you’d never do a search for messages with a particular reaction, so there’s no functionality loss is this use case.

What I’m hearing is that they’re very different beasts for very different applications. A typical web app would likely need both.

Let me see if I got it. It would be like a denormalized table with a flexible number of columns? So instead of multiple rows for a single primary key, you have one row (the file), whose structure is variable, so you don’t need to traverse other tables or rows to gather/change/delete the data.

The downsides are the usual downsides of a denormalized DB.

Am I close?