What's wrong with clicking the error / warning icon in the navigation pane? It shows me my warning, I click the warning and it shows the appropriate file with the offending line highlighted in yellow. Click the warning again, and it will pulse the warning highlight in your source again, no line hunting necessary.

Is your complaint that Xcode just doesn't reposition your cursor? The highlight and caret where the warning occurs isn't enough?

And when Google drops support for h.264 I'll drop Chrome if I can't find a plugin. That's the reason that I switched to Chrome from Firefox too, though I'm not the same poster as the AC above.

I got tired of having my Linux boxes struggle to playback flash videos, and went looking for a browser with HTML5 video support using a codec that anyone gives a damn about (read as h.264). Chrome saved me from Flash on Linux and OS X and ended Mozilla's reign as my browser provider of choice going back to Phoenix days.

All Mozilla's stance has amounted to today is to force me back to using Flash again for everything beside Youtube video. Quite frankly, I'm interested in a pragmatic solution, not burning my legs to make a point about software patents or whatever Mozilla's justification for their obstinance is now.

That said, I agree with their stance on this WebP issue. There's no good reason to continue to pitch battles when the war's already been won by JPEG. It's just a shame that they can't see that h.264 has already won the battle for video and just hook into the OS-provided media frameworks. I'd like to use Firefox again.

I'd rather not have the option myself. Having Flash available is a disincentive to creating a better HTML5 experience suitable for mobile devices. With Flash available, mobile site developers can just create their sites and call it a day, regardless of how poor the experience is.

Not having the fallback means that you have no alternative but to create suitable code in order to reach mobile users. Since Flash for whatever reason already encourages lazy development, it would be better that the option didn't exist at all.

Jobs' obstinance, coupled with iOS marketshare will lead to a better mobile browsing experience for all of us, at least that's my take.

Limiting themselves to just a handful of devices IS their solution, along with abstracting away the minor hardware differences behind robust API calls.

Because, unlike electricity, bits aren't scarce. We can make more.

You need to get over yourself and realize that computing is bigger than just the desires of developers and geeks. What most of those who rail against walled gardens studiously avoid addressing is the simple fact that Apples succeeds by addressing the needs of people who are neglected by traditional computing. To wit:

My 60 yo mother doesn't want what "the iPhone should have been, and what Android still has a chance of being."

She wants to read a book and surf the web. She doesn't want to have to decide whether the Droid version of FBReader will run on her tablet, or wonder why the x86 version of her favourite PopCap game won't run on her ARM tablet either.

She's no fool, but good luck trying to convince her that she's better off in a situation where she needs to know what an ISA is or why it's important, or any of the other things happening in the largely uncontrolled Android market.

Most important, and more to the point: My mother will never research to find out that her program won't run in the background because Adobe hasn't gotten around to updating it's development tools to leverage the new iPhone APIs yet. All she knows is that the shit Apple sold her doesn't work.

Apple will continue to succeed as long as they prioritize the user experience, even if it's to the detriment of developers. There are a lot of non-technical users out there and they have money to spend.

You are confusing Flash lite, a limited subset of Flash with "Full Flash" in Adobe parlance, which is coming with 10.1. No shipping smartphone save the Nokia N900 ships with a full featured Flash runtime.

The Maemo plugin is a sluggish performer from what I've heard too. Adobe really needs to hit the Flash 10.1 for Android release out of the park, or risk validating all of Jobs' criticisms.