Sorry, but coming from an embedded world the use of Real-time here seems borderline offensive to me. Anyone care to explain what it means in this context? From the dawn of computer science it has been about strict time guarantees - and I highly doubt this is what's being referred to here.
Horizon 1.0: a realtime, open-source JavaScript back end from RethinkDB
121–130 of 133 posts
Re: Horizon 1.0: a realtime, open-source JavaScript back end from RethinkDB
#122Sorry, but coming from an embedded world the use of Real-time here seems borderline offensive to me. Anyone care to explain what it means in this context? From the dawn of computer science it has been about strict time guarantees - and I highly doubt this is what's being referred to here.
Re: Horizon 1.0: a realtime, open-source JavaScript back end from RethinkDB
#123Re: Horizon 1.0: a realtime, open-source JavaScript back end from RethinkDB
#124Re: Horizon 1.0: a realtime, open-source JavaScript back end from RethinkDB
#125Hey guys, Slava @ Rethink here. The team is really excited to launch Horizon -- it's based on a lot of feedback from users of very different backgrounds, and we think it will make web development dramatically easier. I've been up for about twenty-four hours, but I'll be around to answer any questions for the rest of the day.
Hi, Slava, I was a web developer and now I am a mobile developer. Nobody is developing web applications anymore (at least in developing countries). We are all mobile first. How does android or ios developers take advantage of Horizon ? Can you give a few examples? How does horizon make mobile (native) developers life easier ? web development is slowing down and mobile development is on the rise. Mobile developers don…
Re: Horizon 1.0: a realtime, open-source JavaScript back end from RethinkDB
#126Although this is about horizon, if you haven't looked at RethinkdB you should definitely check it out. It's an awesome database for a variety of use-cases. Personally, I think their query language + support for joins makes it much more useable than MongoDB (which I've used quite a bit).
But man was I sad to leave RethinkDB for that!
Re: Horizon 1.0: a realtime, open-source JavaScript back end from RethinkDB
#127Earlier quoted context omitted.
This is awesome, really looking forward to it. Rethinkdb is my goto database for everything nowadays, and I tell everyone I meet about it. Also: kudos to whoever is handling the artwork/marketing side of things. Love the vector art and website designs.
Christina from RethinkDB here (I work on all things community)... I'll pass the kind words along to our co-founder Mike G. who worked countless hours on the website, plus Annie Ruygt who does the artwork! It's wonderful to hear positive feedback since we do most of our design in-house :D
Re: Horizon 1.0: a realtime, open-source JavaScript back end from RethinkDB
#128Saw a demo of this at a realtime meetup in Palo Alto and was pretty impressed. Like everything RethinkDB does I anticipate it will be a fantastic one-two punch of sound engineering and smooth user experience.
Awesome! Was it Mike Seid's demo? Will have video up soon. Thanks for stopping by our meetup :D
Re: Horizon 1.0: a realtime, open-source JavaScript back end from RethinkDB
#129Sorry, but coming from an embedded world the use of Real-time here seems borderline offensive to me. Anyone care to explain what it means in this context? From the dawn of computer science it has been about strict time guarantees - and I highly doubt this is what's being referred to here.
Real-time in the web world means you don't need to hit the F5 or refresh button.
Re: Horizon 1.0: a realtime, open-source JavaScript back end from RethinkDB
#130Sorry, but coming from an embedded world the use of Real-time here seems borderline offensive to me. Anyone care to explain what it means in this context? From the dawn of computer science it has been about strict time guarantees - and I highly doubt this is what's being referred to here.
AFAIK, soft-real time has been a well known term since the 80s. It means that the quality of service degrades the longer it takes for a response to be returned, and eventually a response is worthless if enough time passes.