You are viewing a single comment's thread from:

RE: Hive Developers Are Kicking Ass

in LeoFinance10 months ago

I've compiled the list, so it is easier to recollect when the time comes to implement any of those ideas (if ever). The descriptions are probably not fully understandable to people not engaged in development as it requires quite a bit of insider knowledge. What can be seen from it, is how long it can take to get stuff done. Some of the points were first discussed before HF24. Most of the optimizations I've already described in article 20 months ago and only now one is actually being actively worked on. But I guess it is because there is no real pressure to improve hived code itself, unless it is needed for second layer applications (lately it was mainly HAF). Instead there are second layer lite accounts on the table, some API overhaul, first steps of design of HAF based smart contract engine etc. so quite a lot of work that is not even on that list.

Sort:  

Yeah. I sensed that reading through the list. It did spell out the order which some things will have to go (if they are ever addressed).

I applaud your efforts to get more ideas on the table and try to bring some things to the forefront of getting coded. It is tough when people have different ideas of what is required.

One of the drawbacks of blockchain is how slow moving it can be. Of course, one of the advantages of blockchain is how slow moving is can be.