Ethereum Fork - (IJCH) Microsoft Approach or will Haste Make Waste?
Ethereum Fork - (IJCH) Microsoft Approach or will Haste Make Waste?
IJCH - Inside JaiChai's Head (meaning: My warped, personal opinions and musings.)
From the Author
Salutations
I am JaiChai.
And if I haven't had the pleasure to make your acquaintance, it's very nice to meet a fellow Steemian.
The Microsoft Approach
In the early days of Microsoft, their corporate culture was driven towards being "the first one out there".
In other words, companies - especially in the software and technology industry, were (and for the most part, still are) hell-bent on being first to market; rather than ensuring their products are free of bugs.
Indeed, an unspoken axiom within the Microsoft organization was to get their software released as fast as possible first, THEN fix any subsequent bugs later.
Just think of how many Windows patches and upgrades we've all experienced in our lives.
Even to this day, complaints abound over the annoying "upgrading your app" wait time and/or degradation of computer performance during upgrade periods.
Unfortunately, interim patches and upgrades are a part of ensuring software viability and they're here to stay.
In essence, they attempt to address previously unknown vulnerabilities before a catastrophic hack or Denial of Service - DoS - attack.
In fact, many White Hat Hackers make their living off of the bounties rewarded when they find a major exploit and report it ahead of an actual hack to the companies that market the product.
On the corporate side of the fence, the mentality is that patches and upgrades extend the life of the current version and testing time of the next version; ideally a length of time sufficient to roll out a better future product.
Ethereum Hard Fork - Two Bugs Already Found
With just days before the scheduled Byzantium hard fork, two bugs have already been found.
The discovery of denial-of-service (DoS) attack vulnerability has forced ethereum's Geth software - an ethereum client used for the majority (roughly two-thirds) of ethereum nodes - to hastily create a new version of their client software.
Also, the next most utilized ethereum node software client, Parity, had to create ANOTHER - its fourth - version of their client software because of possible inadvertent partitionings of the network due to a "consensus bug" during the hard fork process.
See:
https://www.coindesk.com/ethereums-geth-client-finds-vulnerability-less-two-days-before-fork/
Personally, I find myself siding with the pundits advocating a precautionary delay in the hard fork - just to make sure.
To me, this is a clear case of "Fools rush in; where a prudent Angel may pause." scenario.
Granted, I have no idea what the overall ramifications of delaying the hard fork really are - only the power players of the inner circle and the Creator of the universe knows that.
But releases of software is not a new thing in the technology world and I bet given the choice between a crappy, vulnerability laden product and waiting a little longer, most people will logically choose the latter.
My recommendation is to pause.
IT IS THE PRUDENT THING TO DO.
By JaiChai
Many thanks for reading my post. And if you enjoyed it, please: Upvote, Follow, Comment and Resteem. - JaiChai "My mind was a terrible thing to waste..."
About the Author
JaiChai has been in the cryptocurrency space for over 6 years. He is an enigma, regarded by his cohorts as sarcastic, funny, intuitive - but most of all, elusive. JaiChai alternates long dormant periods with concentrated episodes of frenzied commentary - only to go silent again. He’s known for randomly submitting philosophical and contrarian posts on most cryptocoin forums.
When asked about his vanishing acts, he says, "I’m just somebody who enjoys being nobody because I look like everybody. Besides, time checking things off my 'bucket list’ - sans notoriety - is time well spent."
@minnowpond1 has voted on behalf of @minnowpond. If you would like to recieve upvotes from minnowponds team on all your posts, simply FOLLOW @minnowpond.
@royrodgers has voted on behalf of @minnowpond. If you would like to recieve upvotes from minnowponds team on all your posts, simply FOLLOW @minnowpond.
@cmtzco has voted on behalf of @minnowpond. If you would like to recieve upvotes from minnowponds team on all your posts, simply FOLLOW @minnowpond.
To receive an upvote send 0.25 SBD to @minnowpond with your posts url as the memo
To receive an reSteem send 0.75 SBD to @minnowpond with your posts url as the memo
To receive an upvote and a reSteem send 1.00SBD to @minnowpond with your posts url as the memo
@reported has voted on behalf of @minnowpond. If you would like to recieve upvotes from minnowponds team on all your posts, simply FOLLOW @minnowpond.
This post recieved an upvote from minnowpond. If you would like to recieve upvotes from minnowponds team on all your posts, simply FOLLOW @minnowpond.
@eileenbeach has voted on behalf of @minnowpond. If you would like to recieve upvotes from minnowponds team on all your posts, simply FOLLOW @minnowpond.