Comment by 6510

2 hours ago

This is exactly what I've been thinking for decades.

I once made a proof of concept. Wikipedia use to have static menu entries. I had a greasemonkey script that hides some of them them.

For entries that shouldn't be hidden the line that hides them is commented out.

https://userscripts-mirror.org/scripts/review/170442

Then I had a form that let you pick which ones you want. It spit out a gm script with all entries commented out except from the ones you wanted to keep.

https://go-here.nl/gm/wikipedia-clean-up.php

I also wrote this as a joke.

https://neanderthal.go-here.nl

When a link or button is clicked the server return a js file that contain one function. Then it executes the function.

To borrow your example, when you've picked the functionality you want in your note taking app a version number like 1.0.0.unixtime can be generated and stored so that you can later populate the config form with the chosen configuration and add or remove things.

Or you could do something with a config file to populate the form again.

An LLM can also modify a config file. Before execution it can be validated, as it is so simple it can show which mandatory entries are missing, which ones are spelled incorrectly.

If you provide the LLM with the html form or the config file (+docs) it shouldn't have much difficulty generating exactly what you wanted.

As the application has now been turned into ravioli it also addresses the ancient puzzle of separating feature updates from security updates.

You can still introduce a new gui that confuses the hell out of users. Then if no one checks the box you can take your learnings from it without 1000 people having to tell you in 500 different places.