He also didn't know about name mangling, and left that part of his job for the future programmers to do manually (method names and args are explicitly named, so you end up with arg named calling methods like [obj method:arg1 count:count]).
A agreed on some of the things you mentioned, pointing out the lack of namespaces particularly, but this you got wrong. Method arguments are not named. In Objective-C the method arguments are placed within the method name, which is a rather unusual way but still fundamentally different from named arguments, note e.g. that the first argument would not be named in that case. In your example, the actual method name is "method:count:", colons included.
Ever wondered why the kernel is written in C (with lots of assembly spices), not C++?
It's interesting that you are talking about the kernel since there is quite a few of them, some of which are successfully written in C++. Haiku is a good example that is currently becoming more and more interesting. I'm not saying that C++ would always be a good choice, especially if you already have a large codebase written in a different language like C, but it could definitely work well if used properly from the beginning.
Instead of simply blaming governments and oil industries we have to think about our own desire to consume oil. Why don't we put more energy and effort into finding and using existing alternatives to oil? We, as consumers, have a responsibility in this situation as well.
So the problem is that the memory of the iPhone is mounted and that the data is exposed? I may not understand this exactly but hasn't the argument been for many years now that iPods couldn't be directly mounted like that?
That said, jetplanes do operate in dusty sandy places (e.g. Middle East). Are the airborne particles significantly different in concentration and behaviour in a jet engine?
Sand itself is not that much of a problem, but a sand storm is. As far as I know at least one air force (Israel) can fly through an ash cloud. They have a birotating brush in front of the engine that moves particles like sand and ash out and through slots, thus protecting the engine. The only problem is that it decreases the efficiency of the engine by a huge factor. It is hard to rebuild existing engines so it is not something other air forces can just put on or off.
I'd like to know more about this agreement between Apple and Sun. I did a bit of searching and couldn't find anything. Do you have more info? A link maybe?
Unfortunately I don't. Not long ago I had a chance to talk with some of the Java engineers at Sun. During their seminar I noticed that they were using portable Macs so I asked them later on why Sun doesn't provide Java on the Mac. The answer they gave me was that Sun would love to support Java on the Mac but that they are prohibited from doing that due to the license agreement I mentioned earlier.
I'm more inclined to let the company that specializes in that stuff deal with it - but then again, maybe it gave them much needed experience for their Rosetta technology
According to the Sun engineers I've talked to it all has to do with a really old license agreement between Apple and Sun that they can't change for now. Sun is forbidden to directly release Java for Mac OS X until the agreement expire or Apple decides to make a new agreement. The only practical solution they proposed was to use the BSD port of OpenJDK. You won't have the Aqua UI and I think you have to deal with X11, but you will have an overall better Java.
Slashdot Mirror
He also didn't know about name mangling, and left that part of his job for the future programmers to do manually (method names and args are explicitly named, so you end up with arg named calling methods like [obj method:arg1 count:count]).
A agreed on some of the things you mentioned, pointing out the lack of namespaces particularly, but this you got wrong. Method arguments are not named. In Objective-C the method arguments are placed within the method name, which is a rather unusual way but still fundamentally different from named arguments, note e.g. that the first argument would not be named in that case. In your example, the actual method name is "method:count:", colons included.
Ever wondered why the kernel is written in C (with lots of assembly spices), not C++?
It's interesting that you are talking about the kernel since there is quite a few of them, some of which are successfully written in C++. Haiku is a good example that is currently becoming more and more interesting. I'm not saying that C++ would always be a good choice, especially if you already have a large codebase written in a different language like C, but it could definitely work well if used properly from the beginning.
Instead of simply blaming governments and oil industries we have to think about our own desire to consume oil. Why don't we put more energy and effort into finding and using existing alternatives to oil? We, as consumers, have a responsibility in this situation as well.
So the problem is that the memory of the iPhone is mounted and that the data is exposed? I may not understand this exactly but hasn't the argument been for many years now that iPods couldn't be directly mounted like that?
On their web site under the link titled donations. http://www.piratpartiet.se/donate
That said, jetplanes do operate in dusty sandy places (e.g. Middle East). Are the airborne particles significantly different in concentration and behaviour in a jet engine?
Sand itself is not that much of a problem, but a sand storm is. As far as I know at least one air force (Israel) can fly through an ash cloud. They have a birotating brush in front of the engine that moves particles like sand and ash out and through slots, thus protecting the engine. The only problem is that it decreases the efficiency of the engine by a huge factor. It is hard to rebuild existing engines so it is not something other air forces can just put on or off.
I'd like to know more about this agreement between Apple and Sun. I did a bit of searching and couldn't find anything. Do you have more info? A link maybe?
Unfortunately I don't. Not long ago I had a chance to talk with some of the Java engineers at Sun. During their seminar I noticed that they were using portable Macs so I asked them later on why Sun doesn't provide Java on the Mac. The answer they gave me was that Sun would love to support Java on the Mac but that they are prohibited from doing that due to the license agreement I mentioned earlier.
I'm more inclined to let the company that specializes in that stuff deal with it - but then again, maybe it gave them much needed experience for their Rosetta technology
According to the Sun engineers I've talked to it all has to do with a really old license agreement between Apple and Sun that they can't change for now. Sun is forbidden to directly release Java for Mac OS X until the agreement expire or Apple decides to make a new agreement. The only practical solution they proposed was to use the BSD port of OpenJDK. You won't have the Aqua UI and I think you have to deal with X11, but you will have an overall better Java.