News for hackers. Stuff that matters.
Re:Thoughts on Flash by Qz on Thursday April 29, 2010 @10:29AM (#1304496)
This is where he loses me:

"Though the operating system for the iPhone, iPod and iPad is proprietary, we strongly believe that all standards pertaining to the web should be open."

Adobe can just as easily say: "Though Flash products are proprietary, we strongly believe that standards pertaining to what software is allowed to run on your computer should be open."

It's doublespeak either way, and it's crazy to think that either of those two viewpoints is good for the industry.

edit: Also: "If developers need to rewrite their Flash websites, why not use modern technologies like HTML5, CSS and JavaScript?"

Flash can handle touch events just fine. Rewriting all that flash code in H/C/J is a monumental task compared to just updating a few flash events.

Basically, this is a lot of corporate spin and not a lot of sound arguments.

Re:Thoughts on Flash by cninja on Thursday April 29, 2010 @10:55AM (#1304628)
My head started to spin when trying to reconcile points 1 and 5.

Point 1 states Adobe Flash has proprietary features and the standardized open feature sets of HTML5, CSS, and JS should be used instead.

Point 5 states 3rd party layers limits development to the standardized features and leaves out the proprietary features that makes Apple unique.

Re:Thoughts on Flash by mbreese on Thursday April 29, 2010 @11:16AM (#1304704)
They are talking about two different scenarios that aren't really that related.

Point 1 is in reference to the lack of Flash within Safari.

Point 5 is in reference to banning applications originally written in Flash.

Re:Thoughts on Flash by smallblacksun on Thursday April 29, 2010 @01:40PM (#1305277)
Or, more cynically,

Point 1 is in reference to a non-Apple product

Point 5 is in reference to an Apple product

Re:Thoughts on Flash by Qz on Thursday April 29, 2010 @02:24PM (#1305430)
Exactly. Apple vs non-Apple (or more generally, things a company controls vs things a company doesn't control) is the only relevant point here. Everything else about open standards and performance woes is just spin.
Re:Thoughts on Flash by danudey on Thursday April 29, 2010 @11:23AM (#1304730)
Point 1 is talking about websites / web applications. Point 5 is talking about native apps. Two different domains entirely.

With point 1, if developers are going to make a website, and they ditch flash, their work would work everywhere well (iPhone/iPad/iPod, Android, WebOS, Symbian, and Blackberry OS 6, as well as on the desktop). They wouldn't be limited to the platforms Adobe decides to support (or decides to support well).

With point 2, if you're going to make a native app for the iPhone, make one for the iPhone. Don't make one with Flash, which may not get around to supporting things like GameCenter, or multitasking, or any of the other hundreds of things Apple adds in new releases.

Choosing Flash for either one makes a substandard experience compared to the other options available.

Re:Thoughts on Flash by cninja on Thursday April 29, 2010 @12:05PM (#1304915)
I do understand your point about using the right tool for the right job, however Apple is arguing both sides. Either cross platform standards are a good thing, or platform specific features are a good thing.

While web applications and native applications are different domains, they are not different enough to mean different reasoning can be used. An end user doesn't really care if something is built using HTML5, flash, or compiled natively. They just care that it looks cool and does cool things.

Re:Thoughts on Flash by pohl on Thursday April 29, 2010 @01:00PM (#1305098)
Either cross platform standards are a good thing, or platform specific features are a good thing.

This is the classic fallacy of exhaustive hypotheses of the 2nd order, a.k.a. "a false dichotomy" or "the fallacy of the excluded middle".

There is a third possibilty: that both are good, and that which is better depends upon the nature of the app one wants to create. This third missing case also happens to be the reality of the situation — there are tradeoffs, and one selects which is better according to the upsides that one desires versus the downsides one is willing to abide.

(Surely you're not claiming that there are no tradeoffs between the native API and web technologies! I can think of several, not the least of which is the limited rate at which innovation can be brought to the web API.)

Re:Thoughts on Flash by btilly on Thursday April 29, 2010 @01:44PM (#1305293)
Cross-platform standards are a good thing for Apple. Getting people to use Apple's platform specific features is a good thing for Apple. Apple does what is good for Apple. There is no contradiction.

Remember, this is not an essay about why everyone else should support Apple's actions. It is an essay about why Apple thinks its actions are good for it.

Re:Thoughts on Flash by jimbokun on Thursday April 29, 2010 @07:12PM (#1306458)
"Apple does what is good for Apple. There is no contradiction."

I don't even think Jobs tried to hide this very well. It's pretty clear he is arguing from the perspective of what is best for Apple, and clearly and coherently explaining why.

Re:Thoughts on Flash by elblanco on Thursday April 29, 2010 @03:55PM (#1305782)
> It is an essay about why Apple thinks its actions are good for it.

Hidden in that of course is the lack of concern for what's good for the consumer.

Re:Thoughts on Flash by roc on Thursday April 29, 2010 @03:31PM (#1305684)
Point 1 states that ubiquitous Flash co-opts the rate of advancement of the web. E.g. You can't effectively differentiate, compete and move everything forward by supporting, say, h264 because Flash is already everywhere.

Point 5 states that ubiquitous Flash co-opts the rate of advancement of the mobile platforms it runs on. E.g. you can't effectively differentiate your device by adding a new sensor, API or capability, because Flash won't bother to support it until the hardware is standard.

It's the same basic argument: Flash becomes the platform, it's not a particularly good one and it's not a particularly good situation for developers.

Would you rather Apple compete with Google, RIM, Microsoft and HP/Palm for developers, or have them compete with interchangeable Flash-playing-boxes, leaving developers to Adobe's whims?

Re:Thoughts on Flash by digitallogic on Thursday April 29, 2010 @01:14PM (#1305163)
"If developers need to rewrite their Flash websites, why not use modern technologies like HTML5, CSS and JavaScript?"

If you have to make significant changes to the UI portion of your application, why not thrown the entire thing out and start from scratch with an extremely new (less mature) technology stack that you're probably complete unfamiliar with.

I believe Netscape got similar advice in the nineties.

Re:Thoughts on Flash by cabalamat on Thursday April 29, 2010 @12:59PM (#1305096)
> [Jobs:] "we strongly believe that all standards pertaining to the web should be open."

Consider Python. Is it a standard? Yes, because there's an open source reference implementation.

Does it pertain to the web? Yes it does, because http clients and servers can be, and often are, written in this language, and its standard library and 3rd-party open source libraries support http and other web protocols such as HTML.

So if you're so keen on stand ards Steve, why can't I write web software in Python for the iPhone and iPad? Why are you such a hypocrite?

On a wider note: Steve, do you want to spend the rest of your life selling sugar-coated digital handcuffs, or do you to change the world for the better?

Re:Thoughts on Flash by nwjsmith on Thursday April 29, 2010 @02:05PM (#1305381)
"why can't I write web software in Python for the iPhone and iPad?"

Ummm... you can. If you write 'web software' in Python, all an iPhone/iPad user needs in order to use it is the URL. Both devices have a best-in-class web browser that would be more than capable of running your web software well.

Also, check this out:

http://cl.ly/k0t

Apple is putting effort into make web apps first-class citizens on their devices.

Re:Thoughts on Flash by danudey on Thursday April 29, 2010 @01:43PM (#1305290)
Is python really a 'standard'? Python's had trouble lately with non-mainline implementations because the grammar keeps changing. There's no standards document laying out how the language should behave, in the sense of 'Jython is compatible with the Python language 2.5'; rather, third-party implementations duplicate features and functionality from CPython based off the PEP they're defined in.

Does it pertain to the web? It doesn't. Python isn't used 'on the web', it's used on the backend to generate web pages, as is C#, Erlang, and pretty much every other language ever. Are you suggesting that Apple should include a Python interpreter in WebKit? It sounds like that's what you're suggesting.

The simple answer would be 'because Python is not a language that is used in client-side scripting anywhere on the web'. No other browser supports it, and even if they did it wouldn't be widely used.

Your argument seems not only spurious but nonsensical. Python is used to send or receive documents over HTTP, so therefore I should be able to write a web app in Python to run on the iPhone? It doesn't make sense.

My home cable internet 'pertains to the web' too, and it uses documented standards like DOCSIS, so why doesn't my iPhone support DOCSIS? It's a ridiculous argument, as is yours.

Re:Thoughts on Flash by cabalamat on Thursday April 29, 2010 @02:04PM (#1305380)
> Is python really a 'standard'?

In an important sense I think it is. If I write a program in Python I can be reasonably sure it will run on someone else's system (obviously I have to take into account different Python versions, different underlying OS, etc). If I write a program in C++ or Scheme, what assurances of portability do I have if someone else's system is running a different implementation, with different libraries available, and different underlying behaviour in edge cases.

> rather, third-party implementations duplicate features and functionality from CPython based off the PEP they're defined in.

Yes; CPython is the standard. It's better if the standard is a program rather than a document, because you can run a program and find out what it does, but a document just sits there and does nothing (and may be hard to understand or ambiguous; the spec for Algol 68 comes to mind here).

> Python isn't used 'on the web', it's used on the backend to generate web pages

It is used as an http client as well as a server.

> Are you suggesting that Apple should include a Python interpreter in WebKit?

No, I'm suggesting that Apple should open up their platforms and allow people who have bought iPhones and iPads to run software of their own choosing on them; I'm sure someone would port Python fairly quickly.

> The simple answer would be 'because Python is not a language that is used in client-side scripting anywhere on the web'.

That's factually inaccurate; I personally have written code in Python that acts as a web client. As have some of my friends.

> No other browser supports it, and even if they did it wouldn't be widely used.

You seem to be under the misapprehension that client-side web programming must involve running inside a graphical web browser. This is not the case. Ever heard of wget? Or scraping?

> Python is used to send or receive documents over HTTP, so therefore I should be able to write a web app in Python to run on the iPhone? It doesn't make sense.

Yes it does. For example, I might want to write a program to cache certain web pages so I can read them even if I'm in an area with poor wifi and 3G access. And I might want to write that program in Python.

Re:Thoughts on Flash by jarek on Thursday April 29, 2010 @01:43PM (#1305291)
The sad thing is Steve, along with many others, totally, entirely believes that selling sugar-coated digital handcuffs is changing the world for the better.
Re:Thoughts on Flash by cromulent on Thursday April 29, 2010 @03:45PM (#1305741)
So...are you saying that Steve Job's efforts have made the world worse, or no difference at all?
Re:Thoughts on Flash by prodigal_erik on Thursday April 29, 2010 @01:39PM (#1305272)
A reference implementation is a good test suite but a poor substitute for a standard. It's huge and you can't just sit down and read it, you have to simulate it in your head to really understand what it would allow or demand. (This is also an awful problem with the HTML5 spec.)
Re:Thoughts on Flash by cabalamat on Thursday April 29, 2010 @05:33PM (#1306142)
On the contrary, its a written standard that you "have to simulate in your head". If you have an implementation, you can simply run the code and see what it does!
Re:Thoughts on Flash by mattmillr on Friday April 30, 2010 @05:09PM (#1309419)
If Jobs had said "We strongly believe that you should be able to develop on the iPad and iPhone using all open standards pertaining to the web," you would have a point. Your logic is all twisty.

"We only want to support open standards" does not imply "we want to support all open standards."

Re:Thoughts on Flash by rimantas on Thursday April 29, 2010 @10:34AM (#1304530)
I guess by "standards pertaining to the web" Apple means HTML, Javascript (ECMAScript to be precise) and CSS. What do you mean by "standards pertaining to what software is allowed to run on your computer"?
Re:Thoughts on Flash by DrSprout on Thursday April 29, 2010 @10:48AM (#1304598)
Packaging systems and their associated programming languages / APIs. Like Android .apk files, Apple .dmg files, Microsoft's .msi. All open and usable by anyone who wants to build one (though some fees may apply.)
Re:Thoughts on Flash by Qz on Thursday April 29, 2010 @10:42AM (#1304570)
Less of an explicit standard and more the previous consensus that the company that sells you your computer shouldn't retain control over what kind of legitimate software you can run on it after it's in your possession, based on some self-aggrandizing notion that they know what's best for you better than you do.
Re:Thoughts on Flash by bobdole2695 on Thursday April 29, 2010 @11:40AM (#1304784)
Uh? Have you met users before?
Re:Thoughts on Flash by Qz on Thursday April 29, 2010 @02:19PM (#1305422)
That's exactly the mentality that keeps 'users' stupid.

Apple is basically saying: "users are stupid, let's protect them from thinking." Imagine if we said that about our kids: "Our kids don't know how to handle the real world. Let's protect them from having to deal with it." (never mind that most parents do in fact go through this phase).

The reality is that users are just kids who haven't learned how to use computers. Two factors make this hard: most computer software is generally poorly designed (speaking in terms of the number of poorly designed products vs the number of well-designed products), and most software is not designed to teach users how to use it.

Apple is busy buying fish for starving people. The company that teaches users how to fish is the company that will win big.

Re:Thoughts on Flash by rimantas on Thursday April 29, 2010 @05:10PM (#1306070)
That's not about keeping users stupid, it's about not making them worry about stuff they should not worry about. The user may be the world's best neurosurgeon, does that mean that they have to learn about filesystems?

  most computer software is generally poorly designed
You are right about this one. But the thing is that Apple does exactly that: offering well designed software. It's not about buying fish, it's about hiding unneeded complexity. How do you drive the car: press the gas and it goes, press the brakes and it stops. Turn the wheel to the right and it turns to the right. You need zero knowledge about what's going under the hood. Now take the iPad: tap an app and it launches, press the home button and it stops. Swipe to the right, swipe to the left…
Re:Thoughts on Flash by Qz on Thursday April 29, 2010 @07:55PM (#1306584)
"The user may be the world's best neurosurgeon, does that mean that they have to learn about filesystems?"

There's a bit of a divide as to what 'personal' computers are being used for. The original mainstream use was to create/edit files using programs. The modern use is to interact with other people via the internet. So no, the neurosurgeon doesn't have to learn about filesystems because filesystems are mostly becoming irrelevant.

I don't think software should be designed to educate people about the trappings of decades of computer cruft. I think software should be designed so that using the software teaches the user how to use the software. Apple's method (re: iPhone/iPad) seems to be to design software that doesn't invite learning, and at the additional cost of limiting functionality.

Re:Thoughts on Flash by GHFigs on Thursday April 29, 2010 @09:25PM (#1306811)
Apple's method (re: iPhone/iPad) seems to be to design software that doesn't invite learning

Could you clarify this, perhaps by comparison to something else? Everything in my experience strongly supports the notion that Apple's general approach leads to much greater levels of competency and independence than anything else out there right now.

Re:Thoughts on Flash by jarek on Thursday April 29, 2010 @07:09PM (#1306451)
Turn the wheel and it goes where you want it to. But if you want to go to Google Voice, you'll have to take a long detour few people know of. You see, the road to Google Voice hasn't been optimized for your comfort. Or Apple's profit.
Re:Thoughts on Flash by jarek on Friday April 30, 2010 @08:02PM (#1309800)
Downvotes noted. The truth, it burns.