It definitely *is* open source but not just *anybody* can rewrite the code - to do that you would need to understand not just the C++ language (which I don't think anyone here is arguing is easy itself) but also boost (a big library which I actually don't use) as well as the other libraries that are being used in the project.

Even the devs themselves missed the subtleties of BerkleyDB that led to the temporary "hard-fork".

In short - no-one is going to come up with a 100% compatible Bitcoin equivalent in another language without a *lot* of work (a point that has been argued in various other threads - the problem was that Satoshi wrote the spec *after* he wrote the code).

And would they be able to tell us when someone is using a "sock puppet" or not?

In C they can indeed make sense - but in C++ they present problems that the language itself does *not* provide guarantees for (in regards to safe exception handling).

So in C++ "goto" really is a "no no" (for error handling as the "goto" in this topic was originally referring to you should just use a "throw").

The *only* reason that *goto* was not *dropped* as a keyword from C++ was to keep backwards compatibility as much as possible with C.

So "fast and handy" they maybe - but in C++ they are 100% *wrong* (as any exception handling would get *screwed* by the *goto* as the language does not cater for this situation).

It goes the same for "setjmp" and "longjmp" (guess most don't remember those) - they can also *not* be used safely in C++ apps.

So then I think that *fundamentally* what we are really looking at identifying is which are the *wrong* patterns and how they should be reworked and also how any *unreadable* code should be changed to make it more readable.

This would be a much more productive direction than just having a "language war" (which never gets anywhere that I've seen in following such things since using Usenet back in the early 90's).

(I also don't think that Bitcoin should be *exclusively* C++ as I do support the idea of eventually there being a Bitcoin protocol RFC type document that *could* be implemented in any decent language).

Whilst I am an advocate of C++ (and don't see any reason to change the language at all) I think in any case the importance is the choice of algorithms and design patterns not the language itself.

Any language that provides the correct semantics with reasonable enough performance and is readable should be acceptable.

BTW - all the C++ haters should have a list of bugs that *crash* the bitcoin-qt client (and lose people BTC) - could we have a list please just so we have an idea of how *broken* it actually is?

(and if it is not broken then why are people arguing it *needs* to rewritten in another language?)

People who repeatedly type C++ sucks *suck*.

Yup - if you would like to help out then maybe I could offer you something to do so (plenty of critics but very few doers on this website).

BTW - a new design is coming (eventually) so please just *bear with it* for now (I am a programmer not a graphic designer).

So in a nutshell - a Project Manager will create a new Project Area (which should be something general like "Client", "Server" or "Scripts") and after giving the Project Area a (real) BTC address and any relevant Notes then Save it - after reviewing all details are correct then the Project Area can be set to Open (allowing it to be seen below the Project).

New Project Tasks are created in a similar way below a Project Area - most importantly for Project Managers to pay attention to is that the Review date and time for the Project Tasks is when they will review the bids (so not when the task must be delivered by but when it must be delivered on or after).

When a contributor makes a Bid on a Project Task then their Delivery date and time is when they are promising to have everything completed (including allowing enough time for review and changes) remembering that the Project Task *owner* does not have to *accept* their bid *before* the initial Review date and time (so if you think it would take you a week you should make it the Review date and time + 1 week at a minimum).

Also note that after you "save" your bid there are 2 more steps - 1st step is to "Check Balance" (to make sure you didn't put in a BTC address you didn't mean to) and assuming no surprises then you have the "Open Bid" button. DO NOT press this button unless you are 100% certain everything is correct (i.e. the BTC address and most importantly the date and time you have *promised* to deliver after all reviews and changes).

Well the budget for Moneychanger now "hotting up" to over 75 BTC so I am guessing more interested devs are going to start consider joining.

I would *please* recommend people to take the time to watch the top "slideshow" at http://ciyam.org so they can get a real understanding of the workflow.

This is designed as a "serious" system for Project Management - so when you Open a task bid you can't *change your mind* and if your task bid is *rejected* by the Project Manager or you yourself *cancel* it then that is also *final*.

Think of it as a bit like Bitcoin tx's - in the same way that they are not reversible neither are CIYAM Open "commitments" (so check, re-check and then re-re-check before you click buttons like Open, Accept, Reject and Cancel).

A lot of the more recent changes to C++ have been to make things *easier* (such as the new use of "auto") as well as to improve its *functional programming* limitations and other general improvements (such as no longer requiring a space between two '>' characters in order to avoid being confused with the '>>' operator).

The major *problem* it has was that unlike more modern languages it wasn't designed to do some of the things that it was later found to be able to do (some admittedly much worse than can be done in other languages) and so has had to *evolve* (and this evolution has been slow).

That evolution is still ongoing but I certainly understand that it is not appealing to many - if "beauty" is in the eye of the beholder then I can appreciate that C++ is the kind of language you would have had to have had quite a few beers before thinking of it as anything more than comely.

I will simply say that I did manage to build CIYAM which is a web application generating platform using C++ and using *no other framework* nor back-end scripting language.

So even if it does suck - it has enough going right with it to be able to do that much at least.

Languages are tools and as such are really only as bad as the hands of those who lack the skill to use them correctly (yes - most people do not have the patience to learn a language as difficult as C++ and I would probably not advise anyone to do so if they don't want to spend many years learning).

Of course you are aware that C++ *does* functional programming, along with procedural, object oriented, generic and let's not forget template meta programming (and actually the *last* one of these is the big *way forward* which basically *no other* language can do).

Probably correct although if a big "popup" did appear warning you that if you don't understand exactly what you are doing that you could well be being scammed might at least help (although I also agree it shouldn't be something that appears every time as that would be annoying for people that do know what they are doing).

I think the RPC console is already not so easy for non-techies to find (although I guess an *advanced* option could be used to hide/display the Debug Window menu item in the Help menu).

I do agree that the dumpprivkey suggestion is not a bad one (although if you displayed a similar warning when allowing the *advanced* option to even *get* to the Debug Window then you wouldn't need it just for that command).

Well the facelift is taking much longer than expected and as we have just recently had fellowtraveler (from Open Transactions) create a Moneychanger project (also known on this forum as the Holy Grail) I have decided to implement the Sign Up anyway.

You'll now notice a gold "key" in the top left of the screen (when you are not logged in) and next to it an icon for Google and other OpenID accounts.

So you can sign up in 1 of 3 different ways:

1) Navigate to https://ciyam.org/open (note the HTTPS) and click on the key to create a "traditional account" (requires an email confirmation).

2) Click on the Google/OpenID icon to sign up with an existing Google/OpenID account (requires a "user name" to be provided).

or

3) Navigate to http://ciyam.org/open (note the HTTP) and click on the key icon to do a GPG sign up (will send you a GPG encrypted email).

Link to the Moneychanger project:

http://ciyam.org/open/?cmd=view&data=20130606055250338000&ident=M100V137&chksum=a2a9d6d5

Note there have been a couple of minor hiccups with the system (too many changes and not enough testing in recent weeks - sorry) so please be patient (I will respond to messages generally within 12 hours).

Bug swatted and please note that after you create a save a Project Task Bid you then need to click "Check Balance" (to verify the BTC address balance is what you think it should be) and then "Open Bid" (it can't be edited after it has been "opened" so be sure all the details are correct first).

For those who do not want to use GPG in order to sign up please use https://ciyam.org/open (i.e. HTTPS) or if you prefer to use Google or another OpenID account click on the icon to the right of the "key" instead of the key itself.

Apart from a couple of the "meetups" I am not aware of any Chinese merchants accepting BTC (apart from Avalon who are actually a US registered company).

Just to be be clear - it is *of course* up to the Project Manager how long to wait to accept or reject a task (the system only mandates that the date and time you offer must be >= to the suggested Delivery date and time).

Ouch - I will look into this - in case it's relevant what browser?

In regards to the dates - you should provide the Delivery date that *you* are comfortable with (once accepted the Task will change to it). Be sure to allow time for review and rework.

Just to let you guys know that I am online now (and will be for at least a few more hours - living in China it is around 9:45pm here).

If you can't reach my on Skype then most likely I am asleep - but I will respond to any email within 12 hours or so.