aptard.apt ⭕

Let me point out here before people confuse Sui with Move: some of the issues the original blog states are specific to Sui Move and are not present in Move in general as used at Aptos. Others are being in the process of being changed. Upgradability On Aptos Move contracts can be upgraded in place as long as those upgrades are compatible. This gives similar power (but cleaner, because of compatibility checks) than EVM proxies, and goes further than Sui. Dynamic Dispatch At Aptos we agree that this feature is important and can be made safe. We have blogged about this before ("The Future of Move at Aptos"). Dynamic dispatch will come to Move on Aptos later this year, and it will be safe, thanks to a new model of access control define in AIP-56. Awkward Mailbox Pattern This is very specific to Sui and not even part of the Move language definition. In Move on Aptos if you like to deposit something in a different account you do so with a capability to write to this account. (And thanks to no requirement to declare inputs upfront, just like with the EVM, you can write to arbitrary addresses, but still have concurrency via BlockSTM's optimistic parallelism). Object Primitive too Generic I'm not really sure if I understand this argument. Since Move is a powerful language which has modules, generics, etc. you can define all higher-level types as you see fit. So this not a matter of the language but of the frameworks. I don't know about Sui, but Aptos has powerful frameworks with lot of abstractions at your fingertips, including NFTs and other building blocks. As regards the ability system, its used to define such higher types, and a novel concept which no other language can offer. So the 'mistake' one may make with abilities doesn't exist in other languages because you do not have this protection mechanism at all!