zubairov

Hi,

Nice one. What about using other data sources? What geo-coding is used in this sample?

Right. With HN in our samples users need to do an additional hop over to the main website. I think next time we could compare it on the other HN link.

Hi Andreas,

We don't have yet any data about this. We are in private beta phase so we just got started. We track our visitors/users very carefully, so by the time goes by we will definitely see some numbers that we can share with HN and Betalist communities.

Great idea! We also thought about this one. As we will re-sell cloud APIs it will be definitely a good feature to protect our users from slashdot effects.

Yes, that's definitely a problem. For our use-case where we want to follow SW engineering best practices like versioning, continuous integration, etc. we thought reuse of git as a repository and them to user will be a good thing.

Thnx for your feedback. Very good point! We will definitely improve our website in the nearest future.

Exactly. Primary motivation was to have a simple versioning for user data flow and Git repository management overhead was too much, however after we implemented it we realized that data portability is a by-product of that.

Agree. Also with our current implementation right now we might pose a bit too much load on Gists (which is actually only our fault), however it's only first step. We want to give our users their data at hand, I could imagine a potential independent 3-rd parties storing our data where other companies (Facebook) will use it on our behalf. Users private data will be more protected, and portable. So if I would like to switch (Facebook --> Google+, hypothetically) I would just revoke access from one site and give it to another.

Thnx for your comments Jason. Indeed any 3-rd party sign-in module lower down the conversion, however, on a given stage it's intentional. We would like to speak out to developers, and to those who are familiar with basic principles of open source software. So Github account is kind of filter for now.

I would question the viability of server-side web frameworks in the age of JavaScript MVC applications. The server-side component approach is dead (see JSF 2.0), so the only benefit of the web-framework in this sense could be only REST-based service creation, and backend for Web-sockets. In these areas one could find more focused frameworks like Sinatra or Express/Node.js.

That's a great news, and it will be very beneficial for both PhoneGap open source framework and ASF Foundation. Clear governance rules in ASF foundation will definitely be stimulative for other developers to participate.

JavaScript is the only programming language that runs on server, client and mobile. Java always wanted to be there, however never made it, and now (with Oracle) will also never make it in future. New name for Java is JOBOL.

Absolutely crazy idea. I lived there in Siberia, there not even a railways available. The reasonable-price logistics is only possible 2 month a year. This idea is a political hype. Such kind of idiotic projects appear shortly before elections and pass away shortly after.

Reduce in start time does not automatically mean your IDE will work faster.

Is Orion a new e5? What happened with e4? What the rest of Eclipse Foundation and Eclipse Projects think about it?