Another client is useful, especially since the current Bitcoin client is a big mess. I was *shocked* that cryptography code looked like this.
Can you be more specific? What exactly makes it a 'mess'?
Topic: minimalistic bitcoin client on D language? - page 2. (Read 10902 times)
Another client is useful, especially since the current Bitcoin client is a big mess. I was *shocked* that cryptography code looked like this.
I'd like to hear some specific criticisms of the code. To me it looks like an impressive job, although I'd wish for more comments. Now I've mostly studied the init, main, script and a bit of net modules. This is some powerful machinery. 
Here we are with the Language war once again. Please just stop!
As for the topic, yes please get an alternative implementation started, the more the merrier
Maybe some good code actually makes it out there, helping future generations of clients to build on top of your code.
+1 on the D implementation (I'm starting a Java one in the holidays)
As for the topic, yes please get an alternative implementation started, the more the merrier
Maybe some good code actually makes it out there, helping future generations of clients to build on top of your code.
+1 on the D implementation (I'm starting a Java one in the holidays)
Another client is useful, especially since the current Bitcoin client is a big mess. I was *shocked* that cryptography code looked like this.
I bet you're also shocked by what restaurant kitchens look like, and by what goes into sausages.
The cryptography code that competent people use, doesn't look like a mess, btw. That 99% of the world uses this kind of obfuscated cryptography only shows that users don't know what they use. Have you ever looked at TrueCrypt for example? It's the exact same kind of mess.
Another client is useful, especially since the current Bitcoin client is a big mess. I was *shocked* that cryptography code looked like this.
I bet you're also shocked by what restaurant kitchens look like, and by what goes into sausages.
Another client is useful, especially since the current Bitcoin client is a big mess. I was *shocked* that cryptography code looked like this.
You want to re-implement the entire client?
Why make a convenient wrapper around the JSON API? That's much easier and just as useful.
Why make a convenient wrapper around the JSON API? That's much easier and just as useful.
It's just not as fun !
I would love a ruby bitcoin client so much !!
You want to re-implement the entire client?
Why make a convenient wrapper around the JSON API? That's much easier and just as useful.
Why make a convenient wrapper around the JSON API? That's much easier and just as useful.
It's pointless, I think. There is may be a "multidimensional" result.
Use jsawk:
Code:
$ ./bitcoin listreceivedbylabel | jsawk -n 'out(this.label+" "+this.amount+" "+this.confirmations)'
user_id:1080 106 5189
user_id:1081 0.05 5557
user_id:1083 2.89 2800
user_id:1087 500 5276
user_id:1105 0.4 462
user_id:1109 0.1 922
user_id:1110 0.04 431
python
I don't like IndentationErrors
perl
Not gonna criticize what I don't know
or java 
I'll leave you the bob = new InstanceLocatorFactoryProxyWrapper
I do not like ruby, python, perl or java
Well, I don't like C or Java or anything else that uses braces. 
I wrote a bitcoin daemon wrapper in Ruby
Fully extensible since it's heavily based on method missing
EDIT : Made it for Rails so it includes a lovely initializer and a sweet yml configuration file
I'll have to spend some time playing with it over the winter break. Any thoughts on keeping a server running bitcoind relatively secure? It seems like having a wallet.dat file on a publicly-accessible server is an accident waiting to happen. Fully extensible since it's heavily based on method missing
EDIT : Made it for Rails so it includes a lovely initializer and a sweet yml configuration file
You want to re-implement the entire client?
Why make a convenient wrapper around the JSON API? That's much easier and just as useful.
Why make a convenient wrapper around the JSON API? That's much easier and just as useful.
I do not like ruby, python, perl or java
I wrote a bitcoin daemon wrapper in Ruby
Fully extensible since it's heavily based on method missing
EDIT : Made it for Rails so it includes a lovely initializer and a sweet yml configuration file
Fully extensible since it's heavily based on method missing
EDIT : Made it for Rails so it includes a lovely initializer and a sweet yml configuration file
+1 on Ruby. Didn't someone recently write a Ruby interface to bitcoind?
If you're bored you should learn some Ruby it's really sweet !
Maybe then wait bitdns?
I'm just bored and a want to write a code
I'm just bored and a want to write a code
I think to start writing a minimalistic bitcoin client on D language. Do you think this makes sense?
The more implementations we have, the better.
Unfortunately, writting a client is no easy task. Satoshi's code is far from from trivial.
I think to start writing a minimalistic bitcoin client on D language. Do you think this makes sense?
Jump to: