Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It's not Apple's job to make sure other's software works. They change the OS to how they want, then others fix their software to work with it. It's the same with Windows, so don't get your panties in a wad.

Could you be any more incorrect? One of the things people use to criticize Windows is that it uses TOO MUCH legacy code and is, in essence, TOO backward-compatible. That's the exact opposite of what you just said.
 
Could you be any more incorrect? One of the things people use to criticize Windows is that it uses TOO MUCH legacy code and is, in essence, TOO backward-compatible. That's the exact opposite of what you just said.


Wow, touched a sore spot, eh? hahahahaha. Ummm, no, not incorrect either. Besides, that wasn't the point of my first post.....can you read any worse? It's still not Apple's job to make their OS work with others third-party programs. It is the same, in that regard, to Widows. It's not Microsoft's job to do that either.

----------

It ****ing is! That's exactly where you are dead wrong!



That's apparently what Apple does - and is free to do so - but apparently you are not in the software engineering domain (well, you're just a fanboi, aren't you... what the **** do you know... it "just works for you"): otherwise you'd known about the importance of keeping the API and semantics thereof stable! Just as on Windows (which is sometimes even infamous for keeping backwards compatibility).

Ummmm, no. It's not their job to do that. That's your job as a developer. It's your software, not theirs.
 
It ****ing is! That's exactly where you are dead wrong!



That's apparently what Apple does - and is free to do so - but apparently you are not in the software engineering domain (well, you're just a fanboi, aren't you... what the **** do you know... it "just works for you"): otherwise you'd known about the importance of keeping the API and semantics thereof stable! Just as on Windows (which is sometimes even infamous for keeping backwards compatibility).

It is Apple's job to keep APIs that they have published as "stable", stable and compatible. They do this. Many developers however use APIs that aren't published as such. They do this knowing that they may change and that in such a case they will probably have to update their app.

Apple has both kinds of APIs: stable and non-stable (where by stable I don't mean they crash but they are subject to change.) This is why there are developer previews: so app developers can test their apps with new OS releases (major and minor) before the OS ships so they can ensure that they have a compatible version out on time if necessary. This is also why there is always at least two weeks between the developer release and the public release.

Also, some stable APIs do change in ways that, if you follow the recommended way to use them, don't impact you. But if you use them in a way that isn't quite the right way, that may impact your app.
 
Last edited:
That's apparently what Apple does - and is free to do so - but apparently you are not in the software engineering domain (well, you're just a fanboi, aren't you... what the **** do you know... it "just works for you"): otherwise you'd known about the importance of keeping the API and semantics thereof stable! Just as on Windows (which is sometimes even infamous for keeping backwards compatibility).

Well, Apple has a history of deprecating APIs. And I think its a good thing, because it keeps the API clean and lets it evolve. Its not like API gets deprecated from one day to the other one - it takes years and you are forewarned early enough so you can change your code.
 
[url=http://cdn.macrumors.com/im/macrumorsthreadlogodarkd.png]Image[/url]


Apple has seeded the eighth Developer Preview of OS X Mavericks to developers, nearly two weeks after the release of the seventh Developer Preview. Registered developers can receive the update via the Software Update tool in the Mac App Store.

OS X Mavericks, which is expected to be released this fall, includes multiple new features like a tabbed Finder, full screen dual monitor capabilities, Safari improvements, and a new Maps app.

Apple is reportedly targeting a late October launch for OS X Mavericks.

Update: As noted by 9to5Mac, Developer Preview 8 includes an updated version of iTunes 11.1 that adds an option to turn off song change notifications.

Article Link: Apple Releases OS X Mavericks Developer Preview 8


It also includes iTunes Radio and Internet Radio with the update from Preview 7 to Preview 8
 
So, in other words, NO, Mavericks does NOT support dual-pane and forces users to open multiple windows to do something that should be simpler. After all, OSX is supposed to just work. I've never understood why they make moving files more complex than it needs to be. Once you've used dual-pane in something like Xtrafinder, you NEVER EVER want to go back to the default finder.

Dual pane is easily mimiced. Drag a tab off the finder and let it go on the desktop and it creates a new finder window at that location. Its not quite teh same as a dual pane, but as I said, just stick with it if you like it. Forklift does a good job IMHO.

Files can be dragged and dropped on the tabs themselves too for copying between locations.
 
Happy to report that even after restart, this build fixes a nasty UI bug in Circus Ponies Notebook that I had been experiencing with previous builds.
 
Last edited:
How is it Microsoft's problem if Apple made incompatible changes in a minor release?
Apple breaks things right and left - and the fans always blame the third parties for Apple's screw-ups.
Because that are the responsibilities of third party developers. You do not expect the OS platform itself to adapt to all kinds of weird third party app behavior, do you?
I don't think is anybody's fault. Mavericks is just a beta software. Microsoft doesn't need to concentrate on this until Mavericks is finally released.
Actually thats why beta software exists in the first place, to give Microsoft the needed time to adapt its applications before Mavericks is released and avoid users from suffering incompatibilities. Now is the time for Microsoft to sort out problems.
 
Maybe 10.9 will fix the sleep problem they introduced in 10.8.5

What sleep problem. I've had ML on about 40 home and work computers bad have no issues with sleep, so I'm curious what has been going on for folks

----------

Does anyone know if Mavericks enables TRIM support for non-Apple SSDs?
Will we still have to rely on TRIM Enabler in the future? It's kind of a dumb, consumer-punishing decision by Apple...

Few consumers in the general market will have non Apple SSDs. So no, they probably aren't in a rush to add something that encourages the .1% to do something they would rather you didn't.
 
Safari 7 and WebGL : Hmm. While your browser seems to support WebGL, it is disabled or unavailable. If possible, please ensure that you are running the latest drivers for your video card.

Firefox 24 and Chrom 29 works fine.
 
Some of you with strange issues that don't seem to affect anyone else then watch them mysteriously go away is most likely due to getting your systems "purged" with the DP update. God only knows what 3rd party crap some of you people install/uninstall between updates. Not to mention the hacks and tweaks.
 
How it it Microsoft's problem if Apple made incompatible changes in a minor release?

Apple breaks things right and left - and the fans always blame the third parties for Apple's screw-ups.

I have yet to see evidence of Apple 'breaking things left and right'. One notable case: MPlayerX (which still crashes on Mavericks). I don't recall the specific details, but someone looked at the code and found out that its a latent bug in the window initialisation code - it was using size parameters before they were properly initialised. In such cases the values are often undefined per specification. Incidentally, it worked on previous versions of OS X, but on Mavericks the component initialisation order was changed and the value was zero, which results in division through zero. This is a very nice illustration of a bug in the application code, which does not get detected, because it uses some undefined convention/feature/anything which by coincidence happens to work. Bugs like these are NOT Apple's fault.

Or if you want a more close to life example - this is like complaining about illegal parking ticket by saying 'but I have parked here for years and never got a ticket!'. Well, it was illegal all the time, just nobody bothered to check it ;)
 
This tops the record for # of developer previews right? Other OSX versions have not had nearly as many developer previews...

Nope. 10.8 had nine releases and it looks like we'll be about the same this time around.

Actually we can't. The next one we get will be GM since they need around 3 weeks between GM and the release like Lion and ML.

They could release september 30 and october 7 and still have three weeks before public release by the end of October.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.