Another important factor is the size of the screen. For me, it better be HUGE. Code editing (and writing) is a lot more fun when you can see much of it. 24"-LCDs have become so much cheaper, it's worth a try.
Responsiveness is directly related to memory usage. A Browser just should not eat up a fourth (500MiB) of my memory. And think of those with lesser hardware, you insensitive clod!
I wonder how many PS users would put that as the first item on their list of "critical features"
Layer sets are just a way of organizing layers into folders, correct?
Let's assume some designer prepares a psd-layout of a website, containing four states of that website, each consisting of 50 layers and each state is grouped into a nice layer-set. Now you open that document in Gimp, and *bam!* all 200 layers are pulled out of that hierachy and shoved into just one level. Now, in order to switch between these states, you have to hide/show 100 layers (I didn't even manage to select more than one layer at a time). Nice training for your index finger;-)
(please correct me if Gimp is able of doing any of the things I complain about!)
Please don't misunderstand me. I am using Linux most of the time and I love it, but sadly I'm unable to do my work without having a Windows-/OS-X-Machine near me.
"reboot later" means for Windows: "I'll annoy you every now and then, showing a little ticking bomb-like timer. If you're not around, because you're code's compiling, you're up/downloading something, or this machine is a (game-)server etc. -- Tough luck, I'll destroy all your work. Have a nice day!";-)
Ubuntu updater often wants you to reboot the PC. So does Windows Update with Vista but quite rarely.
Yeah, but Vista/XP forces you to reboot (i.e. initiates the reboot by itself) while Ubuntu _just announces_ that you should reboot and then leaves you alone.
I for one get each web-layout I have to implement as a Photoshop.psd-file from our designers. Gimp is already pretty good in displaying.psds, but doesn't support criticals features like layer sets.
Guess you have a point (though I actually think that (basic) set theory should be taught as early as possible;-)). Still I am convinced that students in college/university can (should) by all means understand basic low-level concepts. I myself had a class about Assembly as well as a class about high-level languages in my first year at university; one helped understanding the other and vice versa, which was quite helpful.
No, I don't agree with that. Prior to showing your students the wonderful world of high level and interpreted languages, they should learn whats acutally going on, what exactly they are doing and what happens behind the scenes when they hit 'compile'.
Sadly, there are enormous amounts of money being made with these annoying, ugly, blinking Flash websites and layer-ads, (mainly) because of the enormous amount of stupidity of designers and their clients. Unfortunately, blinking ads and websites do work, and they attract way more users (i.e. possible customers) than well-designed and appropriately built sites.
If Flash would be erased, the industry would come up with just another technology to drive sophisticated users nuts. So the only way to deal with this is to gain control over the force of ad-blocking and Flash-blocking contraptions, and if you ever encounter some jerk giving a webapp "more 'boost', a bit of 'zoom' and a little extra 'swoosh'", tell him why everything he's doing is wrong and encourage him to make it better. I'm doing this all the time and I think I may have achieved some progress. There's a better web ahead, and I bet it even can include Flash;-)
Slashdot Mirror
Another important factor is the size of the screen. For me, it better be HUGE. Code editing (and writing) is a lot more fun when you can see much of it. 24"-LCDs have become so much cheaper, it's worth a try.
Responsiveness is directly related to memory usage. A Browser just should not eat up a fourth (500MiB) of my memory. And think of those with lesser hardware, you insensitive clod!
You have to be careful these days when posting things involving enumerations of random things and one cup.
I almost tried to imagine... oh nevermind.
I just hope the optical drive can be replaced with another harddrive in the good ol' ultrabay-fashion. 64gig just isn't enough.
Let's assume some designer prepares a psd-layout of a website, containing four states of that website, each consisting of 50 layers and each state is grouped into a nice layer-set. Now you open that document in Gimp, and *bam!* all 200 layers are pulled out of that hierachy and shoved into just one level. Now, in order to switch between these states, you have to hide/show 100 layers (I didn't even manage to select more than one layer at a time). Nice training for your index finger
(please correct me if Gimp is able of doing any of the things I complain about!)
Please don't misunderstand me. I am using Linux most of the time and I love it, but sadly I'm unable to do my work without having a Windows-/OS-X-Machine near me.
"reboot later" means for Windows: "I'll annoy you every now and then, showing a little ticking bomb-like timer. If you're not around, because you're code's compiling, you're up/downloading something, or this machine is a (game-)server etc. -- Tough luck, I'll destroy all your work. Have a nice day!" ;-)
Ubuntu updater often wants you to reboot the PC. So does Windows Update with Vista but quite rarely.
Yeah, but Vista/XP forces you to reboot (i.e. initiates the reboot by itself) while Ubuntu _just announces_ that you should reboot and then leaves you alone.
I for one get each web-layout I have to implement as a Photoshop .psd-file from our designers. Gimp is already pretty good in displaying .psds, but doesn't support criticals features like layer sets.
I don't really believe it. My 2.5"-Harddrive consumes about 3-4W, I presume SSDs consume at least 1-2W. Can that be a full hour?
Guess you have a point (though I actually think that (basic) set theory should be taught as early as possible ;-)). Still I am convinced that students in college/university can (should) by all means understand basic low-level concepts. I myself had a class about Assembly as well as a class about high-level languages in my first year at university; one helped understanding the other and vice versa, which was quite helpful.
No, I don't agree with that. Prior to showing your students the wonderful world of high level and interpreted languages, they should learn whats acutally going on, what exactly they are doing and what happens behind the scenes when they hit 'compile'.
Sadly, there are enormous amounts of money being made with these annoying, ugly, blinking Flash websites and layer-ads, (mainly) because of the enormous amount of stupidity of designers and their clients. Unfortunately, blinking ads and websites do work, and they attract way more users (i.e. possible customers) than well-designed and appropriately built sites.
;-)
If Flash would be erased, the industry would come up with just another technology to drive sophisticated users nuts. So the only way to deal with this is to gain control over the force of ad-blocking and Flash-blocking contraptions, and if you ever encounter some jerk giving a webapp "more 'boost', a bit of 'zoom' and a little extra 'swoosh'", tell him why everything he's doing is wrong and encourage him to make it better. I'm doing this all the time and I think I may have achieved some progress. There's a better web ahead, and I bet it even can include Flash
hmmm... dunno, even though such a game could only be better than "The Simpsons - Hit and Run", it's not likely to be good.