Also: Chrome, Xcode, Skitch, Divvy and the basic CLI tools.
I don't know what my problem is, but I guess my need for new features keeps diminishing. Maybe in forty years I'll finally be able to use Plan 9.
Preview annotates things well enough that I never use Skitch, although Skitch is cool if you want to use the sharing features.
You might be missing out on Dropbox. I wouldn't want to go without it these days as I use more than one computer regularly and don't have to remember to commit 'WIP' on a branch before I head home, I just drop the mic and get the fuck out. YMMV.
Divvy is great. I use it w/ SizeUp every day and wouldn't want to go without them. I don't miss xmonad at all anymore.
Other than that I install 1Password, The Unarchiver, Growl, CrashPlan, Flux, TextMate, iTerm, and GitX and I am good to go.
I seem to shed tools as OS X improves as well, but I hope that nobody is using plan9 in 40 years! ;-)
I would probably use Dropbox if I didn't have a VM. A friend has been trying to get me to use one of their competitors for a while.
Plan 9 is great, just a bit too much ideology to actually get anything done. I hope it's still maintained in 40 years in case I do go that way. :)
"Maybe in forty years I'll finally be able to use Plan 9." - LOL!!
And then there are lots of "default writes" that I do on every new computer… :(
You just made me realize I don't even have a 'top 5' anymore, a basic linux installation contains everything that I need to get through my working day. Email, browser, vi, c-compiler.
> Without it, I can't login anywhere
Here is the problem with 1Password and other similar tools: if you are in a place where you don't have access to 1Password, you can't login at all (i.e. you are screwed). This is why I force myself to remember all my passwords even if they are complex and numerous.
1) I have internet access to get to dropbox.com.
2) I have my iPhone handy.
1Password syncs to both of these over the air. So, bare a catastrophe, I should be fine.
Also, if the app you want to block calls out during installation, it's too late.
One thing I have noticed is that support for MKV/VP8/WebM has always been pretty bad. It uses a LOT of CPU time and in general was really slow. When YouTube put me in the HTML 5 beta it was unbeknownst to me sending me WebM content because I had Perian installed and it was causing HUGE spikes in CPU usage and overall lag because it was trying to decode and render WebM, whereas h264 requires almost no CPU power on my older MBP.
I hope that the community as a whole picks up the project and helps it succeed, it would be fantastic to still have it around.
Why does it take so long for MKV to load?
QuickTime expects to know the location of every single frame in a movie in order to play it. This is easy with its native format, MOV/MP4, but more difficult for several others, including MKV. Perian has to read in the entire file in order for seeking and playback to work.
That's probably (part of) the reason MKV and WebM are slow for you (since WebM uses the MKV container format).
Afaik playback performance is not affected by this. Poor playback performance is mainly related to the lack of hardware acceleration (and codec optimizations) people take for granted since h.264 matured on OS X.
Are there any alternatives?
Given that Apple has seemed to feel, for the last few OS releases, that it's acceptable for "deprecate" and "break" to happen in the same step, I wouldn't get my hopes up.
Thank you for appropriately assigning the root cause. I would have never linked the two.
To the team, thanks for all your years of hard work and best of luck on future projects.
Perian just made open source codecs work with Quicktime's API. Quicktime X however demands much more that makes it impossible to do without rewriting all the codecs. Those same codecs are directly embedded in other players (like VLC) so it's not a big issue. Quicktime X is pushing towards hardware acceleration, better battery life (with a few tricks), and multicore processing that the old model just doesn't work with.
Right now when you run older codecs, Quicktime X actually runs a little host process in 32bit that actually does the decoding using a fork of the old Quicktime 7 code. Native codecs run in 64bit using multiple cores and hardware acceleration.
VLC's recent UI changes have been a step backward (specifically making it impossible to see the playlist and the video at the same time), but at least you can queue things up to play.
I love the VLC redesign though, and it arrived just in time, so I'm happy.
But as others have pointed out, there is indeed another major open source media player.
At what point did VLC start using the ffmpeg libraries?
If I'm not mistaken mplayer has used them since its inception.
A sad day.
Perian team, great job guys and thanks for the many years of awesomeness.