A little comparison of two main platforms for which we make the oracles. They are showing a lot of concurrency in the social field recently, so let’s break it up.
ETH
Pros
• Simple and fast development
• A wide range of tools for creating and testing software
• Big audience of users and developers
Cons
• The network is often overloaded. Because of this, it is hard to estimate the price of the transaction — this is crucial for the subscribable Oracle service
• Since there was no contract testing tools in the beginning, neglecting any kind of testing is a common case now. This has a huge impact on the quality of the contracts
• Smart-contracts cannot be updated
EOS
Pros
• TPS(transaction per second) rate is just fantastic. It is a new level of dev quality :)
• Permission sharing system — is, indeed, an interesting concept which can bring lots of use cases
• WASM machine means that the smart-contracts could be made MUCH more advanced in comparison to the EVM. What’s more, it is something new (so much chains are around EVM)
Cons
• Development speed on WASM is much lower that on the EVM. This fact is present due to the lack of the tools and the technological puberty of EOS and WASM itself
• EOS is still a beta and with every update you need to reconsider stated development pipeline
• Limited audience. The reason is in the registration process (not address generation as in the most of the systems) and creating an account is not free. EOS audience is much lower than the ETH one (260k+ vs. 10mln+)
A reminder for you: there are lots of use cases for both of the platforms and we don’t recommend using one certain. The key is in flexibility and everyone needs to enrich his stack.
