I mean it's essentially what steempeak does. If our users find an issue we fix it. Not sure what the issue is?
Steempeak has it easy we don't have to have consensus we just update but i mean this is software... find an error and fix it.
You are viewing a single comment's thread from:
Bugs in a front end are easily fixed on demand as you say. The situation is a lot different when dealing with a (supposed to be) immutable database. If there are bugs that corrupt the state, recovering from that can be very painful, or in extreme cases not even possible.
I agree that the development process is a bit light on testing. Ideally every operation would have a comprehensive set of unit tests across the full range of allowable inputs and states, as well as random (fuzz) tests, but this is actually very difficult to achieve in practice. Hopefully the developers will make steps in that direction though.
Yes and this bug is not painful nor extreme.
That does appear to be the case but when bugs aren't caught in testing it indicates a risk of other more painful or extreme bugs also getting through.
As much as I love Steempeak and obviously the good work of your hands and that of your team, I beg to differ. A front end and the what is essentially the foundation that front end resides cannot compare.
I feel most witnesses no longer resonate with other steemians struggling to make something on the chain. I am still waiting to see if this hard fork actually does anything to improve manual curation. I doubt it. Heavily! 😬😬
Posted using Partiko Android
This hardfork is just a matter of fixing a delegation bug. I'm thinking you're talking about last hardfork?
Yes. It was in response to this.
Bugs will always be discovered even months into the latest hardfork so that doesn't concern me as much.
I was just addressing something that I have been overly concerned with since HF21 was announced. But now that it is here let us see what it brings.