File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Basics of Mac OS

 
Hussein Baghdadi
clojure forum advocate
Bartender
Posts: 3479
Clojure Mac Objective C
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all.
I want to familiarize myself with Apple world, so I have some basic questions please...
1. do Intel processors are faster than Macs ?
Mac G4 is about 1.60 GHZ , while Intel P4 is about 3 GHZ (or something like)
2. how Mac OSX uses the hard disk ?
I mean, Windows uses letters like C: D: E: .... and Linux uses / /user /root
3. In windows, we double clicked on My Computer icon to view the HD, then we can choose any partition to navigate to folders and files, can we do the same thing in Mac OS ?
4. We can use tools like : eclipse, IntelliJ, ant and others on Mac OS, but what about application servers like : JBoss, Tomcat, OC4J, Weblogic ..... ?
5. Can we do wireless Java developement on Mac OS ?
thanks for your patients...
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 64188
83
IntelliJ IDE Java jQuery Mac Mac OS X
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
1) Clockspeed is a poor indicator of actual performance. Read this.

2) OS X is a Unix operating system and uses the Unix filesystem notation.

3) Yes, the program is called Finder.

4) Yes, Tomcat and the like work without issue.

5) Can't think of any reason why not.
 
Loren Rosen
Ranch Hand
Posts: 156
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
To add a little bit:

An analogy I like to use regarding clockspeed is to think about automobiles. There's no single number that will really tell you how fast a car is. It depends not just on the engine size or max RPMs, but on the transmission, tires, brakes, etc. The issue with computers is pretty similar.

Unix filenames are just paths like /a/b/c. It's quite possible for parts of the path to live on different physical filesystems; the result is pretty transparent to an application. Usually paths to other filesystems look like /Volume/volumename/a/b/c, but so far as I know that's just a convention.

On wireless development, there is one potential issue: you probably need an emulator for the wireless device, for testing purposes, and unfortunately many of these are Windows-only.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic