So I guess despite me never claiming that I am a developer, my openly visible commits are there to demonstrate that I am also not incapable of developing.
If you're not incapable of developing, why you are making random git pulls from BBR and inserting them into XMR without an idea of what the code actually does? Semi-capable might of been a more appropriate word.
Actually, How did that gaffe slip past extensive peer-review by a team of no less than
seventeen experienced XMR developers?
Unless it wasn't actually reviewed and you have unfettered access to the repo.
Why did it take a developer of a competing project to point out your mistake so you can revert it?
I'm being a little harsh there, you had a long day and you were probably burned out dealing with the drama surrounding the attack. Understandable.
However it's a point made by zoidberg that if the XMR developers don't fully understand the commits they are implementing and just add features willy nilly from other project some damage
could of been done. Malicous backdoor could of been inserted into the XMR this way.
I see you making not so subtle insinuations that crypto_zoidberg is a glorified code monkey, If it wasn't for CZ there could potentially have a mtgox like situation on our hands with poloniex, you should be more respectful about background works. He has done some hand-holding on a number of occasions and you know it well. I actually checked out your git commits. Majority of them are version bumps, string replaces & single line additions. seems if zoidberg role is code monkey your role is secretarial duties- you are assigned to brush up on the verbiage and misc typos, But I suppose you prefer the role 'architectural visionary' or 'creative director' and consider pushing out code something mostly below you, but something you do to keep you occupied whilst you are having a morning croissant or on the shitter maybe?
True innovation does not come from code churn. It also does not come from design alone. It comes from straddling the line between well thought through design and the actual implementation. That is predominantly where the core team is and should be focused
Someones been practicing their best Jony Ive impression
. I agree with what you said about code volume being a useless metric. Anyone can hire 10 freelancers from bangalore. The only reason it was added to infographic was I heard someone ask if the project was dead due to lack of activity?? So the clear numbers are shown to demonstrate neither projects are stagnating, clearly the fact BBR has less cooks in the kitchen doesn't mean the broth is being cooked slowly, nor is the quality suffering.
About true innovation:
- True innovation starts with: Taking the time to develop an intimate understanding of the codebase you are working with, so you are unrestricted to expand freely without worry.
Example: auditing the Proof-of-work so it's not blatantly crippled upon launch. A third party good samaritan had to step in to fix Monero's initial borked code, Hardly inspired confidence in the 'real' team. He had this to say:
I took a look at the code and changed some extremely easy to spot "errors"
By the way, I'm not even a real coder, so whatever changes I made should be easy to spot; especially for experienced developers.
- True innovation starts with : Choosing block emission parameters from scratch, instead of just leaving them default because Greed won over in an arguably rigged vote
If there is anyone who considers the XMR emission schedule optimal and not just a necessary blemish that's good enough and will "have to do" (polar opposite of innovative) I would like to meet them.
- True innovation starts with: Designing a novel memory-hard blockchain based Proof-of-work function from scratch that's many times faster than the vanilla cryptonight PoW adopted in XMR, yet provides the same level of ASIC resistance. Something which the Monero developers admittedly tried to deny due to lack of understanding until they were educated by an authority on the subject BBR synchronized from scratch 20x faster than XMR. The difference will be smaller on usual day with same transaction flow but it's undeniably and provably faster
- True innovation starts with: Designing your cryptographic constructs with the future in mind. In an eloquent and frugal way BBR allows the network particpants to not take onboard more than they need to. The blockchain can be easily pruned, drastically reducing bloat. BBR is already a leader in terms of disk footprint- (5x smaller) such feature only serves to increase the gap.
we could go on, BBR baked in alias support, XMR devs dismissed it as a gimmicky feature, now they are adding in Aliases themselves
XMR community balked at the '1% tax' only to find themselves brainstorming for fundraising ideas for development funds now
BBR was built on a concrete foundation. This was a project dreamed up from scratch. Every detail was carefully planned.
XMR was not designed from scratch, it was cloned from another questionably shady developer, warts 'n all.
Some of the flaws have been polished out. It's completely fair to say there will be continued polishing but there are certain aspects such as the poor emission rate which will
never be fixed. It has to be swept under the rug or twisted with careful marketing to appear as positive feature. Because it was not their creation they do not have the luxury of choosing ideal parameters. Therefore it's built on a sandy foundation which is being retroactively strengthened but it will always remain less than ideal.
Would you consider the eloquent design from a database architect somehow less worthy than the moron that spits out a few classes for the DAL?
...Would you argue that the hours of design effort a UI specialist puts into making a wizard intuitive and beautiful should not have his efforts held high against the junior developer who wired up the buttons?
Maybe part of this is referring to Monero's ongoing work on moving blockchain out of RAM, or the work on outsourcing wireframe mockups to your unreleased, groundbreaking, this-changes-everything GUI that will allow auntie mabel to easily manage her ring-signature based cryptocurrency portfolio
Meanwhile I have tested a fully functional, clean and intuitive GUI released long ago by BBR; introduced without a whole lot of prior fanfare
I have tested and confirmed blockchain.bin dataset has been reduced in real life. The update was just pushed out, not with a ton of hand waving in advance. None of these are 'innovations' which are being slated for future release or hypothesised about in missives. They just get added then moved onto the next.
Seems if we make an analogy Monero developers
stole brought a phone and now just getting acquainted with learning how to use it as they go,while proclaiming they are masters leading the way whilst BBR developers already clearly familiar with the functions and keep mostly low-key just making updates- not so much talking but the work rate is high. . There is nothing wrong with this but you are liars to imagine you are the only ones innovating in this space.
With XMR all it ever is is 'ongoing work' more premature assured congratulatory self-pats on the back and more hubris eminating from core team. You can smell the superiority complex a mile off with you guys..the air is just thick with unwarranted supercilious
smug You seem to believe you've achieved enough critical mass to have won the race before it's even really started. The best part of avoiding the Monero circlejerk not having to deal with a community of insular elitists. You guys embarked on an orchestrated smear campaign to throw every other competing cryptonote coin under the bus and I have some pretty damming evidence including internal conversations implicating some of the more senior XMR community members in what (even to a casual observer with no skin in the game) is undeniably dirty tactics. As someone else put it some of your PR schemes would make goebbels blush. Rest assured I will elaborate on that when the dust starts to settle.
