> I did some research to find why this took so long. 13 years ago, extensions.json used to be extensions.sqlite. Nowadays, extensions.json is serialized and rewritten in full on every write debounced to 20 ms, which works fine for 15 extensions but not 84,194.

Occasionally, databases are useful. ;)

▲

Waterluvian 3 hours ago | parent [-]

This is probably a good example of the opposite. It would be a mistake to design for the fleetingly rare case. If you’re dealing with a handful of extensions, a json file that’s rewritten is fine.

▲

shakna 2 hours ago | parent | next [-]

But the software already has multiple database systems built in. There's not exactly overhead to use what plumbing is already there, instead of writing to disk.

	▲	estimator7292 33 minutes ago \| parent [-]
		Easier for a user to edit.

▲

HPsquared 3 hours ago | parent | prev | next [-]

In an ideal world, software with 100 million users would be optimised for energy usage. It all adds up. This does pale in comparison to everything else, though.

▲

3 hours ago | parent | prev [-]

[deleted]