My understanding is that on the Intel version of OSX it is running Sun's Java runtime. The PPC version had a port by Apple to PPC that reportedly did have bugs. Have you tried this program on Intel? It might also, of course, be a bug in one of the libraries as well.
I thought this happened to me. But it turned out that the Startup Disk control panel in Windows only worked once I booted at least once into OSX via the option key. I wonder if others had that happened. I was pretty scared because I, like an idiot, didn't back everything up. But now I have Age of Empires III goodness going when I get bored.
Ah. USCD Pascal. I learned to program on that running on an Apple ][+. I never tried it on an Apple///. (There actually is an Apple/// emulator out there - although I can't imagine why anyone would need it)
It was pretty interesting. I came back to Pascal like languages with the original Modula-2 on my Mac. Then Lightspeed C and Lightspeed Pascal came out. I stuck with Pascal, eventually learned C and the rest is history.
The problem is though that the current transition with Apple doesn't do this. The 68k -> PPC transition allowed plugins to be shared across. The PPC ->x86 doesn't, thus the headache for users of Photoshop, Xpress, or InDesign. The 68k->PPC and Sys9->OSX transitions allowed backwards compatibility. The PPC->x86 transition won't allow you to run Sys9 programs. Yes Sheepsaver might eventually do this, but right now it is hard to get running and it is still reportedly quite buggy.
So the current transition is not nearly as backwards compatible as previous shifts.
Admittedly, unlike most MS transitions, various System upgrades with the Mac tended to break more applications. For instance I had several programs that wouldn't run under classic. It wasn't that big a deal for me. Compare this to Windows. I definitely had quite a few programs that wouldn't work in Win2K that did in Win95. But I had more programs that broke during the move to Sys7 or the move to Sys8. I think MS is to be commended for focusing so much on backwards compatibility. But it definitely has had its costs.
Unless I'm mistaken it has nothing to do with a "C++ object model" which obviously would work fine under XCode. Rather it has to do with using the old CFM stuff which was depreciated and dropped quite a long time ago by Apple. XCode won't even build them and they aren't supported with native Intel code. So they need a new plug in model which will require all new plug-ins. A boon, I suppose, for some developers, but definitely a hassle for end users. And probably the greatest weakness and danger for Apple in the Intel transition. But something that's been discussed a lot since the WWDC last year. Of course having built plugins under Metrowerks I say "about time." Yuck...
While your largely single threaded apps only get a 25% increase, that second core means you can be doing something else quite well while that one app is running. I do this all the time with iMovie on my dual 800. It really does make the system feel more responsive. So while everyone is right, I think they discount the real world effect of dual processors or dual cores.
Interesting as I develop software that we port to lots of different environments. While XCode has a ways to go still, it's vastly improved the last year. Every time we had to run Codewarrior though it was like someone was pulling my nails out of my hands. And I'm hardly alone. Visual Studio is heads and shoulders about Codewarrior and even has a lot of features vastly superior to XCode.
Thats just the thing... the "flaws" he's referring to were very small. You should expect more from a 1.0 release...
I don't know - the distortion in the TIFF and the importing of Raw sound like more than a very small bug. The file management issues, while highly annoying, could be chalked up to a bug. Fundamental functionality is more than a bug.
So what was up with Datsun becoming Nissan.
I get the Lexus - Toyota line. Infinity is Nissan. And aren't Acura's Hondas? Then there is that weird Mazda - Ford connection.
I'm so hopelessly confused. . .
That's my understanding. Initially Caldera seemed a nice distro. I'm not a big Linux guy, but in the early days I liked it. However it didn't keep up, possibly due to Noorda's illness. It quickly got overtaken.
This makes a lot of sense. Get people using video podcasts before Apple gets into it. The interesting issue will be how Apple can police podcasts (or if they should) regarding use of copyrighted sources.
I say that because it is almost inevitable that many of the non-techie podcasts will be sports highlight shows competing with the evening news. Indeed that's almost the killer application. *Except* that obviously they have no right to use the feeds.
I don't know how (or even if) Apple is policing current podcasts. I know a lot of people are pretty careful about the legalities with music, whereas I've found some that I'm pretty sure are just violating laws left and right.
But mark my words, Apple will try to get news stations to put up highlights and the like. i.e. your locals station's sports highlights for college sports is bound to be there.
My big question is exactly what the licensing for podcasts of borrowed feeds is. For example ABC regularly uses CBS sports feeds and vice versa with big expensive agreements. How does that fit into podcasting?
To a point. Clearly had the patent case gone differently I bet Apple would have done the UI differently. I'd note one big patent UI precedence though - Adobe's patents for movable tabs that one sees in say Photoshop but never in non-Adobe products.
Slashdot Mirror
You can't write commercial software with VS Express whereas you can with XCode. So "free for playing around" isn't quite the same as free.
My understanding is that on the Intel version of OSX it is running Sun's Java runtime. The PPC version had a port by Apple to PPC that reportedly did have bugs. Have you tried this program on Intel? It might also, of course, be a bug in one of the libraries as well.
I'd second Michael Johnson's. But I'd pick Topa's as second as well. The first two choices in the article don't do it for me.
I thought this happened to me. But it turned out that the Startup Disk control panel in Windows only worked once I booted at least once into OSX via the option key. I wonder if others had that happened. I was pretty scared because I, like an idiot, didn't back everything up. But now I have Age of Empires III goodness going when I get bored.
Ah. USCD Pascal. I learned to program on that running on an Apple ][+. I never tried it on an Apple ///. (There actually is an Apple /// emulator out there - although I can't imagine why anyone would need it)
It was pretty interesting. I came back to Pascal like languages with the original Modula-2 on my Mac. Then Lightspeed C and Lightspeed Pascal came out. I stuck with Pascal, eventually learned C and the rest is history.
The website says it won't run XP. That's kind of a huge limitation.
The problem is though that the current transition with Apple doesn't do this. The 68k -> PPC transition allowed plugins to be shared across. The PPC ->x86 doesn't, thus the headache for users of Photoshop, Xpress, or InDesign. The 68k->PPC and Sys9->OSX transitions allowed backwards compatibility. The PPC->x86 transition won't allow you to run Sys9 programs. Yes Sheepsaver might eventually do this, but right now it is hard to get running and it is still reportedly quite buggy.
So the current transition is not nearly as backwards compatible as previous shifts.
Admittedly, unlike most MS transitions, various System upgrades with the Mac tended to break more applications. For instance I had several programs that wouldn't run under classic. It wasn't that big a deal for me. Compare this to Windows. I definitely had quite a few programs that wouldn't work in Win2K that did in Win95. But I had more programs that broke during the move to Sys7 or the move to Sys8. I think MS is to be commended for focusing so much on backwards compatibility. But it definitely has had its costs.
I think there are enough people who never use that feature but know there will be that one time they need it.
Why not just run your purchased songs through Hymn to remove the protection?
Most expensive? I got mine for less than $1000.
Unless I'm mistaken it has nothing to do with a "C++ object model" which obviously would work fine under XCode. Rather it has to do with using the old CFM stuff which was depreciated and dropped quite a long time ago by Apple. XCode won't even build them and they aren't supported with native Intel code. So they need a new plug in model which will require all new plug-ins. A boon, I suppose, for some developers, but definitely a hassle for end users. And probably the greatest weakness and danger for Apple in the Intel transition. But something that's been discussed a lot since the WWDC last year. Of course having built plugins under Metrowerks I say "about time." Yuck...
Before I got to Apple, I really had no idea how much Avid had alienated their customers. It'll be a business-school case study someday. ;-)
I think Quark made it there as the case study first...
Lectoids from Planet X across the 8th dimension.
Actually my favorite mice and keyboards are all Microsoft labeled. I think MS has done some great hardware.
While your largely single threaded apps only get a 25% increase, that second core means you can be doing something else quite well while that one app is running. I do this all the time with iMovie on my dual 800. It really does make the system feel more responsive. So while everyone is right, I think they discount the real world effect of dual processors or dual cores.
A day and a half? Only to a Linux user is that a breeze.
I thought the reason FW800 wasn't taking off were the bugs on both platforms that often kept it so it was slower than FW400.
It isn't clear what the resolution is. The big problem with iTMS is that their resolution sucks. I can't imagine paying for those videos.
There is some Cocoa glue for Python. I've not used it much since most of the stuff I write doesn't need much of a GUI. It seems to work fine.
Interesting as I develop software that we port to lots of different environments. While XCode has a ways to go still, it's vastly improved the last year. Every time we had to run Codewarrior though it was like someone was pulling my nails out of my hands. And I'm hardly alone. Visual Studio is heads and shoulders about Codewarrior and even has a lot of features vastly superior to XCode.
Thats just the thing... the "flaws" he's referring to were very small. You should expect more from a 1.0 release...
I don't know - the distortion in the TIFF and the importing of Raw sound like more than a very small bug. The file management issues, while highly annoying, could be chalked up to a bug. Fundamental functionality is more than a bug.
So what was up with Datsun becoming Nissan. I get the Lexus - Toyota line. Infinity is Nissan. And aren't Acura's Hondas? Then there is that weird Mazda - Ford connection. I'm so hopelessly confused. . .
That's my understanding. Initially Caldera seemed a nice distro. I'm not a big Linux guy, but in the early days I liked it. However it didn't keep up, possibly due to Noorda's illness. It quickly got overtaken.
This makes a lot of sense. Get people using video podcasts before Apple gets into it. The interesting issue will be how Apple can police podcasts (or if they should) regarding use of copyrighted sources. I say that because it is almost inevitable that many of the non-techie podcasts will be sports highlight shows competing with the evening news. Indeed that's almost the killer application. *Except* that obviously they have no right to use the feeds. I don't know how (or even if) Apple is policing current podcasts. I know a lot of people are pretty careful about the legalities with music, whereas I've found some that I'm pretty sure are just violating laws left and right. But mark my words, Apple will try to get news stations to put up highlights and the like. i.e. your locals station's sports highlights for college sports is bound to be there. My big question is exactly what the licensing for podcasts of borrowed feeds is. For example ABC regularly uses CBS sports feeds and vice versa with big expensive agreements. How does that fit into podcasting?
To a point. Clearly had the patent case gone differently I bet Apple would have done the UI differently. I'd note one big patent UI precedence though - Adobe's patents for movable tabs that one sees in say Photoshop but never in non-Adobe products.