101–110 of 152 posts
We've been down this road before with the HTML5 vs Flash iPad post that Lee Brimelow made. The title is wrong, this is not Adobe's official response this is from an Adobe evangelist.
It's clearly not their official PR response, but the author obviously speaks as a representative of Adobe.
Earlier quoted context omitted.
> Jobs wanted web apps. Developers balked. Web apps would have been cross-platform (at least with Android and webOS). Apple responded to developers and now they've seen their chance to lock users and developers to their system. Jobs didn't want web apps, he wanted no apps. Web apps would have been more than useful given the right js APIs. It wouldn't have done a thing for games, but there's a great deal of stuff you…
Go back and watch the first iPhone keynote. It was all about web apps.
Earlier quoted context omitted.
I clarified my comment -- there is a distinction between an official adobe blog, and a blog by an official representative of Adobe.
Be that as it may, I said nothing about the blog being Adobes official blog, only that I was surprised by license and freedom they give to their rep.
Earlier quoted context omitted.
It's also in Apple's interest to get people using Objective-C and their toolkit. It brings developers to the Mac by forcing them to buy one. I'm not convinced Apple is trying to force developers to buy Macs, and I'm far from convinced that such a strategy would actually work.
I bought a Mac Mini with my iPod touch solely so that I could potentially write applications for it. I never did get around to it - my girlfriend went farther than I did - and so it sits, gathering dust, under my desk. But if I had a toolkit that let me develop iPhone apps without having to buy a Mac Mini, then I'd be much more likely to develop an iPhone app. So take me as a data point: the existing practical restri…
So, there are a couple things here that jump to my mind. 1. Adobe isn't completely innocent. They're pretty close to a monopoly on their type of software and charge dearly for it (their Creative Suite costs as much as a MacBook Pro). They've done a lot to make sure there are no non-Adobe Flash players even when that's just hurting customers and not costing them money since they don't sell the player. They're not exac…
Earlier quoted context omitted.
Of course the question everyone is interested in is are you allowed to publicly comment on / criticize issues like Apple strategy, policies and technologies. So are you?
I've never experimented with that boundary. Publicly criticizing your employer is unwise and unprofessional no matter who you work for. I don't imagine there are many Fortune 500 companies where you would last very long doing that.
Edit: I just realized that you're not allowed to comment on it if there is one :)
Earlier quoted context omitted.
>1. Adobe isn't completely innocent. Who cares about a company being "innocent" ? What does that even mean ? >(their Creative Suite costs as much as a MacBook Pro) Do you have a serious study saying that Creative Suite is overpriced ? Because it doesn't look that way to me. And what does that even have to do with anything ? >I'm sure they don't want to deal with developers using up their support time over things that…
People have invested time and money in this platform, and yet Apple decides to change the terms of the game and screw them over completely. Investing in a platform does not guarantee you'll profit from your investment, nor does it oblige the provider to continue providing you the means to recoup your investment.
sheesh... while one half of Adobe's brain (the flash-obsessed Macromedia one) is still screaming and flinging mud, the other half already used some of the perfectly Apple-endorsed C/C++ code they've got lying around and build a useful iPad App: http://itunes.apple.com/us/app/adobe-ideas-1-0-for-ipad/id36... - It's not like they're all about Flash; although it's obviously this guy's job to make it look like it - hence…
Earlier quoted context omitted.
It's also in Apple's interest to get people using Objective-C and their toolkit. It brings developers to the Mac by forcing them to buy one. I'm not convinced Apple is trying to force developers to buy Macs, and I'm far from convinced that such a strategy would actually work.
I bought a Mac Mini with my iPod touch solely so that I could potentially write applications for it. I never did get around to it - my girlfriend went farther than I did - and so it sits, gathering dust, under my desk. But if I had a toolkit that let me develop iPhone apps without having to buy a Mac Mini, then I'd be much more likely to develop an iPhone app. So take me as a data point: the existing practical restri…
The App Store is 185k titles strong, most of them crap. Developers without a passion for the platform are exactly what they don't need any more of.