Nxt source code analysis (QA)

[Come-from-Beyond]

Still not convinced you have a handle on your memory problem just because you are using Java nio.   Did you happen to have coded a memory caching algorithm so that your java code knows when to take and replace what's in your memory mapped file?  I doubt it,  that would be akin to writing your own object oriented database.

Man, I see u r so stupid not so smart, so I'll put u back into ignore list for a week. C u later.

[FrictionlessCoin]

Still not convinced you have a handle on your memory problem just because you are using Java nio.   Did you happen to have coded a memory caching algorithm so that your java code knows when to take and replace what's in your memory mapped file?  I doubt it,  that would be akin to writing your own object oriented database.

Man, I see u r so stupid not so smart, so I'll put u back into ignore list for a week. C u later.

I guess your answer to my query was.... "I guess I didn't think about that... will go back to the drawing board and try to figure this out.... see you in a week."

Well let's hope that NXT is still alive in a week's time.

[Meizirkki]

Kind of Post Scriptum to previous analysis.

1. Java and it's unpredictable object's size, nice article in russian (sorry, guys ).
2. For those who don't look deeper: 10000 blocks is just 10 days in current rate (AFAIK, we're still not getting desired 1440 blocks per day). Ten days to kill big part of our decentralized network. And ten days more to kill the rest.
3. There will be short-time paradise for miners 255 coins every minute. Wow.
4. I believe that if such kind of attack will start, devs fix the problem in one or two day, so it is actually not a reason to sell you coins. Just some funsy math. Do you remember how fast C-f-B redo NRS from self-written http code to Jetty? Moving blockchain to DBMS is the same, more or less.

That's why bitcoind uses leveldb.  It would be joke to keep the entire block chain in memory.

So you are saying this NXT keeps the entire block chain in memory?  

Pathetic.

I mean, they likely haven't done any analysis of what kind of database to use as a backend.   There is no way that they'll be able to fix this problem in time for folks to realize that they can spam the network and blow up every JVM that sits on this network!

Well... clock is ticking....  waiting on the dbms implementation....

Also,  realize that they use Java serialization to store the transactions in file....  

So when these JVMs go 'out of memory error'... they can't save the transactions file.... and even if they do... that'll blow up!

HILARIOUS!

DO I GET THE PRIZE FOR SEEING THE FATAL FLAW!

*Applause*

All you do is come around and flip shit on every nxt thread. If the code is so shit just fix it and move on to making the fork you were planning.

[instacalm]

Well let's hope that NXT is still alive in a week's time.

Stop being like that FrictionlessCoin, what's your use of being so bothersome? From a psychological standpoint it is obvious that those posts of yours derive from jealousy.

You think you are so great... yet there is nothing worthwhile of yours to see? Where's constructive criticism? Where is your from scratch next gen currency? All I can see is that you are trying to push a dead ship called IXCoin, that's it. Face it and redefine yourself, please. It is boring to read your posts, you know?

[FrictionlessCoin]

Kind of Post Scriptum to previous analysis.

1. Java and it's unpredictable object's size, nice article in russian (sorry, guys ).
2. For those who don't look deeper: 10000 blocks is just 10 days in current rate (AFAIK, we're still not getting desired 1440 blocks per day). Ten days to kill big part of our decentralized network. And ten days more to kill the rest.
3. There will be short-time paradise for miners 255 coins every minute. Wow.
4. I believe that if such kind of attack will start, devs fix the problem in one or two day, so it is actually not a reason to sell you coins. Just some funsy math. Do you remember how fast C-f-B redo NRS from self-written http code to Jetty? Moving blockchain to DBMS is the same, more or less.

That's why bitcoind uses leveldb.  It would be joke to keep the entire block chain in memory.

So you are saying this NXT keeps the entire block chain in memory?  

Pathetic.

I mean, they likely haven't done any analysis of what kind of database to use as a backend.   There is no way that they'll be able to fix this problem in time for folks to realize that they can spam the network and blow up every JVM that sits on this network!

Well... clock is ticking....  waiting on the dbms implementation....

Also,  realize that they use Java serialization to store the transactions in file....  

So when these JVMs go 'out of memory error'... they can't save the transactions file.... and even if they do... that'll blow up!

HILARIOUS!

DO I GET THE PRIZE FOR SEEING THE FATAL FLAW!

*Applause*

All you do is come around and flip shit on every nxt thread. If the code is so shit just fix it and move on to making the fork you were planning.

You know why I hang out in the Nxt threads?

Because you can learn a lot from the mistakes of others.

[FrictionlessCoin]

Well let's hope that NXT is still alive in a week's time.

Stop being like that FrictionlessCoin, what's your use of being so bothersome? From a psychological standpoint it is obvious that those posts of yours derive from jealousy.

You think you are so great... yet there is nothing worthwhile of yours to see? Where's constructive criticism? Where is your from scratch next gen currency? All I can see is that you are trying to push a dead ship called IXCoin, that's it. Face it and redefine yourself, please. It is boring to read your posts, you know?

I am not the only person who is warning you folks about the NXT memory problem.

The other dude (Alex something) is saying a similar thing.

If this thing is not fixed quickly... then this is a dead coin very quickly.

[FrictionlessCoin]

Where is your from scratch next gen currency? All I can see is that you are trying to push a dead ship called IXCoin, that's it. Face it and redefine yourself, please. It is boring to read your posts, you know?

Solid technology is not written in a short time.  I takes weeks or months to create something really solid.  Not like NXT that was written in less than a week.  Take for example eMunie,  the guy has been working for 6 months already and he has not launched yet.   The Next Gen Currency (TNG) takes time.

iXcoin... has like 5 peta hash per second in its network.   It may not be as popular today as DOGEcoin but the applications of such a network are tremendous and I see it as a good platform that a lot of people would like to leverage.  

My interest in NXT however is more on the lines of 'what not to do when creating a new coin'.  It is always cheaper to learn from other people's mistakes.  Kind of like the Edsel which was a flop, but it was followed by the Ford Mustang which was wildly successful.  So as I learn from NXT mistakes,  I can build a better Next Gen Currency.  Hmm... (NGC) has a nice ring to it.

[ciappa]

Hello,

I speak very bad English!
Can anyone explain what happened to someone nextcoin easy? Is the source code so bad?

thank you

[NxtChoice]

The core of Nxt is the idea and thought of Nxt, say TF.  Software engineering and database are important, but they are not beyond the present technology. We can do it even in a short time. The stakeholders will donate to hire more DB experts, and I will also donate if some one organize it.

[FrictionlessCoin]

The core of Nxt is the idea and thought of Nxt, say TF.  Software engineering and database are important, but they are not beyond the present technology. We can do it even in a short time. The stakeholders will donate to hire more DB experts, and I will also donate if some one organize it.

Ideas are a dime a dozen.

I am not sure if NXT has any good ideas.

But rest assured,  if I discover that it does,  then it will be incorporated in the Next Gen Currency (NGC).

[nexern]

Hello,

I speak very bad English!
Can anyone explain what happened to someone nextcoin easy? Is the source code so bad?

thank you

no, a tiny brain (FrictionlessCoin) is far overwhelmed to read the code that way to understand
the inner workflow and desperately trying to cover his more than once showed insufficient
knowledge by focusing on code beauty details. instead stopping this before it's going more
and more ridiculous for him, he is to long on this road, so (unfortunatly for him) he has to
go on with this nonsens.

this code review has added some very good improvements so far from some very good java
coder but nobody has found any serious problem nor the flaws as far i can see.

please correct me if i am wrong.

[instacalm]

I am not sure if NXT has any good ideas.

Every post you provided has proven that you are indeed clueless.

I've said it before, if you think you are oh so great then prove it. Until now there's nothing, nada, except your envy.

Last post dedicated to you. Back to topic, source code analysis.

[achimsmile]

no, a tiny brain (FrictionlessCoin) is far overwhelmed to read the code that way to understand
the inner workflow and desperately trying to cover his more than once showed insufficient
knowledge by focusing on code beauty details. instead stopping this before it's going more
and more ridiculous for him, he is to long on this road, so (unfortunatly for him) he has to
go on with this nonsens.

this code review has added some very good improvements so far from some very good java
coder but nobody has found any serious problem nor the flaws as far i can see.

please correct me if i am wrong.

Can't correct you, IMO everything in your post is true!

[ciappa]

ok, so what you're saying is that the entire next code is not good? Is next doomed to fail?

[nexern]

ok, so what you're saying is that the entire next code is not good? Is next doomed to fail?

code -> good -> nxt -> good

[FrictionlessCoin]

ok, so what you're saying is that the entire next code is not good? Is next doomed to fail?

code -> good -> nxt -> good

code -> bad -> bugs -> fail

[bitcoinpaul]

You know why I hang out in the Nxt threads?

You write some garbage and you get honest answers from CfB. You are trolling around to learn a few tricks from CfB. This is just dishonorable.

I have the impression you don't want to be friendly and nice, FrictionlessCoin. Please, just go. Thank you.

[nexern]

because it fit's into this thread just on thing which has attract my attention.

i have to admit that i am not a native java coder and i just have had a quick look at
the api part due to the client dev, therefore this could be nonsens but for me, the code
structure seems that the creator intentionally veiled his native codingstyle.

if so, i bet the flaws couldn't be found by hunting partial code strucs but more within the
logical flow in general. moreover, if this is correct, the energy needed to change a perhaps
long used coding style this way must be immense. at least there is no chance to get any
usefull code correlation this way.

as said, it could be totally wrong but i have seen many lines of code in different
languages, this structure doesn't seems coincidental for me.

perhaps a fluent java coder could have a quick overview again, with this in mind.

[FrictionlessCoin]

You know why I hang out in the Nxt threads?

You write some garbage and you get honest answers from CfB. You are trolling around to learn a few tricks from CfB. This is just dishonorable.

I have the impression you don't want to be friendly and nice, FrictionlessCoin. Please, just go. Thank you.

If you are an expert in a field and you see an amateur do very shoddy work, the I think one would have the responsibility of pointing this out.

The work here is plain and simple shoddy.

Maybe the ideas may make sense (don't know,  I have not seen the spec),  but the work is shoddy.

[bitcoinpaul]

because it fit's into this thread just on thing which has attract my attention.

i have to admit that i am not a native java coder and i just have had a quick look at
the api part due to the client dev, therefore this could be nonsens but for me, the code
structure seems that the creator intentionally veiled his native codingstyle.

if so, i bet the flaws couldn't be found by hunting partial code strucs but more within the
logical flow in general. moreover, if this is correct, the energy needed to change a perhaps
long used coding style this way must be immense. at least there is no chance to get any
usefull code correlation this way.

as said, it could be totally wrong but i have seen many lines of code in different
languages, this structure doesn't seems coincidental for me.

perhaps a fluent java coder could have a quick overview again, with this in mind.

Interesting.