Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
If Apple's not going to support Classic or Rosetta then they should release them into the public domain with full documentation.

I believe Rosetta, at least, involved (not inexpensively) licensed technology from a third party —*and Classic wouldn't work on Intel anyhow without something like Rosetta. What I would like to see, though, is for an enterprising third party (quite possibly an open source project, or, dare I say, Woz?) to persuade Apple to release all pre-OS X ROMs and Mac software under a clear, permissive* license for use by all current and future emulation projects.

* By which I mean no restrictions*intended to limit redistribution, commercial use, or derivative works. Public domain probably isn't feasible because it'd also preclude things like indemnification and various obligations attached to the code for the benefit of parties other than Apple.
 
Speaking as a heavy user of Alfred (+ PowerPack) KeyRemap4MacBook, and SizeUp, this strikes me as a very good thing, because, of the few dozen applications I use, these are the only ones I want to have this sort of functionality, and banning this sort of utility from the Mac App Store seems far preferable to a system (not unlike Java, say, or Android) where end users are expected to understand and authorize entitlements, which, among other things, would encourage "dumbing down" of the potential space of entitlements. Instead, let the MAS remain a place for "safe" sandboxed apps that I can be reasonably confident won't affect my system when they're not running, and let the Mac remain open to other software (aside from perfectly sensible "first use" warnings and measures like Gatekeeper).
 
Can't live without my QuickSilver. Glad I can get it without the App Store. Why can't there be an API to register hotkey callbacks or something?
 
This isn't a world-class security feature. I would prefer for Apple to fix the security holes in the operating system, than doing this.

*bingo*

One can never have too much security, but any hacker finding a way to breach this sandboxing will then be able to go after all of the other holes thanks to the OS maker's laziness and false belief that sandboxing makes for a cozy impenetrable workaround.
 
so stupid apple is reducing the functionality f the OS at a tie when we are all getting bored of IOS and want new cool functions and features... typical large corporate attitude..:rolleyes:

If you cannot handle sandboxing design into an application then you prefer inherently broken software.

----------

*bingo*

One can never have too much security, but any hacker finding a way to breach this sandboxing will then be able to go after all of the other holes thanks to the OS maker's laziness and false belief that sandboxing makes for a cozy impenetrable workaround.

http://developer.apple.com/library/...ignGuide/AboutAppSandbox/AboutAppSandbox.html

It's called separation of concerns.

Sandboxing the App Space and adhering to this sets a standard for all Apps.

Engineering resources then move to the Kernel and FileSystem access methods that Sandboxing cannot touch and refine the layers of security while maximizing performance, scalability, while tracking down bugs that get exposed from FreeBSD and other 3rd parties that Apple works within their Kernel and Filesystem levels.

Apple streamlines Foundation, CoreFoundation, AppKit, the WindowServer, Quartz Compositor and more and these sandboxed apps get even richer, more secure APIs to leverage.

Sorry, if you prefer to write around already highly refined APIs to exploit a performance hack that is exposed by a private API or of something similar, but don't be surprised when GNOME, KDE and Windows APIs all move to this model.

After all, Linux has sandboxing as well.
 
This is exactly why I haven't really invested in apps from the Mac App Store. Sure I've bought a couple from Apple. Even a couple games like Angry Birds. Grabbed some freebies like Twitter and Evernote. But beyond that? Not worth the risk at this point.

I love my iOS devices—they are extremely secure and easy to use. But I, like many other Mac users, make my living on my machine. I don't have time to screw around with all these limitations. I have money to make. I have clients with budgets and timelines to satisfy. That is why I will continue to invest outside the App Store for any mission critical applications. The moment Apple removes that capability, I won't hesitate to go back to Windows—and I hate Windows. Ask anyone I know “Who is the biggest Apple fan?” and they will say me. So I'm not making these comments lightly.

My hope is that Apple will find a new way to securely implement these features in a future OS. I'm optimistic, but cautious. Apple has yet to prove to me that they are taking the Mac App Store seriously. We should be getting more features and capabilities over time—not less.
 
Apple has yet to prove to me that they are taking the Mac App Store seriously.

I'm waiting for Apple to take the Mac seriously. I am happy they are making money hand over fist with the iDevices and I hope they continue doing so. I just want we few and proud Mac users to get some love and not continuing signs of what seems like the Mac's (and general computing in general) inevitable decline.
 
I think I understand this in theory, but do any posters have an actual real-world example of a program they use with this?

Apps that won't work the same (or at all) after the Sandboxing update:
Alfred
Fantastical
Moom
Sparrow
Cloud
Fontcase
DaisyDisk
Growl (Not sure about this)

Basically, anything that has a global shortcut, interacts with the GUI, needs to interact with another application, or needs some kind of system function to work.

Pretty much any application that is capable of doing more than opening, editing, and saving a file will be broken by the sandboxing requirement. As a result the only apps that will be in the MAS will be "dumb" apps that don't do much.
 
If Apple's not going to support Classic or Rosetta then they should release them into the public domain with full documentation.

They do :

http://support.apple.com/kb/TA48312?viewlocale=en_US#system

You can download System 7.5.3 Rev 2. They released all software prior to 1998.

And frankly, you're asking for bad software design. Legacy cruft and bit rot are bad for progress. There's a big difference between what you're asking (extended support) and what we're discussing (the balance between functionality and security).

Nothing prevents you from running older software on older hardware if you absolutely must use outdated applications.
 
Thinking more about this: I find it hard to believe Apple are going to disable global Hot Keys. Many applications use them. It shouldn't be overly complex for Apple to implement a secure hotkey API.

I'll believe global Hot Keys have been disabled when I see it.
 
If Apple's not going to support Classic or Rosetta then they should release them into the public domain with full documentation. Time for a class action lawsuit and a change of law regarding this issue.

IBM owns Rosetta. Not Apple. So good luck in the courts trying to sue Apple for not stealing and giving away somebody else's software. There's probably other code in Classic that is not Apple's, but licensed with limitations as well.

Or were you planning on suing IBM?
 
Hm... Macworld refutes this... And in response tuaw adds an editor's note saying they stand by the story but can't say why. The note also adds...
...all I can tell people is that either Apple is unsure of what hotkey functionality is in this case, or something has changed very recently in such a way as to negate what was said previously by Apple.

Clearly tuaw is confused since both options are absurd: I'm pretty sure "Apple" knows what a hotkey is and Apple hasn't contradicted itself because Apple hasn't made any statements about hotkey apps. By "Apple" I suppose tuaw means their source at Apple. Tuaw must find their source unimpeachable.

Could it be that their source is simply misinformed or otherwise lacks the ability to speak authoritatively (yet anonymously) for Apple?

Time will tell...
 
YEAH!!! EVIL STUPID APPLE.
How DARE they make the OS more secure!

Or do you think that they should simply carve out great big holes in the only security measure (Sandboxing) that is proven effective in fighting malware?

The 99% of us who want a secure system frankly don't give a rat's ass about mildly inconveniencing a few lazy users. Sorry for the devs, but times move on.

99% of the macuser are noobs? No, I don't think so, Tim.
 
so stupid apple is reducing the functionality f the OS at a tie when we are all getting bored of IOS and want new cool functions and features... typical large corporate attitude..:rolleyes:

mac app store isn't the only place for app.
i could see why they are after sandbox.
 
Headline: Apple is evil!!!! OMGWTFBBQ!!!! [Updated]

Content:

[Update]: It's not!
 
Automator is slow as molasses and impractical for setting up global hotkeys. I use Alfred (with PowerPack which you CANNOT get from the App Store) and it's lightening fast.

I just hope to God Apple never forces all 3rd party devs to use the Mac App Store or I will be forced to leave the Mac altogether. And I love my Macs. (Albeit a little less these days since upgrading to Lion.)

After using Mac OS 10.7 Lion, I believe that one should not use the term upgrading to Lion. That is unless you are changing from an OS older than CP/M or MS-DOS.

Lion is a step or 2 backwards. From what I hear Mountain Lion Mac OS 10.8 will be another step or 2 backwards. The only thing that may save the Mac is that since MicroSoft like to copy Apple, Windows 8 looks to me many steps backwards. They've done a good job of copying Apple's new poor OSes so the Mac OS should continue to lead all but many of the older Mac OSes & one or two of a Windows versions.
 
Forbidding hotkeys in apps??? Something very strange happens there! All modern applications on different OS have this features for DECADES! Security issue? Then your OS is buggy as *****, Apple!

-1 Apple
 
Stupid is true

IF Apple were to do this, it is very stupid - a lot of us use tools like Typinator and Keyboard Maestro to 'enhance' our OSX use and experience. If this would stop those tools operating, I'll be asking Apple to recompense me for the money I spent on them.

However, simpler is just not to use the App store and return to 'the good old days' of users making the decision on the suitability of an app themselves and just download from the authors site.

--
I need someone to protect me from all the measures they take in order to
protect me. -Banksy, street artist (b. 1974)
 
This isn't a world-class security feature. I would prefer for Apple to fix the security holes in the operating system, than doing this.

Right and their going to do it with Magic. That what they are doing but I guess its not good enough for many, so its time for you to move to something else.

----------

I'm not seeing this as a big deal. Power users don't really use the MAS anyway (we all are familiar with non-mas versions of apps having more features than the mas ones..) I see what Apple is trying to do, prevent dumb a$$es from messing up their own computers with malware and shitz. This doesn't affect anyone who knows what they are doing.

Productivity tools like these are for power users; and for them, everything is the same as pre-MAS days. Noobs use the MAS, everyone's happy.

The problem with this model of course is, who gets malware from the MAS anyway? As long as gatekeeper and the like are under user control, all this complaining is pointless IMHO.

Pointless for those who think they know better, but for most they will turn on the security and move on with their lives without worrying about every malware in existence trying to mess their system. I am all for the "i know better than anyone else" to get some nasty trojan and have to deal with it. People will be the monkeys they are going to be no matter what you do for them. :rolleyes:

----------

*bingo*

One can never have too much security, but any hacker finding a way to breach this sandboxing will then be able to go after all of the other holes thanks to the OS maker's laziness and false belief that sandboxing makes for a cozy impenetrable workaround.

Make believe super hacker, nice delusion.
 
Sandboxing is an good idea - e.g., better stability - but it is not worth it at the cost of reduced functionality. Unfortunately most of the 'improvements' we're seeing in the new OSs is glitz and glam rather than improved functionality. Apple needs to return the functionality that existed in previous systems to the OS. New advances should not destroy old functions.

----------

IBM owns Rosetta. Not Apple. So good luck in the courts trying to sue Apple for not stealing and giving away somebody else's software. There's probably other code in Classic that is not Apple's, but licensed with limitations as well.

Or were you planning on suing IBM?

Well, that makes it easier. I already own IBM.
 
Apple needs to return the functionality that existed in previous systems to the OS. New advances should not destroy old functions.

Apple has not removed any functionality of old OSes. You're confusing legacy APIs and old CPU architectures with functionality.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.