Welcome, Guest. Please login or register.

Author Topic: mac and pc sucks!!!!  (Read 36603 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Daedalus

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 893
    • Show all replies
    • http://www.robthenerd.com
Re: mac and pc sucks!!!!
« on: May 20, 2010, 01:23:01 PM »
Quote from: stefcep2;559707
What? Its not obvious to you?

No becacuse you're the only person thats ever opened more than on layer in photoshop. Layers, are one of the least efficeint ways to image process, but its The Industry Standard, so it must be good, right?

Eh, what? Really, have you ever had to do much work on any photographs in Photoshop? Non-destructive editing of images is vital when you're fine-tuning a photograph, and layers allows that. Yes, it's the industry standard with all that implies, but that doesn't exactly make it a bad thing either. It's industry standard to provide USB sockets on motherboards - is that a bad thing? Besides, many many years ago, TV Paint was the first application I ever used with layers in it. It was limited to 3 layers, but I found it was amazingly flexible, and quickly got frustrated with having to merge layers to free up another one, only to wish I hadn't because I want to edit something on one of the merged layers.

Quote

Professional magazine photographers have been opening up images in photoshop for more than 10 years with a fraction of the RAM.  I'm convinced that most shots are taken at higher resolutions than needed, just beascsue they can.  I have a digital publishing and design graphics magazine from 2000.  3 Megapixels cameras were the next big thing.  Now they'll shoot the same photo at 12 megapixels, and complain they don't have enough ram in Photoshop to open it .

It really depends on what you want the image for. High-quality prints need 300dpi at least, so all you have to do is multiply this up to what size you want and that's the amount of pixels you need. It's not rocket science, but why not deal in the highest number of pixels you can, in case you do end up wanting to print it poster sized? And why not have several layers so you can adjust your curves and go back later on if you feel after you've printed it that you've lost some detail, and readjust? It's unfortunate, but layers are just that - layers, including however many million pixels of information. It's a large amount of information which is incomparable to an encyclopaedia, and there's no way to get away from it. Pure, raw information.

Quote

In 1998, my school was using G3 imac with firewire to do all that shit-with about a tenth of the hardware specs.  You only think we've come a long way..


Have you tried watching a youtube video on a G3 Mac recently? Yes, I'm not defending the programmers of these things who are producing massively inefficient code, but some things in the modern world do actually need more CPU power and memory, like it or not.
Engineers do it with precision
--
http://www.robthenerd.com
 

Offline Daedalus

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 893
    • Show all replies
    • http://www.robthenerd.com
Re: mac and pc sucks!!!!
« Reply #1 on: May 21, 2010, 09:39:37 AM »
Quote from: stefcep2;559872
No, but I remember editing raw full screen PAL overscan video, which has 4 times the amount of pixels per frame than your average 320x200 youtube rubbish.  If I can't watch a youtube video with that same G3 then that just proves the point about how aerated the youtube/flash code is, not how incapable the hardware is.


Yes, I've edited full-screen video on a G3 to, and still routinely do it on my G4. My point is that mainstream things like Flash video are bloated massively, but they're also a staple of modern communications and need the raw horsepower to overcome the bloat. That's unfortunate but that's the way it is, and that's why my G3 and G4 Macs, while still suited to video editing, aren't suited to casual web browsing., whereas a Core 2 Duo Mac is.

Quote

For a minute there i thought you "just didn't get it", but seems thats only partially true.


Don't patronise me just because I don't fully agree with you. There's nothing you've said that I "didn't get" but some of what you say doesn't make sense. If you have x amount of information you want to process, of course you need >x memory to process it. No amount of efficient, assembly programming is going to change that.
Engineers do it with precision
--
http://www.robthenerd.com