BitShares Forum
Main => General Discussion => Topic started by: davidpbrown on April 08, 2016, 10:36:07 pm
-
@bitsapphire et al - Any update from Moonstone?.. I've been out the loop but happy to now have BitShares2.0 working and then hoping other areas still progressing well.
-
@bitsapphire et al - Any update from Moonstone?.. I've been out the loop but happy to now have BitShares2.0 working and then hoping other areas still progressing well.
Cob gave an update and mentioned how graphene code has some major issues that prohibit scaling... Said moonstone is being held back by these issues
-
@bitsapphire et al - Any update from Moonstone?.. I've been out the loop but happy to now have BitShares2.0 working and then hoping other areas still progressing well.
Cob gave an update and mentioned how graphene code has some major issues that prohibit scaling... Said moonstone is being held back by these issues
I call BS on that statement. Moonstone is never coming imo, smelled bad from the start and their continued silence just confirms that.
Sent fra min MotoG3 via Tapatalk
-
@bitsapphire et al - Any update from Moonstone?.. I've been out the loop but happy to now have BitShares2.0 working and then hoping other areas still progressing well.
Cob gave an update and mentioned how graphene code has some major issues that prohibit scaling... Said moonstone is being held back by these issues
I call BS on that statement. Moonstone is never coming imo, smelled bad from the start and their continued silence just confirms that.
Sent fra min MotoG3 via Tapatalk
I was busy when I first read cob's email, so I kind of glossed over the specifics of that part of it. But reading it again, what he relayed about the Graphene wallet doesn't sound even remotely accurate. After all, many people are using Bitshares browser wallets without any problems. So who gave him that information, bitsapphire?
-
@bitsapphire et al - Any update from Moonstone?.. I've been out the loop but happy to now have BitShares2.0 working and then hoping other areas still progressing well.
Cob gave an update and mentioned how graphene code has some major issues that prohibit scaling... Said moonstone is being held back by these issues
I call BS on that statement. Moonstone is never coming imo, smelled bad from the start and their continued silence just confirms that.
Sent fra min MotoG3 via Tapatalk
Yeah, I wouldn't be betting the farm on it, either. From my understanding of cob's update, he isn't relying on Moonstone per se. He simply mentioned that Moonstone is trying to address some of the same problems he's facing. I'd love to get a perspective from a BitShares Graphene person ( @bytemaster ?) on the Graphene scalability issue that cob discusses in his thread (link below).
https://bitsharestalk.org/index.php/topic,22171.msg289021.html#msg289021 (https://bitsharestalk.org/index.php/topic,22171.msg289021.html#msg289021)
-
Guys, think about it... Scaling issues come up AFTER the thing has been implemented. Like they're load-testing Graphene instead of writing a wallet?
<DELETED FROM NET> <-- Tonyk sent me messages that I was being too frank
-
@bitsapphire et al - Any update from Moonstone?.. I've been out the loop but happy to now have BitShares2.0 working and then hoping other areas still progressing well.
Cob gave an update and mentioned how graphene code has some major issues that prohibit scaling... Said moonstone is being held back by these issues
I call BS on that statement. Moonstone is never coming imo, smelled bad from the start and their continued silence just confirms that.
Sent fra min MotoG3 via Tapatalk
I have a feeling they tried to use emscripten to port the C++ cli_wallet over to js which would explain the huge js files and scalability issues ..
-
Having multiple options for wallets can only help BitShares appear flexible and useful for different interests; so, hope they keep working on it.