So a little while ago I started a thread, and people chimed in with some good reasons / features these machines have which keep them relevant in this modern day and age. There will come a day though (for many people, this day has already come), when they are simply too old to be useful at all.
I have a desktop for all my heavy stuff (media, gaming etc.), but still use my 1.67 PB regularly for server management (SSH), audio production (Logic), casual gaming (Quake 3 etc.), minor photo editing (Aperture), development (Python), web surfing etc. etc.
For all of those tasks bar web surfing, it will never be obsolete. Pro audio is probably going to be using 24-bit 48kHz RAW for the foreseeable future - which the PB handles just fine. Every day there are bigger and better synthesizers etc., but the sheer number of producers still using G5s seems to suggest that it's perfectly feasible to make decent music with the tools we have already.
There are always going to be players for the old retro games (though I feel Quake 3 has been somewhat superseded by Quake Live) - thus, gaming will never make it obsolete.
It's debatable whether using a PPC for development work will be feasible in a few years' time; it really depends on what you are developing. Most of what I develop is either for embedded hardware targets, web applications, or command-line utilities. Regardless, the only intensive part of development is compilation, which can be done on a remote machine anyway.
While I don't do any editing, I use Aperture to manage my library and fix the colour levels on scanned negatives (I shoot a lot of film - such a hipster, I know). When working with images from my DSLR, my PB does struggle. I feel this is definitely an area where they really show their age due to the lack of RAM and CPU oomph when dealing with high-resolution RAW images.
So what does that leave? Well, web surfing, and the hardware itself. Thanks to the TFF and the like, we have a modern web browser which is able to handle HTML5. I'm no web designer, but I feel that many websites these days have a severe case of information overload. The other day my girlfriend was complaining that my PB was slow while browsing the Daily Mail (avoid!). Given the design, it's not at all surprising. On further inspection, there are 4.4 MB of resources on the homepage alone (see this for the breakdown). That is absolutely ridiculous. The thing that really grinds my gears is when you go to read an article, the sidebar lists every single article - meaning the thing you're reading takes up maybe a screen height or two, and then there's a massive white gap all the way to the bottom, with reels upon reels of articles on the right that I would have noticed anyway while methodically going through everything on the front page. CSS3 is also another sticking point. It's now possible to achieve a lot of things with pure CSS that would have previously only been possible using sliced up images. The toll some of these functions take on the CPU is quite large in some cases.
So finally, we have hardware. Well, most of us at least one of: USB 2.0, Firewire 800, Gigabit ethernet, b/g wireless. Given I've worked on some, I know shamefully little about wireless technologies. There's some pretty interesting stuff brewing, what with mesh networks etc., but for the end user, I think it's all pretty transparent. The wifi in Coffee shops etc. will probably be b/g compatible for the next few years, but I can see the introduction of new standards being a major issue. While USB 2.0 opens up the possibility for using adapters, the chipset has to be supported in the OS, which a new one won't be. Which means people will either have to learn to use Linux, or hope someone ports the inevitable Linux kernel module for the new chipset(s).
If I need to move any large files around, I transfer it over the network. But there are always going to be USB 2.0 flashdrives and external hard drives, I don't think we'll see any change here.
So to conclude, for my personal usecase, there are really only two things which will mean the demise of my PowerBook:
I look forward to hearing some other perspectives on this topic.
Cheers,
Mike
I have a desktop for all my heavy stuff (media, gaming etc.), but still use my 1.67 PB regularly for server management (SSH), audio production (Logic), casual gaming (Quake 3 etc.), minor photo editing (Aperture), development (Python), web surfing etc. etc.
For all of those tasks bar web surfing, it will never be obsolete. Pro audio is probably going to be using 24-bit 48kHz RAW for the foreseeable future - which the PB handles just fine. Every day there are bigger and better synthesizers etc., but the sheer number of producers still using G5s seems to suggest that it's perfectly feasible to make decent music with the tools we have already.
There are always going to be players for the old retro games (though I feel Quake 3 has been somewhat superseded by Quake Live) - thus, gaming will never make it obsolete.
It's debatable whether using a PPC for development work will be feasible in a few years' time; it really depends on what you are developing. Most of what I develop is either for embedded hardware targets, web applications, or command-line utilities. Regardless, the only intensive part of development is compilation, which can be done on a remote machine anyway.
While I don't do any editing, I use Aperture to manage my library and fix the colour levels on scanned negatives (I shoot a lot of film - such a hipster, I know). When working with images from my DSLR, my PB does struggle. I feel this is definitely an area where they really show their age due to the lack of RAM and CPU oomph when dealing with high-resolution RAW images.
So what does that leave? Well, web surfing, and the hardware itself. Thanks to the TFF and the like, we have a modern web browser which is able to handle HTML5. I'm no web designer, but I feel that many websites these days have a severe case of information overload. The other day my girlfriend was complaining that my PB was slow while browsing the Daily Mail (avoid!). Given the design, it's not at all surprising. On further inspection, there are 4.4 MB of resources on the homepage alone (see this for the breakdown). That is absolutely ridiculous. The thing that really grinds my gears is when you go to read an article, the sidebar lists every single article - meaning the thing you're reading takes up maybe a screen height or two, and then there's a massive white gap all the way to the bottom, with reels upon reels of articles on the right that I would have noticed anyway while methodically going through everything on the front page. CSS3 is also another sticking point. It's now possible to achieve a lot of things with pure CSS that would have previously only been possible using sliced up images. The toll some of these functions take on the CPU is quite large in some cases.
So finally, we have hardware. Well, most of us at least one of: USB 2.0, Firewire 800, Gigabit ethernet, b/g wireless. Given I've worked on some, I know shamefully little about wireless technologies. There's some pretty interesting stuff brewing, what with mesh networks etc., but for the end user, I think it's all pretty transparent. The wifi in Coffee shops etc. will probably be b/g compatible for the next few years, but I can see the introduction of new standards being a major issue. While USB 2.0 opens up the possibility for using adapters, the chipset has to be supported in the OS, which a new one won't be. Which means people will either have to learn to use Linux, or hope someone ports the inevitable Linux kernel module for the new chipset(s).
If I need to move any large files around, I transfer it over the network. But there are always going to be USB 2.0 flashdrives and external hard drives, I don't think we'll see any change here.
So to conclude, for my personal usecase, there are really only two things which will mean the demise of my PowerBook:
- Continuation in poorly designed, resource-heavy websites
- Migration to newer, unsuppoted wireless standards
I look forward to hearing some other perspectives on this topic.
Cheers,
Mike
Last edited: