drakaan (688386) writes "If you ever used jumpcut, it's time to grab any edits you posted and save them to your home machine. Recently, Yahoo! sent out the following email message:
Dear Jumpcut user,
After careful consideration, we will be officially closing the Jumpcut.com site on June 15, 2009. This was a difficult decision to make, but it's part of the ongoing prioritization efforts at Yahoo!
We have released a software utility that allows you to download the movies you created on Jumpcut to your computer. As well, you can now download your original assets. Please visit the download page at http://www.jumpcut.com/myhome/?subnav=download to get started.
Once you download your movies, you may choose to upload them to another site such as Flickr, which allows video uploads for short videos (90 seconds or less). You can find out more here: http://flickr.com/explore/video
Thanks for being a part of Jumpcut.
The Jumpcut Team
Sad news...jumpcut was a lot of fun. On the other hand, they *finally* put together a way to easily download the videos...maybe if they'd done that a year ago, this would be a different article..."
...Let's say a year from now, Microsoft does a SCO. They claim that Mono contains code that was stolen from the.NET Framework reference source code. They point at their code, they point at the license, and sure enough, there's similar code. After all, both projects are implementing.NET; there will almost certainly be lines of code that looks alike...
Seriously. Like, "there's an emptiness and it gnaws at me" kind of missing it.
I know why PJ went off the grid, and I respect her concerns, but it still sucks. In the meantime, anyone who feels the same can pay a visit Here, where some folks that used to frequent Groklaw are trying to re-establish a community that cares enough about the same things to keep them visible and discussed.
...so, I was grumbling to myself about IE not supporting certain CSS3 capabilities (selectors, box-shadows, text-shadows, etc), when I decided to go ahead and write a letter on the IE8 blog site:
I'm a web app developer and long-time [x]html/css hacker, and I'm curious about the timeline for IE8 supporting at least *some* of the useful new stuff in the CSS3 spec.
find it immensely aggravating that I can easily do rounded corners, drop-shadows, custom checkboxes/radio buttons, and opacity in Firefox, Safari, etc (but not in IE) using nothing more than CSS3-compliant stylesheets.
I always keep graceful degradation in mind when coding, but that doesn't mean I *want* pages to be either ugly in IE or uneccesarily complicated and verbose just because of browser compatibility issues.
When will I be able to rely on IE supporting CSS3 fully? It would help a lot in terms of lowering bandwidth, and simplifying development while ensuring a cross-browser experience that doesn't leave IE users with a dumbed-down view of a web app.
Shortly thereafter, I got a note back from Eric Lawrence on the subject:
The final version of IE8 was completed in March; in general, it does not (and thus will not) support CSS 3.
Planning for the next version of IE has started, and we have a large number of requests for support of various CSS3 modules.
I'm fine with that, but it misses the crux of my question (namely "when will IE be doing the stuff that other browsers have been doing for a year or more with CSS3?"), so I asked another question:
Does that mean that the next version of IE will support *some* CSS modules when it ships, or that it will support the CSS3 spec in its entirety?
When will we see some blogging on the subject?
...and got a reply...
It's important to note that thus far, only 5 of the CSS3 modules have reached Candidate Recommendation stage: http://www.css3.info/modules/. Some modules are still in working draft stage, and it appears that at least one isn't even at Draft stage yet.
We will discuss our IE9 plans as they solidify. At this point, we're primarily listening to feedback from developers.
Thanks for identifying some of your top requests.
I get it. I do, really. I *know* that CSS3 is unfinished. What I *don't* get is why 8 years after the initial working draft, the spec isn't close to being finalized, and why the parts that are simple or relatively stable have not been implemented by all browser vendors.
I'm not sure what the primary issue is...politics, money, over-cautiousness...all I know is that the situation makes it harder than it needs to be for me to create simple things that just work in all browsers (a newspaper-style multi-column layout...a drop-shadow on a box or text...alternate images for checkboxes or radio buttons...text displayed at a 45-degree angle).
But hey, what do I know...I'm not coding browsers or part of the CSS working group.