I've been trying every which way to install Solidity in my geth console- why? -because the outdated tutorials recommend to do that- and as a programmer you need to have the disposition of not accepting "no" for an answer from a stupid computer- need to just keep hacking away at it until you can get the damn thing to do what you want- or you'll go nowhere- so- speaking of going nowhere- back to the point of this question...

I've decided- after consulting multiple pages across the web and this website that I should just find a different way to compile my smart contracts- probably using this remix thing

so before I concede defeat to this task- I want to know- what are the relative merits of compiling smart contracts within the geth console? Why was it put in there in the first place? Why was it removed?


The reasoning behind the change is here: https://github.com/ethereum/EIPs/issues/209

This has caused some controversy here: https://github.com/ethereum/go-ethereum/issues/3793

To be honest I think this is more of a "documentation" issue than a "tech" issue. The docs should be updated to reflect how the tech works, rather than having the tech held back by what (old) docs say.

It's not that big of a deal to install truffle separately or solc separately and do your compilations outside of geth. See How to compile Solidity contracts with Geth v1.6? for more details.

  • cool- yeah- I mean- I agree that compiling programs in a console is wacky- it's just that- if the docs say I should be able to do it- I want to give it a try- and if at first you don't succeed... and so on- thanks for these resources Jul 25 '17 at 20:09
  • 1
    I went through the same experience! Updating the docs seems a low priority these days. Jul 25 '17 at 20:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.