ZC3rr0r

I need to re-read the lyrics to that song, it's one of my favorites by APC.

Thanks. I did not know that, but after reading into it 10000 days now feels a lot more personal.

Other than James Hetfield noone springs to mind in the category "Musicians' moms killed by Christian science". Who else were you referring to?

Yeah, I'll look into that. It's just a shame to have to do extra work and spend extra money because a company decides to screw you over after your purchase.

Well, look who's looking like an idiot for setting up my entire house with Hue lights recently after running two bulbs with local control for years... sigh it's getting mighty frustrating having to deal with companies hoarding your data.

I actually ran this setup for a pretty long while without major issues. YMMV but OneDrive is not a terrible way to store a single user database backend if you don't have a lot of sequential writes going into it in a short timespan.

Yes, but at the time Excel didn't support concurrency either ;-)

Anyway, you are correct about the issue with concurrent writes, but that's only because Access was intended as a single user DB. If you wanted a multi-user DB you should be getting MS SQL server.

Not saying this product strategy worked (it clearly didn't, otherwise people would not be using Excel), but that's how they envisioned it to work.

Storing data is only one of the parts to the formula of what makes a database. Proper databases require structured storage of the data and some way to query the data constructively. Excel did not have those features until Microsoft gave up trying to convince people to not use it as a DB and added it to Excel.

Well, to be fair to Access, it's not like Excel is such a great multi-user database either, now is it? ;-)

Microsoft spent years and years trying to get people to not use Excel as a database, until they eventually had to give up hope that anyone who doesn't know the difference would voluntarily use Access, so they started adding database-like functionality to Excel to meet their customer's demands and try to make the experience at least a little bit less painful.

This is a real-life case of "meet the user where they are" despite the designer's wishes, because even within Microsoft, there is strong agreement on not using Excel as a DB.

That was the most infuriating thing about this whole post to me. Elon's braindead take is on brand and expected at this point, but that chart (or worse, the reaserch behind it) is the true crime here.

Companies are held to certain expedience standards when it comes to removal. If you request it and the company doesn't delete within the described maximum time, they will get fined under GDPR.