pull down to refresh
I completely agree with commitment to excellence and this is consistent with the intention of Flint. Like with any product development, there will be phases
- Private alpha (we're calling Kindling)
- Public beta (we're calling Firewood)
- GA (we're calling Blaze)
The level of quality you're speaking to for security and robustness definitely applies to #3 Blaze. For most applications, I would expect #3 to still require human programmers to review/audit/improve the code for proper attention to security, privacy, and scaling.
For #1 Kindling and #2 Firewood, pure vibecoding will be the norm to make it accessible to more people and to experiment and iterate in a more rapid fashion. For Kindling, like any alpha software, it is "tester beware" and hence there is encouragement to use small funds while testing.
It actually doesn't. MDK, Lexe, LN, Spark, Ark, e-cash, etc. doesn't support it. Few wallets support it. Basically no one could test your apps. The goal here is to make it easy for people to test and rapid iteration.
I think this is cool, with one exception:
If you design for money transmission and you're not rich, you can't have the type of bugs they are preemptively disclaiming. Moving fast and breaking things on Facebook built us an industry focused on maximum data extraction and thus maximum privacy invasion.
So while it may sound cool to approach it like that, I'd be much more impressed if there was an item that said something like:
You're not afraid to commit to excellence: In a world where you do nothing but chat with a bot all day, all you have is reputation. Exposing the public to products that are low-security and low-privacy is damaging to your reputation, so you focus on getting it right. Restarting is cheap and easy because all it costs is GPU ticks.