Re: Gimp, Anyone?

[P. J. Alling]

I never had that problem, plenty of core memory, I learned to program 
assembler on the IBM 360/370, I've still got my "green card" and my 
"yellow card" somewhere.  My first commercial job was writing assembly 
for the Commador64 however.  God how I _don't_ miss those days.

Gonz wrote:


Adam Maas wrote:

P.J.


See my last post. I've used assembler, I've even hand-assembled.

-Adam


LOL. That reminds me of the days I used to load a primitive boot 
sequence into a PDP (DEC) by the switches in the front, so it could 
load the next phase of the boot loader through the paper tape reader.  
I knew the BINARY values of most of the instructions by heart.  Those 
were the days!  The machine had core memory also.  Not enough of it tho!

rg


P. J. Alling wrote:

Obviously you've never used assembler.  You guys are talking past 
each other, and unfortunately you don't have a clue about what 
Graywolf is talking about.  (I think he's being a bit pedantic but...).

Adam Maas wrote:

12 years, give or take. Including coding (I don't do it for a 
living, but I write C, C++, Python, Bash and Bourne Shell, some 
basic and some Objective-C).

You simply don't know of which you speak. The 5% is the API 
interface and a few other bits necessary for platform differences 
(CHanges in the VM code to handle x86's incredibly wonky memory 
architecture, etc). The 95% is what does the actual work, all the 
backend code for EVERYTHING PS does, the plugin architecture and 
even as much of the UI code as they can make common (there will 
always be some). PS maxes at 2GB memory allocation on both Windows 
and Mac, this is due to being a 32bit program and being designed 
for the common 2GB/2Gb split that Windows and Mac prefer (Linux 
often uses a 1GB/3GB split, but that's a kernel compile option and 
varies between system).

-Adam

Graywolf wrote:

Hum, how long you been working with computers? Every bit goes 
through that 5% of code and comes out different. The other 95% is 
the user interface.
Yep, in Unix (Mac x) and XP that means the API. Modern 
multiuser/multitasking OS do not properly allow direct access to 
the hardware. Nothing I said was incorrect to anyone who 
understands this stuff. What we are talking about is how the 
hardware reacts to the software. For example PS uses 2 gigabytes 
max ram in Windows (even if your system is maxed out with 16 or 32 
gigabytes, and whatever the kernel will allow it in Unix (that can 
be changed simply in Unix, but not I think in windows).

And specifically, I do not know exactly how much is common code 
between the two platforms. I do not even know what PS is coded in. 
The programming language can make more difference than the 
hardware does. I figured we were using educated guesses.

I get the feeling I am talking with school kids here (lots of 
facts, not much understanding).

graywolf
http://www.graywolfphoto.com
"Idiot Proof" <==> "Expert Proof"
-----------------------------------










--
When you're worried or in doubt, 
	Run in circles, (scream and shout).