Now on a personal note, yes, many will remember my rants against CFVIDEO-type functionality (which reminds me ... publishing that lost episode of ColdFusion Weekly where I go a bit nuts on the idea might still be fun ...), but honestly I've warmed to the idea, especially on the presentation end of things. Being able to easily (and I mean easily) create video playlists is, I now have to admit, very cool, and moreover it's right up CFML's alley.
The CFVIDEOPLAYER functionality uses FlowPlayer, which is a really slick open source (GPLv3) video player. It has modular plugins, supports streaming, is imminently scriptable, and has a published API for extending the player. This bodes well for adding even more functionality to this feature in the future.
This is what I love about open source projects. Right when a feature is implemented we can put it in your hands, and we can be completely open about where we're going with things. And you can help us by downloading the latest build, trying out the new features, and giving us your feedback.
I think one of the areas CF (whether open or adobe) can move forward is the inclusion of features such as this (and e.g pdf ,image processing, forms) that web developers use commonly with minimal fuss. Looking at php 6, they're fiddling with improving some of the o-o implementation, but there's nothing new that's inspirational or really has an eye on the contemporary web in 2009.
Thanks Mike--there are people on both sides of this issue of course, which is one of the interesting things to me about being involved with OpenBD. On the one hand you have people saying (and I was one of them!) that an "application server" shouldn't do these sorts of things, and on the other, there's the sheer productivity and ease of use advantages of including features like this.
I think since I've started looking at OpenBD (and Railo, and ColdFusion) more as a development framework and set of powerful custom tags (oversimplification, but bear with me ...) instead of an application server in the true sense of the word, things like CFVIDEOPLAYER and some of the other "front-end" tags start to make a lot more sense.
I completely agree with your comment about PHP as well. While we do have to keep looking at and implementing improvements in the underlying language aspects, I think those have to be balanced with how web developers actually *use* these tools. And that's what tipped me on CFVIDEOPLAYER. It's a really handy tag that makes sticking video in a web page dead simple, so if it doesn't add tons of bloat to the engine or compromise other features, why shouldn't it be in there?