People say the same thing about manual memory management, garbage collection and memory leaks, but to be honest, something about conceptually leaving out the UX of such a powerful tool (like memory allocation) always rings hollow.
If writing "smart contracts" is to remain not for "anybody but very seasoned developers" how can that not seem like anything but a giant gaping hole in the conceptual abstraction itself? Do you think people say the same thing about payment processors? What do you think would happen if Stripe approached its API the same way? Sure, one is a proprietary payments processing system and the other is an entire decentralized virtual machine for contracts. I get that.
But implying that "everybody is busy with much more pressing issues" despite admitting "most people would say it's not the best" really implies a blind spot. Successful technologies end up building layers where folks who aren't "very seasoned developers" can't hurt themselves. Pretending that these layers don't exist or emerge or deliver value is omission.
If writing "smart contracts" is to remain not for "anybody but very seasoned developers" how can that not seem like anything but a giant gaping hole in the conceptual abstraction itself? Do you think people say the same thing about payment processors? What do you think would happen if Stripe approached its API the same way? Sure, one is a proprietary payments processing system and the other is an entire decentralized virtual machine for contracts. I get that.
But implying that "everybody is busy with much more pressing issues" despite admitting "most people would say it's not the best" really implies a blind spot. Successful technologies end up building layers where folks who aren't "very seasoned developers" can't hurt themselves. Pretending that these layers don't exist or emerge or deliver value is omission.