Though, I guess the issue here is comparing bidet to no-bidet.

The bidet is so much better than TP only, it is not even close. Instead of feeling gross, you feel glorious, is what it is.

I bought mine off Amazon for like $40 and it does that.

BTW I do clean mine now and then, and there is like, almost nothing to clean. Compared to e.g. my humidifier, that needs almost-daily cleaning.

This is really about having SSO, not about Octa or Google.

What we see in reality is that append-only database is unusable without making additional "projections" or whatever you call them, databases that are ready to be queried/updated, with maybe specific denormalizations, indexes and so on.

And oh, btw, those later databases are not "imutable".

If I hire Assembled to help with support, what can they provide?

Obviously, they will have zero knowledge of the product. What can Assembled help with here?

Is this about fending the first-line questions, like "please reboot your computer"?

BTW there is like thousands of companies that do that. Not clear what is special here.

Is it actively used?

Hmmm, I thought that if you sign an agreement... it does not matter whether you "mean it" or not. You signed it, so it has to have some meaning.

Or, can you back out of a signed agreement by saying "Oh, I did not mean it"?

Not an expert, but seems dubious/shady.

NULL in SQL has nothing to do with pointers.

It means that the value is missing or otherwise unknown.

Consider the column that is tracing the reading of a meter of some kind. And let's say that we could not get a reading -- due to some fault. So we did a reading, and we want to record that. What "value" should we record? 0 is no good - may make you think that we recorded a reading of 0 - which is not true.

NULL is the solution - it specifically tells you that the reading is missing or inapplicable.

Obviously, this complicates things, but incidentally translates well to other languages that have a (completely unrelated) concept of a null pointer.

That bothers me. It is like saying that "infinity" (+inf) equals other infinity. Which is just wrong.

Some other SQL dialects will return "UNKNOWN" rather than "t" (true), which imho makes way more sense.

>> We're currently at 1/10th of Amazon.

Curious, where is the "1/10th of Amazon" coming from?

This is tricky, as handling a person asking for a medical advice is a rather special thing, compared to a person asking to buy a vacuum cleaner.

The thing is, all of your medical info will go to all of the above trackers, and surely they will sell it to whoever wants to pay for that. Insurance companies included.

Seriously, the article was just a rant. Yeah, people 50 years ago did something wrong. So what.

That is not much of an insight. It is as insightful as saying "water is kinda wet.". Well... sure it is.

What we need to deal with, is not "make a simplest system".

Rather, we need to deal with: "build a system that does A, B, C, ... and so on". Now, if you can do all of the above and make it simple... awesome. But if you cannot do all of the above, but the system is simple.... that is useless.