We put a lot of satire in to this, but I do think it makes sense in a hand wavy extrapolate in to the future kind of way.
Consider how many apps are built in something like Airtable or Excel. These apps aren't complex and the overlap between them is huge.
On the explainability front, few people understand how their legacy million-line codebase works, or their 100-file excel pipelines. If it works it works.
UX seems to always win in the end. Burning compute for increased UX is a good tradeoff.
Even if this doesn't make sense for business apps, it's still the correct direction for rapid prototyping/iteration.
Can't believe I missed this thread.
We put a lot of satire in to this, but I do think it makes sense in a hand wavy extrapolate in to the future kind of way.
Consider how many apps are built in something like Airtable or Excel. These apps aren't complex and the overlap between them is huge.
On the explainability front, few people understand how their legacy million-line codebase works, or their 100-file excel pipelines. If it works it works.
UX seems to always win in the end. Burning compute for increased UX is a good tradeoff.
Even if this doesn't make sense for business apps, it's still the correct direction for rapid prototyping/iteration.