This looks cool! Stablecoin on-ramps are still not perfect. I think it's important to meet customers where they're at, so a lot of the banking-centric onboarding options won't work everywhere. Don't really understand a lot of the criticism on this thread, seems to mostly be caused by the "crypto = bad" opinion. Good luck with Karsa, keep up the good work!
CTO of Vigilant here. Does anyone have ideas on how to do versioning for an SDK that you change often? Would putting new features in a "beta" release version make sense?
One of the features we're excited about adding is a way to cache values locally. Having control of cache ttl and refresh intervals would be a must if we added that. You're right that the tool should just work without the developer worrying about affecting latency.
Feature Flags looks like it's crafted around automated rollouts. Varse was designed to be more manual, just for reading / writing key - value pairs. You can use it to store long-lived variables like database_url. It could also be used for short lived variables like percent_db_migration_rollout.
Have you used Feature Flags in the past? I'm curious what your experience was.
It's a variable or config that gets injected into a server at runtime. At least that's what I've heard it called in the past. I think it's interchangeable with environment variable.
Since almost all websites use HTML / CSS, its the output format we wanted to target. If you don't use HTML it breaks things like SEO, accessibility, etc.
Our current API is design in the editor -> HTML / CSS. Exposing the internal data structure wouldn't work well. We've changed the structure multiple times in the past few months. We have plans to change it rather dramatically in the future.
We actually looked into Tldraw. I read a lot of the source code and their editor is impressive. We ran into performance problems at around 1000 nodes when panning and zooming. After seeing that, we decided to make the jump to WebGL.