aenario

> This whole notion of "documentation can get out of sync with the code, so it's better not to write it at all" is so nonsensical.

I do believe that in a lot of case an outdated, wrong or plain erroneous documentation does more harm than no documentation. And while the correct solution is obviously "update the doc when we update the code", it has been empirically proven not to work across a range of projects.

You might have some success selling this "technology" to wedding invitation printers and similar websites. They always have trouble demonstrating the various paper options / partial glossy / metalic cut out options

You seem to only conceive of the web as "html+JS frontend communicating in real time to some server"

We have decades of distributed systems without a central server. Such as git, bit-torrent, Mastodon, Matrix, and the whole web3 mess. It's for these use-case that CRDT helps solve real problems.

It's a very narrow use-case of conflict-free data type. Sure if you are willing to wait for however long to get a lock before you can edit something.

The main goal of CRDT is for long-split branch such as can happen in federated systems or with offline management. (think git)

I think your LAMP (Linux, Apache, MariaDB, Python) is a fancy new LAMP (Linux, Apache, MySQL, PHP).

You are complaining that the allergens information takes room on your restaurant menu.

We the people, through our democratic processes, have asked companies for transparency of their tracking process, the industry have decided as a whole to say fuck off and made the process as painful as possible.

Yes, the companies are evil/stupid villains on this case. Not everything needs bloody philosophy.

It was actually refused by ad & publisher networks. They really wanted the capacity to "convince" the user that their tracking is very special and good for them.

That when you need a given feature, you will more probably find an actively maintained package which cover it and is compatible with the rest of your dependencies/framework.

*historically contributed

Will contribute 6-10% of yearly emission in the coming years

"The social network" does not make Mark Zuckerberg look bad. He looks like a poor socially inept nerd who got scammed by Parker, it makes one want to pity him.

The very notion of identity thievery is "BigMoney" (banks and credit rating) putting on their customer the responsiblity of what we used to call fraud.

We used to have a Do-Not-Track header, which all websites promptly ignored.

The hard part is having a legally-binding standard

Given the current available API, I'd imagine the law-maker could have decided to write in the law 'consent must be collected through a javascript window.confirm() popup'

I can see a way this would be useful to use the same abstraction to limit app/user web access to a single domain.

For instance the dropbox binary can only access "/home/dropbox" and "/net/dropbox.com" if this was more well-known/used.

libuv bindings ?

The interesting thing about coopcycle is that it's actually a coop of coops :

Several local delivery coops (say one per city) collaborate to fund development and hosting of the software solution.