HN user
You can try it out, whats in memory is a compressed mathematical map of your data, typically it uses about 30-34x less memory than the total dataset size. Currently the only ram hungry part is during the graph build (which we're working on lowering too.)
I'm confused, what's the point of this? It looks interesting, but is this just a way to define infrastructure config?
The wikipedia demo is cool, try it out!
I think its quite easy to get non sloppy looking ui code. I normally start by asking it to follow apple design guidelines, and then customise it from there. The thing that makes it slop, is when you're not specific about what you want. Then it's going to use the "average of all code" designs.
The other things is especially when adding animation, people often prompt "animate the button" which to a developer is very vague and would need alot more work.