What are the advantages/disadvantges of various web frameworks like Django, Ruby on Rails, Flask, etc when it comes to Bitcoin? Are some better at interfacing with the daemon than others? Do some implement security better or have holes that make them inappropriate for bitcoin development? Which is the best?

closed as off topic by cdecker, o0'., ThePiachu, Colin Dean, Highly Irregular Jan 25 '13 at 9:11

Questions on Bitcoin Stack Exchange are expected to relate to Bitcoin within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    Note people who voted to close: Make it a habit to write a comment when you participate in closing a question so that the person who wrote it knows what was wrong about it. It is not necessarily obvious in this question. – D.H. - bitcoin.se Jan 25 '13 at 11:51
  • 1
    Hi Kinnard, just wanted to let you know the reason this was closed is that it's really more of a programming question than a bitcoin question. To be more precise, the users who can effectively answer this question are more likely to be found on a programming stack exchange than on this one. – eMansipater Feb 8 '13 at 4:53

Bitcoin wallet development usually involves communicating with either bitcoind through HTTP JSON RPC, or otherwise with other Bitcoin Clients through the Bitcoin Protocol over TCP. On top of that, there are the usual requirements of authenticating users, securing data and so forth. All of those security issues are not Bitcoin specific, thus I think this question would be better asked elsewhere.

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