3 ms·

> Nope, the source code is linked and it's compact enough that you should be able to learn everything in about an hour. I don't doubt that somebody who wants t

> Nope, the source code is linked and it's compact enough that you should be able to learn everything in about an hour. I don't doubt that somebody who wants to learn this can do that in an hour as you say. But why would I invest one hour of my time to learn something I have no idea what it is !? I skimmed through the readme and wiki and all I see is something vague about how async is good and how stellar the performances are. The world is vast; the flood of information is a serious problem. My piece of advice to you fellow HN member is that the burden is on you to explain why something is interesting. Otherwise people will flock to crappy complex stuff, because unfortunately those are better explained.

bullen 5y ago
I'm not doing this for fame or money, I'm building a 3D MMO platform for eternity, so it's all or nothing: Either all I did in life will disappear or I'm making the next open Minecraft in which case everyone will use it anyway. I'm fine with both outcomes. Notch spent zero time documenting and he obfuscated the binaries, still more people know that reverse engineered source today than any other source to ever exist, maybe forever (unless I succeed)!
- jwhitlark 5y ago
  He's not saying you have an obligation to document your code, he's saying if you're going to add it to a discussion, you need to give us a one-sentence description of what it is so we can see how it is relevant and decide if we want to spend an hour getting to know the code. Basically, tell us what the value proposition of your comment is, otherwise it's just a link in a vacuum.
  - bullen 5y ago
    Most people have problems with persistence, it's a though subject until you realize most of the problem is fear caused by responsibility. Most databases (SQL) where designed before the internet, that is a major flaw in them and this instead uses HTTP from the start and JSON in regular files. So it's simpler. But it also has authentication, relational values, indexing and it's async. joint parallel distributed. So it's versatile and powerful without becoming complex and heavy! It allows you to have coherent data at many locations around the world without a big complex monster like described in the article. The only downside is disk space!
    - ithkuil 5y ago
      Can you give a one like description of the technique you use to achieve coherence?
      - bullen 5y ago
        It's very simple, on every insert/update/delete the node that receives the command calls all the other nodes async. and waits until they have made the call before it makes it and then responds. The id's are secure random longs, so collisions are rare. You can see the code in Root.send(...) or see the live trace by going here and pressing the Make button: http://root.rupy.se/node?make&info http://root.rupy.se/node?make&info
        ithkuil 5y ago
        So if one node fails (or the network fails), some nodes will have the new value, while other nodes won't have it. I'm confused about why you call this "coherence".
        bullen 5y ago
        The system only works for writes when every node is online. It's a tradeoff that is well worth the simplicity. To have fault tolerance for writes never really works and it's very wasteful. Specially when the nodes can be very reliable and report downtime for you to fix the issue manually if a node goes down. In 5 years of operation my home hosted cluster has better uptime than all cloud providers: AWS, GCP etc. for writes and 100% uptime for reads. I have blogged about how to make a 100% write uptime database here: http://talk.binarytask.com/task?id=4662372011677848884 http://talk.binarytask.com/task?id=4662372011677848884 But my conclusion is that it's a waste of time.
        ithkuil 5y ago
        This is a legit solution if your requirements allow it. I'd advise you to not be too bullish on the universality of this principle of yours. Unfortunately real life is often more complicated than the scenario you describe and I wouldn't describe the solutions smart people came up with (various consensus algorithms or convergent replicated data types) as a waste of time.

bullen 5y ago

I'm not doing this for fame or money, I'm building a 3D MMO platform for eternity, so it's all or nothing: Either all I did in life will disappear or I'm making the next open Minecraft in which case everyone will use it anyway. I'm fine with both outcomes. Notch spent zero time documenting and he obfuscated the binaries, still more people know that reverse engineered source today than any other source to ever exist, maybe forever (unless I succeed)!

jwhitlark 5y ago
He's not saying you have an obligation to document your code, he's saying if you're going to add it to a discussion, you need to give us a one-sentence description of what it is so we can see how it is relevant and decide if we want to spend an hour getting to know the code. Basically, tell us what the value proposition of your comment is, otherwise it's just a link in a vacuum.
- bullen 5y ago
  Most people have problems with persistence, it's a though subject until you realize most of the problem is fear caused by responsibility. Most databases (SQL) where designed before the internet, that is a major flaw in them and this instead uses HTTP from the start and JSON in regular files. So it's simpler. But it also has authentication, relational values, indexing and it's async. joint parallel distributed. So it's versatile and powerful without becoming complex and heavy! It allows you to have coherent data at many locations around the world without a big complex monster like described in the article. The only downside is disk space!
  - ithkuil 5y ago
    Can you give a one like description of the technique you use to achieve coherence?
    - bullen 5y ago
      It's very simple, on every insert/update/delete the node that receives the command calls all the other nodes async. and waits until they have made the call before it makes it and then responds. The id's are secure random longs, so collisions are rare. You can see the code in Root.send(...) or see the live trace by going here and pressing the Make button: http://root.rupy.se/node?make&info http://root.rupy.se/node?make&info
      - ithkuil 5y ago
        So if one node fails (or the network fails), some nodes will have the new value, while other nodes won't have it. I'm confused about why you call this "coherence".
        bullen 5y ago
        The system only works for writes when every node is online. It's a tradeoff that is well worth the simplicity. To have fault tolerance for writes never really works and it's very wasteful. Specially when the nodes can be very reliable and report downtime for you to fix the issue manually if a node goes down. In 5 years of operation my home hosted cluster has better uptime than all cloud providers: AWS, GCP etc. for writes and 100% uptime for reads. I have blogged about how to make a 100% write uptime database here: http://talk.binarytask.com/task?id=4662372011677848884 http://talk.binarytask.com/task?id=4662372011677848884 But my conclusion is that it's a waste of time.
        ithkuil 5y ago
        This is a legit solution if your requirements allow it. I'd advise you to not be too bullish on the universality of this principle of yours. Unfortunately real life is often more complicated than the scenario you describe and I wouldn't describe the solutions smart people came up with (various consensus algorithms or convergent replicated data types) as a waste of time.