I don't understand this sentence. If the structure is going to change over the time, it means you will need to regenerate the whole system, plus you will apply the changes that you made on the generated code to the newest generated version. So it isn't a valid case for generating code.
When email templates are edited in the external service, you run the generator to pull in the latest structure, and it breaks your build with new type errors.
For years when discussing displays and computing ergonomics, I've claimed that I look forward to the day when my screen doesn't need to emit light, and maybe using it can feel more like paper.
Reading this makes it seem less sci-fi future, and possible today if we can get enough interest/momentum.
I'm trying to think of practical places to start for a sellable product. I love the Paperterm idea, but recognize that it's super niche. Maybe something focused on distraction-free writing?
I've written multi-thousand line Makefile build systems across multiple directories and multiple platforms, from scratch.
I must say Make is the most non-intuitive language I've ever had to work with. It's been near impossible for other engineers to pick up the build systems I've written. They still come back to me to ask questions years later.
And most importantly, you have to use tabs instead of spaces. ::sigh::
It's a great tool for some things, just like anything else. But I'd be careful about using it as your default.
I wouldn't want to use it for its intended use without first looking hard at modern alternatives. (perhaps starting here? https://github.com/ninja-build/ninja/wiki/List-of-generators... )
But for solving the problem of "where should we keep our developer command shortcuts?" (which you might answer with "shell scripts" or "a Rakefile"), I've found Make to be pretty great!
This data is stored on the Matic blockchain. The most important bits are
1) Text contents of the tweet
2) Canonical link to tweet (on twitter)
3) Digital signature by owner (using their ethereum wallet)
Valuables (the service minting tweets) is also responsible for linking a twitter account to an ethereum address. Also, these tweets are purely collectibles, i.e. they don't confer copyright or commercial rights to the buyer.
So when you want to sell a tweet, Valuables verifies who you are and that you own the account (presumably), they produce one certificate and promise never to produce another, and then it goes into the blockchain.
So now there is one and only one entry for this tweet in the Valuables Twitter namespace, but there can be more from other organizations and on other blockchains.
It's going to become even more of a collectors' item when Valuables shuts down, or Twitter changes their URL scheme, or we're not using https:// anymore ;)