Sans Browser » Web

WaSP Adobe Task Force

enefekt — Tue, 11 Mar 2008 13:24:36 +0000

The Adobe Task Force will collaborate with Adobe on all of the companyâ€™s products that output code or content to the Web, and will continue to advocate compliance with Web Standards and accessibility guidelines by those who use Adobeâ€™s products to design and build Web sites and applications.

Blog post

Press Release

HTML 5 in 15 Years?

enefekt — Mon, 10 Dec 2007 12:25:08 +0000

Reading over the article on ALA previewing HTML 5, there is a lot of cool stuff. The video and audio tags, and the new structure elements are all great. That last part stung a little bit though:

Work on HTML 5 is rapidly progressing, yet it is still expected to continue for several years. Due to the requirement to produce test cases and achieve interoperable implementations, current estimates have work finishing in around ten to fifteen years.

Hold up. Now, I’m sure that “work finishing” and being able to use it in more than one browser have to be two completely different things.(Hopefully!) But thats a long time!

Just as a head check in case there are folks looking to develop advanced RIAs right now. The Flash Player get’s over 90% penetration after just about a year. That means, Flash Player 9, along with Flex and ActionScript 3 apps incorporating video and audio, have a runtime penetration rate of over 90% right now. And in at the most one year, over 90% of clients will have the capability to playback H.264 video. That includes Linux, Windows, and Mac.

Merging the Best of the Web And Desktop

enefekt — Fri, 20 Jul 2007 11:52:17 +0000

There sure is a lot of news surrounding this right now.

The Browser As A Peer, is Here

enefekt — Fri, 27 Apr 2007 22:28:37 +0000

Brent Simmons strikes again with a really insightful post on why the whole “desktop vs web” debate is already dead. He uses the term “hybrid apps”, which is similar to an Internet Desktop App, but a more general categorization.

In the browser or out of the browser? Make that decision on an “app-by-app basis”. Look at the requirements of the project/product. No need to make blanket decisions. But there is always the considerations of you and/or your teams skill-sets. I think this is where runtimes like Apollo and XULRunner shine.

Of course though, highlighting some of the values of living outside of the browser are appropriate:

None of my browsers can provide the user interface that Twitterrific provides

Anyone who wants to do everything in just one desktop app, the browser, canâ€”provided they donâ€™t mind giving up protected memory and all that modern goodness.

The HTML Output Assumption

enefekt — Wed, 18 Apr 2007 12:13:00 +0000

An excellent post here by Dave Thomas on PragDave, one of OG Pragmatic Programmers.

He really drives home the point of server-side applications needing to be client-independent, not assuming the client is a browser, and spitting out just HTML.

Favorite antagonistic quote:

Recently, folks have been trying to circumvent this simplicity by making browser-based applications more interactive using technologies such as Ajax. To my mind, this is just a stop-gap until we throw the browser away altogetherâ€”Ajax is just lipstick on a pig