Re:Show HN: Real-time apps without the hassle
by taf2 on Thursday March 27, 2014 @09:10AM
(#7480103)
The main issue I see here is the use of a port other than 443 - this means traffic will likely be blocked for many users, also over 443 traffic should be encrypted to avoide bad proxies messing up the request headers
Re:Show HN: Real-time apps without the hassle
by simoncarter on Thursday March 27, 2014 @08:32AM
(#7479921)
Nice clean design. However, I'm not sure about the use-case you present on the website. If you're developing websocket enabled apps, you're going to have use get a socket server at some time, so why put it off?
Re:Show HN: Real-time apps without the hassle
by kristiandupont on Thursday March 27, 2014 @10:18AM
(#7480511)
Are you on a touch device or a Windows machine perhaps? Because to me, it feels smooth but too sensitive. And since scrolling is always smooth in osx, it only feels annoying.
Re:Show HN: Real-time apps without the hassle
by salmar on Thursday March 27, 2014 @11:13AM
(#7480859)
It has the same philosophy behind it, SimpleRT is simpler for now, has only a JS API and it's not meant to be used in production, just for development purposes. No signup needed, just use it and play around with it. We'll see how it evolves
Re:Show HN: Real-time apps without the hassle
by mariusz79 on Thursday March 27, 2014 @08:15AM
(#7479850)
Can you, JS People, please stop calling your apps "real time"? If you've ever written one true real time application, you would not be calling your web apps "rt"
(Action Stations, Action Stations - Downvoting imminent. Prepare for impact)
Re:Show HN: Real-time apps without the hassle
by kasey_junk on Thursday March 27, 2014 @08:58AM
(#7480040)
Seriously. Generally I don't get freaked out about the dynamic nature of language, but in a technical/computing context real time means something specific & web socket libraries aren't it.
Think "stuff that controls your car" or some components of a mars rover, or some medical devices. It needs to respond within hard time limits or Bad Things can happen.
Re:Show HN: Real-time apps without the hassle
by ceejayoz on Thursday March 27, 2014 @09:15AM
(#7480140)
Even Google doesn't care about this level of pedantry. Analytics has a "real-time" dashboard now. Like it or not, "gay" means "homosexual" as well as "happy", "hacker" means more than just people tinkering with electronics, etc. these days.
Re:Show HN: Real-time apps without the hassle
by kristiandupont on Thursday March 27, 2014 @10:24AM
(#7480549)
If they cared because there is a risk of misunderstanding, I could respect that. But nobody is going to confuse the two, ever, and coming with terminology is hard. Using "real time" in this case is, in my opinion, well chosen and much better than other recent terms like "responsive design".
Re:Show HN: Real-time apps without the hassle
by lgieron on Thursday March 27, 2014 @11:54AM
(#7481123)
I for one got confused - I assumed the link is about real-time systems and not a web app (I'd be interested in reading about the former but not the latter).
Re:Show HN: Real-time apps without the hassle
by ethanbond on Thursday March 27, 2014 @10:01AM
(#7480399)
You just said it. Most call themselves web devs to begin with. Not software engineers nor computer scientists.
You also alluded to a division which justifies this usage: this is a project by web devs for web devs. Web devs might use different language than software engineers or whatnot.
Re:Show HN: Real-time apps without the hassle
by RyanZAG on Thursday March 27, 2014 @10:21AM
(#7480523)
There are tons of meanings for "real time". Just because you like one of the definitions doesn't mean the other definitions don't exist. eg, http://en.wikipedia.org/wiki/Real-time_data
Re:Show HN: Real-time apps without the hassle
by mariusz79 on Thursday March 27, 2014 @08:34AM
(#7479930)
I wouldn't. And here is the problem JS folks are having.. Real Time does not mean "happening as fast as possible" but "deterministic". If I tell the process to turn something on and off every 1ms, the rt system will do everything in it's power to do it.
Re:Show HN: Real-time apps without the hassle
by Joeboy on Thursday March 27, 2014 @09:48AM
(#7480310)
> Real Time does not mean "happening as fast as possible"
That's not the meaning that's being used here. Here it means "events are shown at the time when they occur". Which is a very common meaning of the expression "real time".
Re:Show HN: Real-time apps without the hassle
by rubiquity on Thursday March 27, 2014 @10:01AM
(#7480396)
No, the meaning used here (and to the OP's defense every JavaScript/WebSockets library uses this definition) is a persistent connection where events are pushed instead of pulled.
Re:Show HN: Real-time apps without the hassle
by lgas on Thursday March 27, 2014 @11:37AM
(#7481019)
Well, that's not a meaningful distinction, because if I tell a javascript web app to turn something on and off every 1ms, the javascript web app will do everything in it's power to do it also. It just doesn't have much power to do it. The real distinction is that a RT system is designed through and through to have a lot of power to do it.
Re:Show HN: Real-time apps without the hassle
by tlarkworthy on Thursday March 27, 2014 @10:22AM
(#7480537)
embedded systems real time is impossible over the internet. So when talking about internet technology, you have to adjust the lexicon slightly. I have no problem with this.
Are you suggesting internet applications are banned from ever using the term real time until they replace the routing architecture?? Its such a good term that I don't think the embedded engineers should get to monopolize it.
Re:Show HN: Real-time apps without the hassle
by davidw on Thursday March 27, 2014 @09:55AM
(#7480345)
Bzzzt. Web "real time" isn't even soft real time, really, in the traditional sense.
It mostly just means "web sockets" so that you're not polling the web server to get updates. And honestly that's a pretty nice development in web development, and something to celebrate. Just that it's not the same thing that a lot of us think of when we think "real time software".
Just seconds before I was to send very clever real time message:
Such RealTime, Wow.
What did you want to show us? Where is the documented source, where is regression test, where even is the license file?
(Action Stations, Action Stations - Downvoting imminent. Prepare for impact)
Think "stuff that controls your car" or some components of a mars rover, or some medical devices. It needs to respond within hard time limits or Bad Things can happen.
along the lines of: responses are guaranteed within a certain time
You also alluded to a division which justifies this usage: this is a project by web devs for web devs. Web devs might use different language than software engineers or whatnot.
Meteor.js isn't a meteor, says the cosmologist.
Edit: Although I admit that I very much associate the "rt" suffix with the "runs in deterministic time" kind of realtime.
http://en.wikipedia.org/wiki/Real-time for a list.
How would you implement "real" rt in JS?
That's not the meaning that's being used here. Here it means "events are shown at the time when they occur". Which is a very common meaning of the expression "real time".
Are you suggesting internet applications are banned from ever using the term real time until they replace the routing architecture?? Its such a good term that I don't think the embedded engineers should get to monopolize it.
It mostly just means "web sockets" so that you're not polling the web server to get updates. And honestly that's a pretty nice development in web development, and something to celebrate. Just that it's not the same thing that a lot of us think of when we think "real time software".