4 ms·
> However the failure of GoChat is not relevant to Pokemon Go. That part is almost right, but also a little confused. He built GoSnaps, which is a geo-enabled
by Mithaldu 10y ago
> However the failure of GoChat is not relevant to Pokemon Go.
That part is almost right, but also a little confused.
He built GoSnaps, which is a geo-enabled gallery with: No chat, few messages, few writers, many readers, medium amount of reads, large messages, not time-dependent. (Not even user state.)
Then he contrasts that to the failure of GoChat, which is a geo-enabled chat with: Many-to-many chat, many messages, many writers, many readers, many read operations, small messages, very time-dependent.
The performance profile between these two things is wildly different and the way he's patting himself on the back over what amounts to half knowledge is pretty disgusting.
- alex_hitchins 10y agoThere is a real feeling of superiority in his post based on his own assumptions (in terms of the other apps stats). I always think it's best to constructivly critique something by not trying to promoting yourself in doing so.
- cloudjacker 10y agowhat if he just didn't mention gochat? its an awesome post
- jonzathe 10y agoFailure of GoChat? GoChat didn't fail, it just had some hurdles it needed to jump. GoChat is back up 100% baby! (I'm the guy who started GoChat). I reached out to the author of this story and he has since updated his story. I now have a team of 6 dedicated guys helping me full time on this and we're cruising forward.
- Mithaldu 10y agoThat is great to hear. Good work! Sorry i can't edit the post anymore, otherwise i'd update that. :) Edit: Wow, he did update it and he's only defending his bullshit with more half-knowledge. At this point i'm ready to call him a liar, just over this claim: "My conclusion is that both apps are very similar in terms of scalability complexity."