130 karma · joined September 17, 2009
As for one of the more bizarre comments here: No minorities are signing up for clear to skip TSA, it doesn’t do that… it merely puts you at the front of the TSA line.
This just seems like a rebel-without-a-clue ranting about … something?
Seems like a ridiculous security risk.
I've never heard anyone but a despot (or vendor to despots) claim anything untoward about Citizen Lab, it sure seems like they're genuine "good" folks. They do great work, and they'll do better with support and access. The announcement makes it sound like Apple is willing to offer similar support to other good actors. I imagine Apple putting the word out will yield a few more.
It raises - again - the question of what we expect from big companies vs governments, and questions of sovereignty. Where's the line between supporting good work and cyber vigilantes (if it's not a thing today, it will be, and what will society's place be with respect to them)?
The lack of empathy or recognition of the terrible conditions warehouse workers have complained of (and have been well documented by journalists) is pretty striking.
The fact that the study doesn't talk about base rates for ethnicities is pretty "striking" (to use a word they breathlessly, and wrongly, use).
In earlier times, having a calvary was a strategic, forceful asset. It was, right up until mechanised warfare. Suddenly, there was no utility to a calvary.
It's impossible to talk about the human consequences of war without understanding how very different war was to a Roman soldier vs an American in Vietnam, or today's asymmetric battlefield.
These frameworks typically just allow you to wrap native methods with JavaScript... so you're not really writing to a single cross-platform code base. Morever, if you can build your app entirely in the HTML/JS/CSS side of things, you're golden... as soon as you start to bridge between the Native and JS layers, things get messy (and often very slow).
You're absolutely right about open platforms and protocols being about lots of people taking risks and building hugely valuable things. My point was that when the core OS is innovating like mad, you need to be close to those OS's to build the best apps... The innovation on the desktop slowed to a crawl years ago, and the majority of innovation has moved to the browser and web-app layer. In mobile, however, there's a LOT of innovation still happening right at the OS level w/ Android and iOS, and so all the frameworks that exist above the native SDK's are going to lag, and not take best advantage of the innovations being released at the OS layer.
The speed of mobile OS innovation will invariably slow (like it did on the desktop), but until then, philosophy about open platforms aside, iOS and Android show no signs of being displaced as the real mobile OS / platform drivers... and so, native's going to lead HTML5 / other "open" platforms for a while.
You're right that things like PhoneGap give access to native features. However, the Native-API-implementations in these frameworks are 1) typically significantly behind the native OS (release date) 2) tend to have less-than-feature-parity
So, often you're stuck writing your own native bridge, or tweaking the portability framework's version, which is time wasted (IMO) vs writing to the native framework. As an example, just try and write a PhoneGap app using Bluetooth: The Android implementation is incomplete, and the iOS version is non-existent.
Also, there are a tonne of performance issues you run into with the HTML/CSS/JS + Framework + Native solutions. As a thought experiment, consider how you'd build Instagram in one of these frameworks.
1) Image filters in HTML/CSS/JS land? Slow. 2) Thousands of images in a continuous virtual scrolling window in HTML land? Slow. 3) Fetching a binary blob (the image) from the OS, and throwing the resulting blob back-and-forth to web-land (for example, to use HTML5 offline storage) ... hellish slow.
Compare that to native... it's just one example of where the theory of HTML for UI and native for logic breaks down when you start to push the platform a little outside it's comfort zone.
Developer platforms: Nokia's owned QT for a while... what did they do? Nothing. Nokia had the WebKit WebRunTime years ago... what came of that? Nothing. Nokia actually enforced arcane third-party code signing/testing for apps on Symbian... who builds a developer platform and thinks that's a reasonable idea?
Ovi Store: Whereas RIM also does carrier-integrated billing for BlackBerry App World, RIM provides the developer with a consistent 70/30 split on app sales, and consistent payment intervals. With Nokia? Your split varies WILDLY from operator to operator, potentially being 35% of gross app price or lower on some operators, and you get paid depending on when those operators decide to remit payment. So, even with the most carrier relationships on earth, Nokia can't even do a decent job getting developers paid.
So, Nokia hasn't got an especially sexy UI w/ Meego, they've not got a great developer tools story (indeed with WRT and QT they have a history of screwing up even when they have a technology advantage), and they understand so little of the app developer needs that they can't even build a billing solution that competes with what RIM have built with App World.
Picking the guy who ran MSFT's business prodcuts division might help them compete with RIM in the enterprise, but it doesn't help them: - Sort out the Meego/Symbian mess, much less make it competitive with iOS/Xcode or Android
- Build the next-gen OS into something slick and sexy, instead of S60 reskinned time and time again
- Develop the kinds of tools, infrastructure and incentive Nokia needs to win developers.
All in all, I'm sure Stephen is a super smart guy, but he's not proven to have the domain expertise to solve Nokia's most pressing problems... which suggests that Nokia doesn't fully understand what their deepest problems are, meaning they really are finished.