juliennakache

Don't know the standalone gem, I'll have to check that out. I'll be glad to get some feedback on apnmachine :)

Hey, you do know that Apple requires developers to maintain persistent connections to their servers, right?

Checkout https://github.com/jnak/apnmachine Feature list: - persistent connection to APN Servers (as Apple recommends) - real-time notifications (no regular polling a la Resque) - super easy to use in Ruby and any languages (as easy as enqueuing a serialized JSON hash in Redis) - persist and queue messages when server is down - horizontal scalability and out-of-the-box load-balancing - fast daemons

Love SocketStream too. I'll be exploring Meteor to see the differences :)

I agree. But still, for that much money, they could put up a youtube video of the experiment :)

Wow. This dude is 14 year old.

That's the reason I actually moved in NYC. For a French 20 something, it's a great city to live in, it's not too far from Europe and the tech scene is booming. My next stop will probably be Brazil. I've travelled over 45 countries and Brazil seems to have that unique combination of "human" perspective, a work culture and a growing tech ecosystem. You should give it a try :)

It sounds like a fake story to me... Like a story made up for entertaining readers. I mean it seriously... Just to much BS to be true :)

where do you wanna work?

I want:

- persistent connection to APN Servers (as Apple recommends)

- real-time notifications (no regular polling a la Resque)

- super easy to use in Ruby and in any languages (as easy as enqueuing a serialized JSON hash in Redis)

- persist and queue messages when server is down

- horizontal scalability and out-of-the-box load-balancing

- fast/scalable daemons.

Hope you like it!

Is there any way to share models with the client and the server ?

I'm not sure a pure MVC (or a Model2) is the best way to architect node web applications. The config part looks great, I'll read that more carefully tonight.

Sounds great =D I've never used fibers in Node, but I'm quite experienced with Fibers and EventMachine aka EM-Synchrony. How do Fibers affect 1.debugging & stack trace and 2. performance & garbage collection ? Thx

Let us install a set-top box at your place and you should be good to go ! :)

Then IMHO it's very unlikely to be "screamin" fast using the MRI

I'ven't looked at the code base, but I don't get how you're allowing true concurrency without any evented framework?

You could have manually take care of the most popular websites.

But it makes sense. Though, how do you deal with false positive ?

Interesting guys. I've been waiting for something similar for a long time now. Quick question though: how do you map all my information to the input fields in each form. Do you kind of "crowdsource" it the first time a user comes across a new form and manually fill it in?

The most interesting part to me is the "generator function", which basically allows for cooperative scheduling.

This would put an end to spaghetti callbacks when doing blocking I/O operations. Very similar to EM-Synchrony for EventMachine/Ruby and (I guess) Inline Callbacks in Twisted/Python.

This and the new module would be a blast for Node.JS !

if they can't keep up a demo website, there is no reason any developer should trust pioneer to invest their time in testing / using zypr...

I user Chrome 14 and updates take over 5 secs to be synced across different tabs. Some kind of a bug or the backend app polls the db regularly to push new messages ?

It was interesting to read both of you guys. I can see a lot of ego on both sides... But that's a good thing :)

No one is wrong or right. It just depends on what you believe users are doing. One thing is certain: users use "local search" techniques as opposed to "systematic" search. The salesman problem describes this: the algorithm operates using a single current node and moves only to neighbors of that node.

However, depending on the "local search" algorithm used, those may be greedy or not: - "Hill Climbing" is greedy. The algorithm is affected by local maxima, ridges and plateaux. - "Simulated annealing" is not greedy. It uses "gradient descent" and does not always pick the "best" neighbors.

I believe the heuristics used by the users: - are not very precise ("Well, it is better, right?") - may change over time ("Oh, look at this!") That's why, I think it is not a "greedy" algorithm with deterministic results, but it is NOT complete anyway (hence, the clear process).

I can't wait for you guys to kick my butt :) ps: I'm a business major...

Totally agree with "it's not about being the first, it's about having it right". But that's why I'm not so sure about "building a working prototype from day one". In Spotify's case, they launched when they already had developed a mac and a pc client. To "have it right", you sometimes need to spend a fair amount of time before launch. Look at Instagram... Their iphone app was pretty much solid at launch: many lenses, clean and distinctive UI, great integration with social platforms, no bugs, no downtime... In Kik's case, they had an iphone, an android and a BB client at launch. This article by @gigaom wraps up my thougt on that. Anyway, this is a nice deck :)

Nice video of Ray Kurzweil talking about all that and Watson(IBM) playing Jeopardy!. http://www.usatoday.com/money/media/2011-02-09-kurzweil09_ST...

It's just a great summary of the concerns I'm living with on a day-to-day basis. Everything is there for non-geek to understand the big picture. AI, Robotics, Singularity, Biotics will lead us to the biggest disruption of the mankind era. One subject that I like that is not talked about : the ability of those supermind to work together lightning fast to form an even more powerful machine or robot.