If you added a few more tools that let the LLM modify code files that would directly serve requests, that would significantly speed up future responses and also ensure consistency. Code would act like memory. A direct HTTP request to the LLM is like a cache miss. You could still have the feedback mechanism allowing a bypass that causes an update to the code. Perhaps code just becomes a store of consistency for LLMs over time.

▲

samrolken 2 days ago | parent | next [-]

This was an unserious experiment meant to illustrate the gap and bottlenecks that are still there. I agree that there's a lot that could be done to optimize this kind of approach. But even if you did, I'm not sure the results would be viable and I'm pretty sure classic coding (with LLM assistance and all) would still outperform such a product.

	▲	Finbarr 2 days ago \| parent \| next [-]
		I found it thought provoking and interesting. Thanks for sharing.
	▲	theendisney 2 days ago \| parent \| prev [-]
		You need to do more unserious experments. This one is perhaps the best stupid idea ive seen. Maybe the browser should learn to talk back. You could store the pages in the database and periodically generate a new version based on the current set of pages and the share of traffic they enjoy. You would get something that evolves and stabilizes in some niche. Have an innitial prompt like; "dinosaurs!" Then sit back and see the magic unfold.

▲

kinduff 2 days ago | parent | prev | next [-]

Creating instructions and adding boundaries on how to grow, and you end up with a seed.

▲

hartator 2 days ago | parent | prev [-]

You should try making this.

	▲	Finbarr 2 days ago \| parent [-]
		I'm tempted to!