Developing for the Ethereum World Computer – Revisited
Taking these different contexts into account, evaluating the different development environments is only possible by identifying the different aspects and value them according to the own preferred usage.
Aspects of Dapp Development
- Solidity Development / Solidity Environment
User can edit Solidity content in a text editor, there should be at least syntax highlighting.
Versioning is supported, eg. by enabling the user to check edited content into a versioning system, show diffs, apply patches, etc.
Modification of code by multiple users is supported, at minimum support of different versions of the code is possible to avoid conflicts.
A first Categorization and a Teaser
This is also a teaser for the upcoming blog posts, which will explain the environments in detail.
Solidity Browser / Ethereum Wallet
In terms of architectural styles, both environments represent minimalism. They are slim and handy, easy to use and fast to learn, but lack some functionality if real development “in the large” is necessary.
Ethereum Studio, the all-in-one-solution
The Ethereum Studio, in our opinion, resembles Deconstructivism. Why’s that? Because here all aforementioned aspects of software development are taken apart and are reconstructed to fit perfectly to Dapp development. This is an all-in-one-solution which we can really recommend, with two limitation: you have to agree to a uncertain pricing model (it just doesn’t exist right now, you can still test the product) and a “closed” environment, which works seemless and smooth, but expects you to let in to this tool and the development process.
But no other tool lets you test your code this easy with manual and even unit testing built into the environment.
Stay tuned for the detailed explanations of these great development tools.