Buying that dell would also cost him 299$... According to the calculations above, he could run his g5 on that money for 2 years straight and it wouldn't be more expensive (and that's without counting the electricity cost of running that new dell for the same time).
Those were my thoughts too. Esp. since the other 118 entries also don't seem to run osx. And I'm guessing most of them use a pc laptop. Which brings me to... power. How long before the g5 drains whatever batteries they put in there 1 minute? 2?
Don't let the java/objective-C comments scare you away, XCode also compiles C++ and you can use the Mac API from it.
And as said, since XCode is free with OSX, you should be all set right away. Just a (very) different IDE to learn, and an equally different API obviuously... Luckily it's starting to get more or less stable/fleshed out right now. A bit more API docs would do nicely though.
Like many others, I don't see what the problem is moving from unix (with its arcane editors;-) to windows.
To put that into perspective, you probably are comfortable with your unix environment because you learned to use it, and then to customize it.
You complain about syncing files in visual studio. Without a more specific problem, I can only say this: that is what visual studio is good at! Why? Because MS created a standard way for versioning systems and editors to communicate. A versioning system can plug itself into anything that uses this (it's called the SCC API). So get an SCC plugin for Visual studio for the versioning system you like. To show you just one, here is a CVS one: http://www.pushok.com/soft_cvs_proxy.php
If you need to do things that aren't present or easy in the SCC plugin, put up an 'external tool' in Visual studio, and assign a shortcut key. Use CVS' command line tool to pass the options you need.
Or let us know what problems you have exactly.
Also, what are you using on unix? Why aren't you using just that on Windows? Windows has a command prompt, and most things you'd need (like cvs) are controllable from it like you'd do on a unix machine, I think. And e.g. an emacs port shouldn't be hard to find, if that is your thing. What are you missing?
Look at the directory/Library/Frameworks on your mac. It's apples version of dll hell waiting to happen: shared frameworks (equivalent to dll's), with no way of knowing who uses them. MS came up with a system to fix this in windows 2000. Seems apple just can't learn from others' mistakes...
Maybe what he was noticing was the result of some settings/preferences/whatever being copied to his library, which many applications will do on the first run, but not when you install them.
Exactly: when you copy a bundle (i.e. a 'program' in a directory that looks like it's just a file) nothing happens, it's just copied. But when you start it, most of these things auto-configure the stuff they need, copying/creating things like preference files everywhere they want/need them, without your knowedge or control.
On the other hand, more and more OSX apps have actually gone to using an install program, including Apple's apps, which I find unfortunate. I like the whole drag-and-drop method of installation.
Strange, because the behaviour above feels to me like the good old times of windows 3.1 : sure we have an easy way to install our software. See, here it is. What, you want to get rid of it again? Euhm, well we have a ton files there and some there and a few here and one there, but that may be used by another progam too, and then there's a change we made in this file here etc etc...
I'm glad when someone takes the time to write an (un)installer!
Ok, so it's 9.82 TFlop/s (PC's) compared to 10.35 tflops (Mac's), so they only won by a small margin.
Price: 5.2M$ (Mac's) but I can't find any $ on the PC's... Seems someelse tried already as well:
http://www.macobserver.com/article/2003/11/17.1. sh tml
It says: "Let's see: Apple's system is faster, but it has fewer processors running at 2/3 the clock speed of the Dell system. We'd make a cost comparison too, but we couldn't find any information on how much NCSA paid for Tungsten, but even if the cost is comparable, the fact that an Apple system publicly outranks a comparable Dell system can't sit very well with Michael Dell."
Slashdot Mirror
Buying that dell would also cost him 299$... According to the calculations above, he could run his g5 on that money for 2 years straight and it wouldn't be more expensive (and that's without counting the electricity cost of running that new dell for the same time).
Sure, and 640k should be enough for everyone...
Those were my thoughts too. Esp. since the other 118 entries also don't seem to run osx. And I'm guessing most of them use a pc laptop. Which brings me to... power. How long before the g5 drains whatever batteries they put in there 1 minute? 2?
Don't let the java/objective-C comments scare you away, XCode also compiles C++ and you can use the Mac API from it.
And as said, since XCode is free with OSX, you should be all set right away. Just a (very) different IDE to learn, and an equally different API obviuously... Luckily it's starting to get more or less stable/fleshed out right now. A bit more API docs would do nicely though.
The original Release date they forgot to remove from the video? ;-)
Because their connectors have about a million pins?
Like many others, I don't see what the problem is moving from unix (with its arcane editors ;-) to windows.
To put that into perspective, you probably are comfortable with your unix environment because you learned to use it, and then to customize it.
You complain about syncing files in visual studio. Without a more specific problem, I can only say this: that is what visual studio is good at! Why? Because MS created a standard way for versioning systems and editors to communicate. A versioning system can plug itself into anything that uses this (it's called the SCC API). So get an SCC plugin for Visual studio for the versioning system you like. To show you just one, here is a CVS one: http://www.pushok.com/soft_cvs_proxy.php
If you need to do things that aren't present or easy in the SCC plugin, put up an 'external tool' in Visual studio, and assign a shortcut key. Use CVS' command line tool to pass the options you need.
Or let us know what problems you have exactly.
Also, what are you using on unix? Why aren't you using just that on Windows? Windows has a command prompt, and most things you'd need (like cvs) are controllable from it like you'd do on a unix machine, I think. And e.g. an emacs port shouldn't be hard to find, if that is your thing. What are you missing?
And you can turn much of the hiding off with things like OnyX or TinkerTool.
Look at the directory /Library/Frameworks on your mac. It's apples version of dll hell waiting to happen: shared frameworks (equivalent to dll's), with no way of knowing who uses them. MS came up with a system to fix this in windows 2000. Seems apple just can't learn from others' mistakes...
Maybe what he was noticing was the result of some settings/preferences/whatever being copied to his library, which many applications will do on the first run, but not when you install them.
Exactly: when you copy a bundle (i.e. a 'program' in a directory that looks like it's just a file) nothing happens, it's just copied. But when you start it, most of these things auto-configure the stuff they need, copying/creating things like preference files everywhere they want/need them, without your knowedge or control.
On the other hand, more and more OSX apps have actually gone to using an install program, including Apple's apps, which I find unfortunate. I like the whole drag-and-drop method of installation.
Strange, because the behaviour above feels to me like the good old times of windows 3.1 : sure we have an easy way to install our software. See, here it is. What, you want to get rid of it again? Euhm, well we have a ton files there and some there and a few here and one there, but that may be used by another progam too, and then there's a change we made in this file here etc etc... I'm glad when someone takes the time to write an (un)installer!
The goal is actually to make money FAST... and that means screwing the users if it'll make money faster. Even if it makes less in the long term.
No, you pay more because you got the computer, euhm console (not that there is much difference...) almost for free.
It's case-insensitive unix. Once you get over that... everything else should be easy! Yeah, right.
Ok, so it's 9.82 TFlop/s (PC's) compared to 10.35 tflops (Mac's), so they only won by a small margin.
. sh tml
Price: 5.2M$ (Mac's) but I can't find any $ on the PC's... Seems someelse tried already as well:
http://www.macobserver.com/article/2003/11/17.1
It says: "Let's see: Apple's system is faster, but it has fewer processors running at 2/3 the clock speed of the Dell system. We'd make a cost comparison too, but we couldn't find any information on how much NCSA paid for Tungsten, but even if the cost is comparable, the fact that an Apple system publicly outranks a comparable Dell system can't sit very well with Michael Dell."
Anyone better at digging up that price?