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?
Whichever versioning scheme you end up choosing, the important bit is to keep documentation for all versions. Bonus points for mentioning in the docs when a feature was first added.
Some examples off the top of my head include python docs, django, bootstrap, postgres and celery.
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.
I’m sure you are already considering this but you’ll probably want the ability to “background” update the local cache so that you don’t have a request hang randomly every X minutes. Also might be nice to specify “I’m ok with a potentially old cache value” on a per-key basis. In my case I think I’d always be fine with “if you can’t reach the config server just use what you last got”.
That's true, although it might get complicated to remember the setting for each user, and for each rollout feature! For more complicated combinations you need groups on the configuration side and to put users (or buckets of users) in groups and give those groups a certain config option.
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.
I use posthog for remote config. Basically long lived flags containing a json payload that allows me to target consumers based on specific properties of that consumer.
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.
in the 1990s which could often make the same edits a professional programmer would make when you edited a visual representation of the code because these were based on a Concrete Syntax Tree
where comments, whitespace, item ordering and all the choices of how to write something are represented. I don't think you could bolt this on to Figma because Figma doesn't have the right representation to keep track of it all.
Graphical editors run into so many little problems like the width of something gets computed to be 13.3333333333px maybe there ought to be a hierarchical "snap to grid" that makes sure is is 13px or 13.3px or 13.33px in the output source code, stuff like that.
Also what exactly is the target? MUI is mentioned in another friend and that's salient to me because I am looking right now at the accessibility of an MUI app: a tool for building applications and theming one single widget set seems like a feasible goal, particularly if it can all be codesigned.
