02-19 Adobe: get with the program
Your own software programs, that is. Between the Photoshop CS3 Beta, which doesn't seem to have any kind of crash logger (weird for a public beta, I'd think) and the craptacular performance of the non-native CS2 apps, I'm going crazy here. Today Illustrator's Pathfinder tool stopped working. Maybe I shouldn't say "stopped working," I should say "instantly crashes the program which is not the expected behavior." Design folks, have you ever used Illustrator while trying to avoid clicking on the pathfinder tool?
I guess it's time to get Matt to teach me Fireworks until Adobe gets their act together. It's times like this you realize the value of competition, and start to notice the difference between a de facto standard and a monopolizing dominator. When the standard you elected for quality's sake becomes an oppressive dictator, maybe it's time for a revolution.
And by the way... let me be the thousandth person to say: the new icons suck.
I guess it's time to get Matt to teach me Fireworks until Adobe gets their act together. It's times like this you realize the value of competition, and start to notice the difference between a de facto standard and a monopolizing dominator. When the standard you elected for quality's sake becomes an oppressive dictator, maybe it's time for a revolution.
And by the way... let me be the thousandth person to say: the new icons suck.
Read comments on your right →
There's a reason I'm still on the PPC hardware, still running software (like Photoshop 5.5 and Illustrator 9) in Classic - it actually works. And more importantly, it's actually stable. I've found it's worth putting up with boatloads of suck in terms of open/save dialogues, memory address limits, swap speed, hardware, etceteras - it's worth it for the simple fact that I don't have to worry about, say, font display working properly on one machine but not another... or some wit of a programmer deciding add/remove point needed to be weened off of the meta keys. #