Apart from having Doom dreams, which I'm sure we all had (yeah?), I remember going to a supermarket after a long session, and instead of turning to walk into an aisle, turning before the aisle, and strafing out into it. At that point, Doom had leaked into real life....
Chrome to Phone (send a link from your desk/laptop to your phone to view later) Snipe (search and locate tabs) Diigo bookmark (best alternative to Delicious after Delicious went downhill - save links to cloud with tags etc) Tabs Outliner (manage windows and tabs, recover sessions, hibernate windows and tabs - absolutely awesome!) AdBlock (of course)
Haha, but if you'd done it properly in OO, you would have a Toastable superclass that has a default toast() method that can be overridden for different types of toastable things if required. E.g. Bagel : public Toastable might use the default Toastable::toast(), but PopTart : public Toastable might have its own PopTart::toast() method. If you have a toastable object that there is not a specialised class for - fine, it's a Toastable and uses Toastable::toast(). In a trivial example like this, it might seem overkill, but scale up just a bit and it quickly becomes very useful.
Slashdot Mirror
Apart from having Doom dreams, which I'm sure we all had (yeah?), I remember going to a supermarket after a long session, and instead of turning to walk into an aisle, turning before the aisle, and strafing out into it. At that point, Doom had leaked into real life....
Anyone?
Chrome to Phone (send a link from your desk/laptop to your phone to view later)
Snipe (search and locate tabs)
Diigo bookmark (best alternative to Delicious after Delicious went downhill - save links to cloud with tags etc)
Tabs Outliner (manage windows and tabs, recover sessions, hibernate windows and tabs - absolutely awesome!)
AdBlock (of course)
Haha, but if you'd done it properly in OO, you would have a Toastable superclass that has a default toast() method that can be overridden for different types of toastable things if required. E.g. Bagel : public Toastable might use the default Toastable::toast(), but PopTart : public Toastable might have its own PopTart::toast() method. If you have a toastable object that there is not a specialised class for - fine, it's a Toastable and uses Toastable::toast(). In a trivial example like this, it might seem overkill, but scale up just a bit and it quickly becomes very useful.