Apple to Unveil New Leopard OS in August 519
Max Fomitchev writes "Looks like Apple is going to reveal its new cool and fast Mac OS code-named 'Leopard' in the upcoming World Developer's Conference in August. Good news for Apple! And terrible news for Microsoft. If 'Leopard' is really what it claims to be, i.e. fast and efficient, in sharp contrast to slow and resource hungry Windows Vista, we certainly would see Apple's remarkable market share gain next year."
More Speculation (Score:5, Interesting)
Way back in the day, Apple code named their boxes by color. From the aforementioned article: So we can speculate that Leopard might not only be fast but also encourage a partitioned Windows installation using boot camp so that it can reference everything within Windows and run Windows apps flawlessly without having to reboot or (more importantly) reverse engineer Windows.
Again, this is just speculation, I've been expecting them to put 'red box' functionality in a release of OS X soon.
Comment removed (Score:5, Interesting)
who said vista was slow? (Score:3, Interesting)
Re:Huh? Wanna say that again? (Score:5, Interesting)
Well one could go with history and note the fact that EVERY new version of Windows has been a lot slower than the predecessor. Meanwhile every version of OS X has been faster than the predecessor.
If you look at the unit sales of Macs from Apple quarterly reports, you'll see that they is usually significantly larger growth YoY that in the overall PC market. That means growing market share.
Of confirm it by looking at sites browser stats. This one shows Mac userbase doubling in 3 years.
http://www.w3schools.com/browsers/browsers_stats.
I can see why you selected your username. But you'd do better if you didn't overreach yourself with your FUD.
Pretty Funny (Score:1, Interesting)
Apple's next Mac OS X, Leopard (Score:2, Interesting)
Re:Huh? Wanna say that again? (Score:3, Interesting)
You'd do well to follow your own advice. I've already posted this, but what the heck:
Q1 2001 [com.com] (roughly 5.4% worldwide) and Q1 2006 [appleinsider.com] (roughly 2.0% worldwide)
I Suspect... (Score:5, Interesting)
Re:More Speculation (Score:5, Interesting)
I have to post anonymously on this one...
But speaking to a well known Oh-Ess Ecks programmer, I asked him about the possibility of Wine noting that he would be the one to ask. He is very collegial with Microsoft and I've hung with him and one of M$'s top programmers as they have both bitched and moaned about the other's OSs (and the Microsoft guy actually made a few points I never thought about before that were on the money...I program Windows for a living but own a niche Mac support company that grew out of a mailing list I use to moderate...I can almost give up the Windows programming these days as my organization is starting to look like it needs centralized day to day leadership, but beyond that, I could care less what OS anyone else uses. I know how to use both and my Vaio is as much a part of me as my new Intelbook).
Getting to the point, talking to the guy and asking him about the possibility of using my Windows skills to port applications using WINE but with a translated front end on the Mac side. Pretty much, simply run the APIs of the apps I have created or have access to, and create new native front ends. Best of both worlds I thought (sorta like when I would create C++ backends and use VB to build the front end on the PC and Hypercard for the Mac -- I got pretty proficient at making certain DLLs could be recompiled as a XCMD simply by dropping it in the right compiler and letting the headers decide what to do with it).
His response was one of the most direct responses I've ever gotten about future plans without him saying anything. Claimed to have looked into WINE, had it running internally (this was a year back, when I was still planning on having to use an X86 emulator to do most of the work as I didn't think the Intel switchover was going to happen so quickly) and he said that while it was a good product, they weren't going to use 'compromised' APIs to do this. When asked if they had any plans to license or develop any of their own non-compromised APIs, he responded that there was no plans to license anything. It was a pretty strongly worded statement, especially when looking into the point by point claims and what was missing from my original query. And considering the last statement I received in this manner was positively prophetic looking back upon the email.
With Bootcamp and the new emphasis on Parallels and my knowledge of their staff, my best bet is that Apple is planning on leveraging Windows to their own needs, making it usable but a pain. Sort of like how their Bluetooth products refuse to work with the Windows side of the Intelbook and simple features that could have been added were ignored to ensure that you only got exactly what you needed to run Windows solidly in Bootcamp, but not with the trademark Apple Ease of Use.
Re:Apple's next Mac OS X, Leopard (Score:5, Interesting)
Carbon's fine, until you actually bother to learn Cocoa. The fact is, religion about this aside, Cocoa is just better. As in 10,000% more productive better. The fact that apps also tend to look better is not a reflection of Carbon per se, but it is a reflection of just how much work you have to do in Carbon to makes things come out right. I'd rather spend time on making the app functional rather than endlessly tweaking the widgets. I came from the Toolbox, then Carbon, and now Cocoa, so I know of what I speak.
However, I disagree that PowerPlant is the cause of a lot of problems, because in many ways PP was the Cocoa of its day, Mac-wise (ignoring the fact that Cocoa has existed in some form since 1987, just not on the Mac). Using a framework on top of Carbon is the only sensible way to program with Carbon - anything other than a small app is unmanageable in Carbon if you don't have a framework there. What may be a source of this perception is that between System 8.0 and 10.0, Apple changed a lot about the organisation of the Toolbox/Carbon and PP may have struggled to keep up with that. It was a tough period all round.
I'd like to see the Finder written in Cocoa, because it would likely be a lot more functional since getting functionality together in a Cocoa app just takes much less effort than the same functionality in Carbon. Given that Apple seems to want to throw a Finder together I'm sure it would be a lot more polished in the same timeframe if constructed in Cocoa.
Re:More Speculation (Score:3, Interesting)
Comment removed (Score:3, Interesting)
Re:Apple's next Mac OS X, Leopard (Score:3, Interesting)
Furthermore, I did not mean to malign Powerplant (it clearly replaced MacApp as the only framework to use, and hell, only way to really write an application pre OS X), but in IMHO it is indeed the source of all these Carbon perception problems because even Greg Dow himself realized that he could not retrofit a lot of OS X features (e.g. Services support, support for NIB views) into his framework. The result being that all those Carbonized PP apps (maybe 99% of all commercial apps at the time of the OS9 to OS X transition) lacking those features gave the illusion that Carbon was to blame. And this deficiency in Powerplant is why Greg started developing Powerplant X before Metrowerks fully imploded.
Re:More Speculation (Score:2, Interesting)
I've seriously considered subscribing because I want to support Slashdot. It might not be a purely practical reason in terms of cost and immediate personal gain, but I enjoy the site enough that I want to help them. If you've ever had to buy a server, you know it doesn't come cheap (don't forget electricity, rack space, bandwidth, cooling, management and maintenance). If you, and everyone else, just block the ads, how is Slashdot going to survive? In that case, you won't be able to discuss at all anymore!