Dang it Steve!
April 15, 2010 Boston
Somebody needs to pull that boy’s head out of his hiney ~
Programmers are all up in arms for damn good reason (and they sure are cute when they get mad) Apple’s new policy BITES and I’m more and more confused about how to do this darn multimedia blogging thing!
I can’t play my videos on my iphone, which means you can’t either, (and that’s how I created most of it so far) because they’re in flash, and they aren’t going to work on the ipad either. BUMMER!
If anyone has any advice or feedback about this Apple ~ Adobe issue, I would really appreciate it!
Sure wish Steve Jobs would just quit the pissing match and play nice in the name of creativity.
How many iphone/blackberry users are out there who really would like the see videos in the Loo, and are looking forward to lying in bed with a sleek & weightless, sexy new 3G ipad~ Mmmmmmmm, Count Me IN!
Does this mean I should ditch Flash? It works so well… And what are the alternatives?
HELP!
p.s. This kind of paragraph totally turns me on, even though I only have a vague idea what it means:
The Absurdity of Apple’s New iPhone Restrictions
C, C++, and Objective-C were all developed more than 20 years ago and all, on the iPhone, require explicit memory management — the most error-prone detail in software development. You know how you tell when an app for the iPhone was written in MonoTouch? It doesn’t leak memory.
You can play the semantic game of “Well, since a C program is not ‘originally written’ until it’s been compiled, if we use a higher-level language to generate C and compile that then we are within the letter of the clause.” But try getting that past your company’s lawyer when you’re trying to get the go-ahead for a business-critical application.
Apple may feel that they are in such a strong position in the market that they can dictate that outsiders use the same techniques to write software that are used internally at Apple. But that’s not how programming works: it is a continually evolving melange of abstractions, techniques, and tools. It has to be allowed to vary at the individual, team, and industry level if it is to progress. I’ve worked on C and C++ at the level of standards compliance suites, I’ve done my fair share of JavaScript, and I can stumble along in Objective C. But personally, when it comes to the iPhone, my language choice is C#: it’s significantly higher-level than C or C++, it’s a little more terse and cleaner than Objective C, it has certain language features that are undoubtedly ahead of Objective C (LINQ), and it provides a better type system. That is just one person’s opinion and Apple can certainly afford to ignore me, but if they think can ignore the last two decades of advancement in the programming marketplace, they’re over-confident.
