Monday, June 30, 2008

cherrypy 3.1 released today

w00t! Cherrypy 3.1 [1] was released [2] today. I'm quite excited about it. For starters, I actually contributed some code. Although it wasn't much I did help debug some socket issues on OS X, and I helped flesh out and finalize the engine plugin interface. Although, I really shouldn't concentrate on my contributions as they are very minor.

Apparently Cherrypy trunk gained support for the Google App Engine over the weekend and I'm very excited about that. Anyways, congrats to fumanchu and the rest of the team!

[1] -
[2] -
[3] -

Monday, June 9, 2008

Saved? I don't think so

According to CTV and TSN, they have saved Canada's Second National Anthem. As nostalgic as the song is for me, it really surprises me how nuts Canadians are going over this fact. Honestly, I had no idea that so many Canadians watched Hockey Night In Canada because of the music?

If they really want to save the song, they should release it under the Creative Commons.

[1] -
[2] -
[3] -

Monday, June 2, 2008

A new browser competitor

Aside from the face-palming-symptoms of dealing with XML [2] DSL's [1][3], I came to another conclusion recently.

Flex, is touted as "a highly productive, free open source framework for building and maintaining expressive web applications that deploy consistently on all major browsers, desktops, and operating systems." [4]

To me, that just reads: Flex, combined with the Flash Player is a browser within a browser. Proof:

  • MXML is equivalent to XHTML - it's a declarative layout language.

  • Flex MXML documents can have embedded actionscript. This is nearly identical to embedding Javascript inside of XHTML. Heck, these two languages have the same origins: ECMAScript

  • The Flex Libraries are well, equivalent to any of the multitude of Javascript Libraries JQUery UI, Dojo, YUI and eventheir own, competing, javascript library Spry.

  • Flex also has an equivalent to CSS that it calls ... well ... CSS even though it's not CSS.

Confused? So is everyone else.

The Flash player needed to run Flex comes as a binary blob provided by Adobe. Alternatively you can use the incomplete and differing FSF implementation of the flash plugin: gnash. Ergo, there are multiple, incompatible potential target environments for flex applications.

On the browser side we have the choice of a plethora of browsers, Safari, IE, Firefox, Opera, Flock just to name a few. The browser most like Flex, also comes as a binary blob for the web. Firefox, is available for all major platforms, and applications which target FF will deploy consistently on all major browsers, desktops and operating systems.

So, adobe re-invented the web, it's technologies and in turn re-created the same problems. They had a chance to improve upon it, to make something better. But didn't. *sigh*.

But more importantly there are many implications to this realization, one of which is the potential of opening up the flash specification, such that competing players can be created. I'm beginning to doubt that Adobe will ever do this. And it may be to their benefit. Having a plethora of competing, incompatible flash player implementations will turn flash development into the same nightmare that current web developers face with the competing browsers.

[1] - DSL -
[2] -
[3] -
[4] -
[5] -
[6] -
[7] -
[7] -
[7] -
[8] -
[9] -
[10] -
[11] -
[12] -
[13] -
[14] -
[15] -
[16] -
[17] -
[18] -
[19] -
[20] -
[21] -