We've been very well aware of it and safely worked around it at the time. It was also something we just disliked and so we changed it across our entire codebase when we decided to write our own library.
When we said "it turns out", we didn't mean that we had suddenly learned that after failure. It's just something we meant to note that we decided to fix.
Depending on your definition of legacy, your argument is either incorrect or invalid.
Case 0: Legacy means "unscalable".
Argument cannot be used to evaluate the scalability of client-server models.
Case 1: Legacy means "old or crufty".
Successfully scaled legacy client-server software includes SMTP, IRC, NTP, NNTP, HTTP, MySQL, Oracle, etc, and to some extent, IP itself. Not to mention in-house systems like credit-card processing.
Client-server architectures are immensely popular, perfectly capable of scaling to high volumes, and used widely because they are easy to reason about and secure.
Indeed, if you've spent any time working on distributed systems, you might realize that scaling fully connected or peer-to-peer systems tends be harder than client-server. Take a look, for example, at the horrifying complexity of distributed agreement protocols like Paxos.
I like PhoneGap, but I like Appcelerator better simply because it creates native apps vs most other cross-platform frameworks that do most of the UI rendering inside a browser component/container. They do this by compiling the framework code (i.e JavaScript) to Objective-C. And the apps created in Appcelerator can be as visually impressive as the ones written in native platform, this is because the framework gives you the ability to create native UI components. Checkout wunderlist, they have used the framework to build their iOS apps and Android app and its a really beautiful app.
They only support iOS and Android right now, that might not be a problem for some, but honestly iOS and Android are the only relevant platforms for now.
But for folks who think cross-platform does not work and creates low quality app should checkout Appcelerator. I think CNBC's latest app is also built using this framework.
You're a bit off here. Appcelerator doesn't actually compile ANY javascript to native code. They expose a device specific API via a proxy/bridge system they call Kroll. They have a bunch of ObjC code that they then front with their Kroll Proxy. They also have a small shim between their JS interpreter, and Kroll on the other side.
So in effect any app you run on Appcelerator is still bound to the characteristics of their chosen JS interpreter, AND the characteristics of their proxy, AND lastly the performance of their native API.
It does provide a relatively simple path, to getting relatively simple apps up and running with native widgets but not inherently native performance.
Disclaimer: I've only ever dug into the iOS source, I can't swear this is 100% valid on other platforms.
no ahem no..they are not compiling js to objective-C..they are exposing their objective-C via a javascript api..big difference! How big? Try debugging an app..
Nginx is a thing of beauty, definitely scores over Apache.
- ease of use
- simplified configuration, I dont need a 500pg manual to get a grasp of nginx
- speed, speed, speed
- what else do you want :)
...Whats surprising is that this went untested for so long.