3 ms·
This seems like such an unergonomic language for developing financial programs, with hidden sharp edges. eg. How on earth could you think it's OK to let you de
by rkagerer 5y ago
This seems like such an unergonomic language for developing financial programs, with hidden sharp edges.
eg. How on earth could you think it's OK to let you destroy (or permalock) coins through any mechanism other than a blatently clear semantic like DestroyCoins()?
Accountants learned that lesson ages ago with the invention of double-entry bookkeeping.
Can any programmers in the space comment on whether and how newer languages improve on some of the gotchas?
- 0x000000001 5y agoThere's Cairo (haven't evaluated it) and then there's Vyper, which is basically Solidity but Python Vyper powers some big projects like Yearn
- K0balt 5y agoThe thing here is to understand the vm. If you understand the machine and environment the machine runs on, its really not complex at all. It’s a lot like writing c or assembly for a well designed microcontroller.