When you consider "my problem is solved this time" as documentation then a discord discussion can be considered good documentation. But If you want documentation as reference for everyone and don't wan't to repeat process/procedures every time some one needs it. It's the worst platform for it. And For documentation we never want the first.

In this context email lists were the best of the best documentation ever.

Don't blame remote work, blame all the underlying problems related to housing pricing and politician who really does nothing to solve it.

First, persistency. You data lifecycle may not be directly proportional to your applications lifecycle. You may need it even after the app is shut down.

Second, RDBM systems provide a well defined memory/storage structure and API - "structured query language". This enables you to easily query your data and acquire suitable views that are beneficial for your applications purposes.

Third, It's always better to outsource your data layer to a battle tested, and trustworty database then trying to reinvent the wheel.

So this paves a road for you to focus on your business logic than splitting that focus for the data layer and business logic.

I have been with Firefox, since it's inception. Never left it. And it never let me down.

Oh glorious BSG!

Done airlines give you outside views, but shoot with potatoes. So it's better not having that. Also there is nothing to see at most of the cruise height.

Thank you. I edited the main body too.

And that's the problem. It gives full control power to Google. That's the reason that popularity needs to be broken.

I am a Elegoo fan on this. Checkout Neptune 3 pro or 4 pros. I suppose Elegoo should pay me for advocacy here :)

I am using Firefox too. However I also consume lots and lots of general purpose websites which in time probably become not consumable if you are not compliant. Which in turn either render FF not usable, or adopt the unfortunate standards.

This is a bad corporate speak that says, "Don't scrape our data, consume through api and pay upto your necks".

A more important topic is, what federated data will be kept on Meta, and most importantly HOW that data will be processed/used/sold by Meta.