Re: What Mac can beat this for the same or less?

On 2007-06-24 19:27:48 -0700, "PC Guy" <pcguy@xxxxxxxxxxx> said:


"michelle ronn" <completelyinvalid@xxxxxxxxx> wrote in message news:2007062418465550073-completelyinvalid@xxxxxxxxxxx
On 2007-06-24 10:34:14 -0700, PC Guy <pcguy@xxxxxxxxxxx> said:

HP Pavilion dv9260nr Notebook

Core 2 Duo @ 2.0GHz
2GB DDR2 RAM
200GB HD
HD-DVD/CD-R Lightscribe Drive
17" Screen
HD Video Tuner
1Gb Ethernet
Remote
Built in video camera
Vista Ultimate 64 (OS X won't see 64 bit support until Leopard)
$1,800.00

Again, troll bait, I expect better from you.

Troll bait? Is not the purpose of this forum to compare Macintosh computers to other computing platforms?

OS X supports 64 bit applications now. It does not support 64 bit GUI applications.

LOL! I was wondering who was going to be the first fool to draw this distinction. Hello McFly! Recall that the primary draw of OS X is its GUI, not its CLI. Anyway with Windows you don't have to worry about this. Even GUI apps are 64 bit.

I would argue that most of the folks in this forum do not know enough to draw this distinction. I have also seen in your previous posts that you seem to know enough about code to know that this is a crap arguement that you are making. In Windows you should worry about this, as a 64 bit user interface is wasting resources; most of the time.

It is not a case of GUI vs CLI. It is a case of user presentation code vs background working code, and the message passing interfaces between the two. This architecture is actually generally better for a variety of reasons, multi-tasking across cores being a large one.

I would also argue that any program outside of something extremely trivial is going to be written in a modular fashion. This means that if it is written by a half way experienced programmer, the GUI interface code is written seperately from the real working code, which makes this distinction a complete non issue. Yes, this is true even for a Windows application.



.

Relevant Pages

  • GUI v. CLI was Re: Starting Perl
    ... the GUI v. CLI Jihaud, a brief refresher course on history. ... Windows noticed that Apple's GUI approach was ... user interface types of problems. ... One True App with a Gagillion command line options. ...
    (perl.beginners)
  • Re: What Mac can beat this for the same or less?
    ... HD Video Tuner ... Anyway with Windows you don't have to worry about this. ... I would argue that most of the folks in this forum do not know enough to draw this distinction. ... This means that if it is written by a half way experienced programmer, the GUI interface code is written seperately from the real working code, which makes this distinction a complete non issue. ...
    (comp.sys.mac.advocacy)
  • Re: command line vs gui
    ... "FJ>> command lines over GUI, even when using Windows. ... "FJ>> best of both worlds with an interface using charts/fields of text? ...
    (comp.os.linux.misc)
  • Re: What Mac can beat this for the same or less?
    ... HD Video Tuner ... Anyway with Windows you don't have to worry about this. ... This means that if it is written by a half way experienced programmer, the GUI interface code is ... written seperately from the real working code, which makes this distinction a complete non issue. ...
    (comp.sys.mac.advocacy)
  • Re: What Mac can beat this for the same or less?
    ... HD Video Tuner ... Anyway with Windows you don't have to worry about this. ... I would argue that most of the folks in this forum do not know enough to draw this distinction. ... This means that if it is written by a half way experienced programmer, the GUI interface code is written seperately from the real working code, which makes this distinction a complete non issue. ...
    (comp.sys.mac.advocacy)