Ok, so I take it as yes, myriadcoin is technically more secure and less easy to attack compared to bitcoin.

if iceland had white hats in their government with this kind of awareness and know-how, it would be a huge step forward for the entire world.

Secondary , god know , nobody will shout that he is exploiting a chain , besides BCX.

 When you're dealing with this massive number of people, it's obviously no longer an open source p2p currency project, but an actual corporation looking to make mega bucks.

Because of all the hyped launches that usually don`t have much to them, this coin was under the radar, it seems now people start to see what 5 algos into one coin means,diff is rising, price is catching up to the diff slowly, and it hasn`t any major exchanges, for this I am supporting the coin even with small donations to the bounty/reward for the dev, even if I don`t have impresive hashpower, this definetely has something to stick it out of the crowd.

Sent you some PMC

Sent 3 PMC now I have 1.5

The calculations are based on market cap predictions.  The price per coin changes based on the market cap and the amount of coins in circulation.

Nothing wrong with Java running server side.  The security hell that is java applets needs to die.  I personally don't install java client side not because it is any direct risk but out of fear that some browser exploit will enable java applet access.  If java applets were killed off an no longer supported by modern browsers I would have no issue with java client side either.  Most financial institutions and large enterprises use java server side.  

The issue isn't so much PHP as the way it was used.  As a side note, you can shoot of your own foot with any programming language, PHP just makes it easier than others.  I would use Python over PHP because dynamic typing and implicit (warningless) conversion between types just makes it to easy to create bugs which only occur run time.  Combine that with no test driven development and you got a recipe for hard to identify bugs.

Someone up thread said testing, testing, and testing.  That doesn't mean let me try to manually "test the hell out of this" it means things like unit testing, code coverage, mocking, automated test validation in build process, etc.  That is impossible with the code as written.  The code as written is untestable, unmaintainable, and undocumented.  Everything is a bunch of static methods, magic constants spread throughout, SQL code interspersed with business logic, mixed with formatting.  The few places where a constant should be used they decided to use a literal 100000000 for conversion from satoshi to Bitcoins.  Money values are handled as floats.  Everything is tightly coupled and poorly documented so if Mark ever did bring on additional programmers that would just be a timebomb waiting to go off.  You can get god's gift to programming but if other "lesser" programmers can make fatal mistakes with your code because it is fragile ... it is bad code.

I agree. I've worked as a software developer for 15+ years and this really is not that bad compared to some of the code out there. I was honestly expecting worse..

If Mark was knowingly running a fractional reserve since 2011, then I think this is clear-cut fraud with jail time involved.  If Mark was not aware of the theft, then it is just incompetence/negligence.  He would have an incentive to inject as much confusion as possible. 

Comparing that to all the other previous Bitcoin TV spots, such as: