Maybe this is a different use case for code generators from what you have in mind? This isn't one-time upfront scaffolding, it's a recurring part of the development process.
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?
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!
Perfect, thanks, that's what I was looking for (and none of the news coverage seems to mention).
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 ;)
My perception is that with AWS, instead of managing a physical data center, you have to manage a virtual one. You still need dedicated technical staff.
A small business should use a backup service like Backblaze. AWS is what you use to _build_ a backup service.
I think the primary feature is limiting the damage of a compromise.
It sounds great to also use this as a way for the customer to cancel service with an unwilling company, but I think in practice they may come after you with a collection agency.
Maybe they problem is the word "need". How do you interpret the word in this context? I read it as "are legally required to", which is a thing that can be true or false.
Which version(s) have you experienced? (Any that track eyes?)
I've only used Quest 1, with _fixed_ foveated, and while it's noticeable, it's good enough that I could see a generation or two of improvement pushing it beyond noticeability.