Slashdot Mirror


Apple In Trouble With Developers

geek writes "According to Marco Arment, the creator of Instapaper, Apple may be in trouble with developers. According to Arment, the new sandboxing guidelines from Apple are pushing developers away in droves. 'I've lost all confidence that the apps I buy in the App Store today will still be there next month or next year. The advantages of buying from the App Store are mostly gone now. My confidence in the App Store, as a customer, has evaporated. Next time I buy an app that’s available both in and out of the Store, I’ll probably choose to buy it directly from the vendor. And nearly everyone who’s been burned by sandboxing exclusions — not just the affected apps’ developers, but all of their customers — will make the same choice with their future purchases. To most of these customers, the App Store is no longer a reliable place to buy software.' Arment also comments on the 'our way or the highway' attitude Apple often takes in these situations and how it may be backfiring this time around."

343 comments

  1. Pray I don't change them further.... by jmorris42 · · Score: 5, Insightful

    Remember, that line didn't even work out for Vader and he had Star Destroyers and millions of clone troopers at his command. If you have the upper hand you can sometimes force people to accept a one sided deal. But if you go beyond that and keep changing the terms on it eventually everyone figures out they might as well take their chances because they are hosed anyway. You have to leave them some hope of survival.

    I especially liked how the article has this:

    "This even may reduce the long-term success of iCloud and the platform lock-in it could bring for Apple. Only App Store apps can use iCloud, but many Mac developers can’t or won’t use it because of the App Store’s political instability."

    Anyone who would write that, in the context of it being a good thing!, is obviously a Kool-Aid drinker. When you are driving those people away it is a warning sign.

    Imagine how badly Microsoft is going to bungle this same gambit. Notice how Valve is already running for the exits? Uh huh, good times ahead for everyone!

    --
    Democrat delenda est
    1. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 5, Funny

      But, according to John Romero, Android is a piracy platform and Apple TV will make you his bitch!

      And now! Daikatana 2!

    2. Re:Pray I don't change them further.... by exomondo · · Score: 4, Insightful

      alter, alter! not 'change'...on the other hand maybe George Lucas changed that line in Empire Strikes Back 're-imagined' special edition 2.

    3. Re:Pray I don't change them further.... by Desler · · Score: 1

      Notice how Valve is already running for the exits?

      No. Adding support for another OS as a hedge is not the same as ditching Windows since Windows will still be where the vast majority of their sales come from.

    4. Re:Pray I don't change them further.... by Lord+Lode · · Score: 3, Funny

      altered that line!

    5. Re:Pray I don't change them further.... by ackthpt · · Score: 2, Insightful

      All the more reason for Apple to hurt Android as much as they can, including Samsung, maker of wunnerful stuff Android-ish. If your developers flee to the greener pastures of Android, you must somehow poison those pastures so they have nowhere to run.

      --

      A feeling of having made the same mistake before: Deja Foobar
    6. Re:Pray I don't change them further.... by CanHasDIY · · Score: 4, Funny

      alter, alter! not 'change'...

      Perhaps he-sa tryin' to be avoidin' LucasArt lawyerin'!

      --
      An enigma, wrapped in a riddle, shrouded in bacon and cheese
    7. Re:Pray I don't change them further.... by jmorris42 · · Score: 1

      Yea, you are right. I was in a hurry so do I still have to turn in my geek card?

      --
      Democrat delenda est
    8. Re:Pray I don't change them further.... by Chas · · Score: 1

      Pray I don't Altair them any further???

      --


      Chas - The one, the only.
      THANK GOD!!!
    9. Re:Pray I don't change them further.... by ackthpt · · Score: 4, Funny

      Yea, you are right. I was in a hurry so do I still have to turn in my geek card?

      Say a couple "I'm am your father"s or "Do or do not. There is no try"s. You might be forgiven.

      Better line would have been "The more you tighten your grip, ..., the more ... will slip through your fingers."

      --

      A feeling of having made the same mistake before: Deja Foobar
    10. Re:Pray I don't change them further.... by jmorris42 · · Score: 0

      Read the article. Valve certainly hopes they can continue to sell most of their volume on Windows but they are stating on the record the Linux port is a hedge against a future where that won't be possible.

      If you think about it, it is almost certain that Steam on Windows is a dead product as soon as the lockdown hits x86. In a world of a single vendor app store Steam is, by definition, forbidden.

      Notice that, for now, Apple isn't even discussing locking OS X. They understand that step is an outright declaration of WAR! on a lot of the existing ecosystem. MIcrosoft is taking a huge risk but they pretty much have to because Win8 is one OS vs iOS and OS X.

      --
      Democrat delenda est
    11. Re:Pray I don't change them further.... by MachDelta · · Score: 5, Funny

      2012 and we still can't punch people in the face over TCP/IP...

    12. Re:Pray I don't change them further.... by jxander · · Score: 1
      --
      This signature is false.
    13. Re:Pray I don't change them further.... by Desler · · Score: 1

      but they are stating on the record the Linux port is a hedge against a future where that won't be possible.

      Funny since that was the same thing I said. So again, where did Valve start "running for the exits"?

    14. Re:Pray I don't change them further.... by ackthpt · · Score: 4, Insightful

      And yet, all the best games and applications are still being written for OSX, Windows, and iOS. You can keep preaching about how great open software is, but when it's hard to make money off the platform, the best developers are never going to go there. You're preaching idealism. MS and Apple preach profits. We live in a capitalist society - guess who wins?

      The gravy train comes with no guarantee you will always remain on it. Apple prospers while those who do business with Apple prosper. When Apple tries too hard to prosper all by themselves they begin to look like that company which nearly died before the second coming of Jobs.

      --

      A feeling of having made the same mistake before: Deja Foobar
    15. Re:Pray I don't change them further.... by cpu6502 · · Score: 1, Interesting

      Only copy of Star Wars 4/5/6 I have are the laserdisc masters that Lucas released to DVD. (Would be nice if he released the laserdisc masters to Bluray, and eliminate the dvd artifacting, but I'm not holding my breath.) I will watch the special defect versions if they air on TV, but I refuse to purchase them. Bad enough I paid $20 to see the primitive 90s CGI in the theater.

      --
      My AC stalker: " I personally agree with your posts most of the time, but that won't keep me from modding you troll"
    16. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 1

      Apple prospers while those who do business with Apple prosper.

      Absolutely true, and they'd do well to remember that.

      When Apple tries too hard to prosper all by themselves they begin to look like that company which nearly died before the second coming of Jobs.

      Well, we're not there yet. For the moment anyway, the real money in mobile app development is still on iOS. Remember that Apple has been grilled over their App Store curation before and they came out the other side wealthier than ever.

    17. Re:Pray I don't change them further.... by exomondo · · Score: 1

      Yea, you are right. I was in a hurry so do I still have to turn in my geek card?

      Nah, perhaps you were the victim of subliminal lucassing.

    18. Re:Pray I don't change them further.... by Dunbal · · Score: 1, Insightful

      Why? Such a quote is fair use. Lucas can suck a dick.

      --
      Seven puppies were harmed during the making of this post.
    19. Re:Pray I don't change them further.... by Wraithlyn · · Score: 1

      Harmy's Despecialized Editions.

      --
      "Mind, as manifested by the capacity to make choices, is to some extent present in every electron." -Freeman Dyson
    20. Re:Pray I don't change them further.... by Culture20 · · Score: 3, Informative

      Remember, that line didn't even work out for Vader and he had Star Destroyers and millions of clone troopers at his command.

      No he didn't. By "A New Hope", all of the clone troopers were dead or in retirement homes (they had their aging accelerated). The Storm Troopers were standard grunts hired from a thousand colony planets. Kenobi thinks they're the super precise shooting clones he remembers, but he's wrong. The only surviving clone is Boba Fett.

    21. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 2, Interesting

      but they are stating on the record the Linux port is a hedge against a future where that won't be possible.

      Funny since that was the same thing I said. So again, where did Valve start "running for the exits"?

      So Valve is positioning itself in front of the exit.

      Viva subtility!

    22. Re:Pray I don't change them further.... by thePowerOfGrayskull · · Score: 2, Insightful

      But, according to John Romero, Android is a piracy platform and Apple TV will make you his bitch!

      And now! Daikatana 2!

      In other news, different developers have different opinions.

    23. Re:Pray I don't change them further.... by fa2k · · Score: 1

      Apple has done things that are much more hostile to developers on iOS, and it's still a hot platform.

    24. Re:Pray I don't change them further.... by Dishevel · · Score: 1

      But Jobs is dead.
      We all know from experience what kind of decisions Apple makes when Steve is not at the helm.
      Apple is dying now that Steve is dead.

      --
      Why is it so hard to only have politicians for a few years, then have them go away?
    25. Re:Pray I don't change them further.... by PopeRatzo · · Score: 1

      Notice how Valve is already running for the exits?

      Which exit is that, genius?

      --
      You are welcome on my lawn.
    26. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 1

      We could in the '90s, but then Microsoft fixed all the TCP/IP features which enabled this.

      /join #lamerz

      *** User1 has quit IRC (Connection reset by peer)
      *** User2 has quit IRC (Connection reset by peer)
      *** User3 has quit IRC (Connection reset by peer)
      *** User4 has quit IRC (Connection reset by peer)

      Those were the days. By which I mean a childish waste of time. But I repeat myself.

      (OK, even Linux was vulnerable to some of the attacks for a while.)

    27. Re:Pray I don't change them further.... by PopeRatzo · · Score: 2, Insightful

      If you think about it, it is almost certain that Steam on Windows is a dead product as soon as the lockdown hits x86. In a world of a single vendor app store Steam is, by definition, forbidden.

      Notice that, for now, Apple isn't even discussing locking OS X. They understand that step is an outright declaration of WAR! on a lot of the existing ecosystem. MIcrosoft is taking a huge risk but they pretty much have to because Win8 is one OS vs iOS and OS X.

      Holy shit, you're on a roll.

      "When the lockdown hits x86"? "Notice that, for now, Apple isn't even discussing locking OS X."?

      Let's talk about it again when Microsoft is as close to locking down Windows as Apple is in locking down its OS. Right now between Apple and Microsoft only one of them has an operating system that is locked down. And to you, that's proof positive of the opposite.

      MIcrosoft is taking a huge risk but they pretty much have to because Win8 is one OS vs iOS and OS X.

      Have you noticed how OSX runs on actual desktop and laptop systems and iOS runs on handheld devices? That's like saying "Windows is one OS and Xbox is another, so it's 2 against 2".

      And I can't even think that far ahead because I'm still amazed that you believe "Valve is building a Linux version because they know there soon won't be any way for them to operate in Windows".

      --
      You are welcome on my lawn.
    28. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 2, Funny

      But Jobs is dead.

      I'm just waiting for the third coming

    29. Re:Pray I don't change them further.... by l0ungeb0y · · Score: 0, Flamebait

      Android? Greener Pastures? If you mean you'd rather code for Android users who would rather spend a week figuring out how to break and hack things to get around paying that exorbitant $0.99 for your app is preferable to coding for iOS and actually get that $0.70 from each App purchase.

      Funny how Linux users think everyone should work for free because they don't want to pay for shit.
      Of course this attitude has no bearing on why Linux fails to attract successful commercial products to it's OS
      and why Android is losing developers due to rampant piracy.

    30. Re:Pray I don't change them further.... by steelfood · · Score: 1, Funny

      It's funny how George Lucas pretty much did in the Special Editions to the fans (and future fans) what Vader did to Lando in ESB. Well, not exactly funny, but ironic maybe?

      --
      "If a nation expects to be ignorant and free in a state of civilization, it expects what never was and never will be."
    31. Re:Pray I don't change them further.... by jedidiah · · Score: 1, Insightful

      This has nothing to do with your twisted fantasies regarding Linux users.

      You want "cheap bastards", then you have to look no further than Windows users that happily steal anything that isn't nailed down and pass it around to random strangers.

      Windows is the platform of rampant piracy.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    32. Re:Pray I don't change them further.... by jedidiah · · Score: 1

      ...and Android.

      Also the breakdown is much more in favor of Windows. If you are some Apple Fanboy trying to lump your platform in with Windows then you're just a moron. MacOS is only slightly less obscure than Linux when it comes to 3rd party support.

      PhoneOS is much more of a thing. Apple was an early mover in a new space and has something of a lead. That doesn't magically improve the situation with Apple's computer OS.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    33. Re:Pray I don't change them further.... by jedidiah · · Score: 1

      Apple was pretty much on permanent deathwatch until a recent change of fortunes.

      Things change.

      The fact that Linux can't be done in by something like Apple going out of business means that it can linger on with or without a "year of the desktop". It may eventually take the world by storm but doesn't really need to.

      When the trolls have been laughing at you for 10+ years while you've been happily using the thing of your choice, the rantings of the trolls don't mean so much anymore.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    34. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 0, Flamebait

      And this post sounds like a butthurt developer who can no longer run rampant outside of his sandbox. He isn't forced to use the app store. He never was.

      The linked article cites no sources, shows no vast number of developers leaving, yet everyone is eating it up like candy.

      It means he can no longer just scan whatever files, contact, personal info, etc.

      Some apps will no longer be viable in the App Store if they perform functions that require that deep level of access.

      The vast majority won't be affected at all.

    35. Re:Pray I don't change them further.... by martin-boundary · · Score: 2

      Boba Fett! Boba Fett! Where?

    36. Re:Pray I don't change them further.... by flappinbooger · · Score: 1

      So we all want to paint with a big brush today, huh? Try this on for size while we're doin' comparisons...

      Android is more like windows than linux -

      Want to know why?

      2 reasons - it's a total 180 from iOS or OSX, and secondly, I've never had to run a freakin command line interface to get simple crap to work on android.

      Thus - Windows.

      Big enogh brush for y'all?

      --
      Flappinbooger isn't my real name
    37. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 0

      Are you fucking retarded?

    38. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 0

      You know your on Slash dot when we end up on start wars. I love this place.

    39. Re:Pray I don't change them further.... by xouumalperxe · · Score: 1

      I don't think it's a matter of drinking the kool-aid. It's more a matter of looking at it from Apple's perspective. The platform lock-in would be good for Apple, so he's arguing that not only is this change bad for consumers and developers, in harming the chances of that lock-in happening the change also harms apple's bottom line.

    40. Re:Pray I don't change them further.... by marcosdumay · · Score: 1

      If Steam runs on Linux, MS won't ever shut it down on Windows.

      It is not an escape route. It is caled "keeping the boat floationg".

    41. Re:Pray I don't change them further.... by Wovel · · Score: 1

      Did you know this article is about OSX?

    42. Re:Pray I don't change them further.... by GPL+Apostate · · Score: 1

      Apple was pretty much on permanent deathwatch.

      But when they split platforms to iOS and MacOS, and iOS became so successful... Well, there's only so much oxygen in a space, and Apple has successfully sucked all the oxygen surrounding them into iOS.

      It won't be too long before all MacOS has become is the build platform to build iOS apps on. Kind of like the expensive proprietary development platforms to build Nintendo games on.

      --
      Microsoft says legacy (serial/parallel) ports are bad. They don't obfuscate the hardware enough.
    43. Re:Pray I don't change them further.... by BitZtream · · Score: 0

      ...

      Right, because the stopped making new clones ... kind of how Apple stopped making computers after they sold me one.

      Stormtroopers are still clones, hence Lea's comment to Luke 'a little short for a storm trooper, aren't you?'

      I guess you ignored the different ages shown in the prequel as well at the clone factory, they weren't all the same age, ever. Replacements were part of the program from day one.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    44. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 0

      Yeah that line doesn't work out in the end... all you get is a carbon popsicle and a hairy gorilla-man and that you're going to be gifting to some fatass toad.
      You do not get the princess, you don't get the boy, and there is a disturbance in the force and you do not pass go and collect $400.

      And right now a lot of people are disturbed by your use of 'force', Apple. Go back to creating fragile but beautiful but over-priced notebooks!! Leave
      development to the pros ... and that's not just the 1500 some developers and dev support staff that work on OSX/iOS projects at Apple but the ~10,000
      professionals world-wide (yep, not too many either) that actually create the software people _want_/_need_ to use. (Who bought their mac because of iTunes?)
      (Who really uses Safari?) .

    45. Re:Pray I don't change them further.... by sco08y · · Score: 4, Funny

      It's funny how George Lucas pretty much did in the Special Editions to the fans (and future fans) what Vader did to Lando in ESB. Well, not exactly funny, but ironic maybe?

      Huh? It's been a while, but I don't recall a scene where Vader slaps Lando to the ground, says, "suck it, bitch, you'll buy it anyway" and shits in his face.

      (That's one kind of dramatic scene where a cape just doesn't work.)

    46. Re:Pray I don't change them further.... by shutdown+-p+now · · Score: 1

      This situation is somewhat different with Win8 Store, because the latter has all those restrictions from the get go. Developers of apps that don't mesh well with those restrictions won't go there in the first place, and so won't have their apps kicked out, as has happened here - and it's really this sudden disappearance of the app from the store (meaning you no longer get updates that way) is what stirs up the users.

      Coincidentally, it's partly also why it's not such a big deal on iOS - there, as well, developers' options were limited from day 1. Apple did introduce some more restrictions as they went - most notably the in-app purchase requirements - but those affected relatively few apps (albeit some high-profile ones). They simply didn't have the kind of apps that are now being kicked out of the Mac store to begin with. Well, and iOS having a good half of the market - and the better half, app developer earnings wise, at that - also helps.

    47. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 0

      You're reading the wrong version of the spec - it's clearly "stab"

      http://bash.org/?4281

    48. Re:Pray I don't change them further.... by ilsaloving · · Score: 1

      Sssshhhhh! You're getting in the way of a perfectly good rant!

      *makes popcorn*

    49. Re:Pray I don't change them further.... by ATMAvatar · · Score: 1

      The de facto reality is that fair use died with the DMCA. All it takes is some harassment via take down notices to scare someone away from fair use of a snippet that the copyright holder doesn't like.

      --
      "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety."
    50. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 0

      I assume:
      1) It's a long time since you last used linux
      2) I'm sure I'll find pretty boring everything you do with your android devices.

    51. Re:Pray I don't change them further.... by Barlo_Mung_42 · · Score: 0

      Wait, so on android you have to use a freaking command line to do interesting things? I guess it really is Linux.

    52. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 0

      "MacOS is only slightly less obscure than Linux when it comes to 3rd party support." Spoken like someone who doesn't know what the hell they're talking about.

      First of all, Linux is very well supported by 3rd parties in certain areas - much better than Mac OS. For example, there is SAP NetWeaver for Linux, but not Mac OS. Eclipse, OpenOffice and many other cross-platform tools (open and closed source) that work on Mac OS are nonetheless much better supported on Linux. In fact, almost anything infrastructure related (Apache, Samba, VMWare, etc.) has a much larger and well organized support base on Linux than Mac OS. The support Mac OS has in these areas is mostly inherited from BSD.

      Now, on the other hand, Mac OS has much better 3rd party support for consumer apps in general than Linux, and is indeed on par with Windows in many ways. For example, nearly all of Adobe's products are available on Mac OS, Microsoft Office, Flash, Quicken, etc. Almost any piece of consumer hardware now has support for Mac OS out of the box as well (f.e. WebCams, Wacom tablets, the firmware updater for my router, etc!). Granted, some of this hardware support is due to the standardization of protocols brought about by USB and the like. I know a lot of "switchers", like my girlfriend, who aren't exactly computer geeks, and very few of them have issues with some missing critical app.

      So if you want to make the point that Mac OS Server isn't well supported, I will agree with you, but for that, there is Linux.

    53. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 0

      I have changed the moving picture show. Pray I do not change it further. - Darth Lucas.

    54. Re:Pray I don't change them further.... by ultranova · · Score: 2

      It's too late. The lawyers shot first.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    55. Re:Pray I don't change them further.... by Spugglefink · · Score: 1

      ...Windows users that happily steal anything that isn't nailed down and pass it around to random strangers.

      I'll never forget the time I gave a copy of OpenOffice.org to a coworker who was talking about going over to so-and-so's house to "get the office put on" her new computer.

      " Hey, here, try this, you can have a copy free and give as many copies away as you like, and it's all perfectly legal!"

      "Well, I looked at that thingie you gave me, and it looked slightly different, so I went over to so-and-so's house and got my computer fixed."

      "What do you mean 'fixed?' You mean you pirated a copy of some rather expensive commercial software? The last time I bought a copy of Microsoft Office, I paid almost $400 for it."

      "$400?! Why would you pay $400? Just go over to so-and-so's house and get the office put on. It's free."

      "Sigh."

      The whole thing makes me think what a dumbass I am. I haven't pirated software since I was old enough to have a job. I switched to Linux 13 years ago in part because software was just too damn expensive, and putting up with all of Linux's crap is very cheap compared to all the money I saved on software. Thousands and thousands of dollars by now, surely. It's so cool walking past a software store, because there's nothing in there that would run on my computer anyway.

      Watching desktop Linux slowly spiraling toward the big hole in the bottom of the toilet all these years isn't so gratifying though.

      Sigh.

    56. Re:Pray I don't change them further.... by BitZtream · · Score: 0

      and it's really this sudden disappearance of the app from the store (meaning you no longer get updates that way) is what stirs up the users.

      So you've never used the AppStore and keep listening to rumors eh?

      Something being pulled from the store because it doesn't meet new requirements doesn't' result in the developer being unable to provide updates or people being able to redownload it. It simply stops being available for sale. This is the same retarded bullshit that was spread around when they stopped selling that app for autistic people.

      Apple has pulled ONE app off the store AND revoked its key so it stopped working on devices, and thats because it was violating security requirements and sending information it shouldn't have been to 3rd party servers ... IN CLEAR TEXT rather than SSL.

      Any other 'pulled from the store' means 'no longer for sale', nothing else. The reason you won't get updates is because the developers then abandon the app because they don't want to be bothered to meet the requirements and without future sales, theres no motivation for most to actually provide the support they claimed to provide initially.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    57. Re:Pray I don't change them further.... by shutdown+-p+now · · Score: 1

      So how exactly would a non-sandboxed app pass review for the next update? Or are you saying that there's still some special exemption in force for apps already in the store?

    58. Re:Pray I don't change them further.... by Kalriath · · Score: 3, Informative

      Bollocks. All kinds of apps are simply impossible to produce within the constraints imposed by the App Store. Like menubar icons that let you plug into iTunes for example (and before you point out that tools like these already exist, I will point out that those are all using temporary entitlements.

      I strongly suspect cool apps like TotalFinder also violate no end of App Store policies as well.

      Or how about an app that simply goes through a folder and renames/deletes some files according to user parameters (like A Better Finder Rename for example)? Impossible - permission must be obtained by means of a file open dialog for every single file the app wants to manipulate.

      Sandboxing is bullshit. Or rather, Apple's implementation of it is bullshit.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    59. Re:Pray I don't change them further.... by Kalriath · · Score: 1

      Actually, an app being pulled from the store does prevent the developer being able to provide updates unless the developer can make it comply with the requirements. But... newsflash... for some apps it is literally impossible to make the app comply with the new guidelines, for example an app that did bulk file renaming cannot be sandboxed, because it needs permission to modify all files in a folder tree. Which it can't do by the way, because the only way to get permission to modify a file is to pop up an open dialog and get the user to browse to it. The developers only option in this case would be to drop the app store like a hot potato, and everyone who bought off the app store is screwed because the developer cannot validate that the user has actually bought it before to offer them a free crossgrade or whatever.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    60. Re:Pray I don't change them further.... by Kalriath · · Score: 1

      There isn't. That guy is talking bollocks.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    61. Re:Pray I don't change them further.... by asdf7890 · · Score: 1

      Notice how Valve is already running for the exits?

      Not quite. They are setting up an extra stall outside, in the expectation that a fair few users will make for the exists. They are increasing their potential total market, not leaving one subset of the market in favour of another.

    62. Re:Pray I don't change them further.... by jythie · · Score: 1, Insightful

      Pity I don't have modpoints, this really shouldn't be '-1 Flamebait'.

      Unfortunately, right now any negative story about Apple (just like Microsoft a few years ago) is ran with since it fits into the currant narrative. All the cool kids hate Apple, and if you want to be part of the in crowd you have to loudly proclaim how horrible Apple is to everyone. Pointing out any possible flaw in the rants makes you a fanboy or troll.

    63. Re:Pray I don't change them further.... by jythie · · Score: 1

      Meh, Apple is always 'dying' for one reason or another.

    64. Re:Pray I don't change them further.... by Anonymous Coward · · Score: 0

      That is not correct. Apple is sandboxing Mac OS X and Mac OS apps will have to be sandboxed to be accepted into the Mac OS app store very soon.

      When you load up Mountain Lion, you will discover that by default the system will not run unsigned apps, including the ones you bought from them and other notable vendors.

      I have been resisting learning objective C, hoping to continue writing portable C++ applications against the Unix API's and other well known interfaces like X and python. I don't know yet if the sandboxing system only works for objective C Cocoa programs. If that is the case, I may not want to write applications fort the Mac and may switch to Linux and hope for the best.

    65. Re:Pray I don't change them further.... by Guy+Harris · · Score: 2, Informative

      That is not correct. Apple is sandboxing Mac OS X and Mac OS apps will have to be sandboxed to be accepted into the Mac OS app store very soon.

      When you load up Mountain Lion, you will discover that by default the system will not run unsigned apps, including the ones you bought from them and other notable vendors.

      Note that "signed" does not imply "sandboxed". The default Gatekeeper setting means that, unless you do Special Stuff, applications downloaded from the Intertubes (by programs that set the "quarantined" extended attribute, at least; dunno if any applications that set it do so only if they were downloaded from an "external" site, for some definition of "external") can't be launched with a double-click (or, presumably, automatically through some code paths) unless they're from the Mac App Store or signed by a "registered developer", even if they're not sandboxed. There are ways (involving a context menu, i.e. Control+click, I think) to override that without changing the default setting.

      I have been resisting learning objective C, hoping to continue writing portable C++ applications against the Unix API's and other well known interfaces like X and python. I don't know yet if the sandboxing system only works for objective C Cocoa programs.

      As far as I know, at least some of the sandboxing is ultimately implemented with Mandatory Access Control hooks in the kernel (see the security top-level directory in the XNU source, and stuff it calls and that calls it), which means it applies to anything that makes system calls, either directly or through libraries or frameworks, regardless of whether it's written in C or C++ or Objective-C or Objective-C++ or FORTRAN or..., as long as it's a statically-compiled language (if it's interpreted, the calls are made by the interpreter, which isn't sandboxed, and if it's compiled on the fly, the code that's running the generated code would need to be sandboxed; I don't know whether software of either type is allowed in the Mac App Store). Some of it might be implemented at the Mach messaging level, which means that part applies to anything that sends Mach messages to the services to which access is controlled, either directly or through libraries or frameworks, regardless of whether it's written in C or C++ or Objective-C or Objective-C++ or FORTRAN or... (same comments apply as in the previous sentence).

      However, if you want to sell or give away your app via some mechanism other than the Mac App Store, you don't need to sandbox it. To have it launchable with the default settings on Mountain Lion, you'd have to join the Mac Developer Program and get a Developer ID and corresponding certificate with which to sign your code.

      (And if you just want to build your own code and run it on your own machine, you don't, as far as I know, even need that, as the code hasn't been downloaded from the Intertubes and thus hasn't had a quarantine label slapped on it. And if you've downloaded the code with, say, curl, that might not slap a quarantine label on it, either.)

    66. Re:Pray I don't change them further.... by Keen+Anthony · · Score: 1

      This is correct. If I remember correctly, the Stormtrooper Corps is actually the Grand Army renamed. I think it's possible there were human recruits. Both the Imperial Army and the Imperial Navy used human recruits, and licensed 3rd party sources such as West End Games' original Star Wars roleplaying game featured recruiting ads promoting the Corps. If you were going to clone your stormtroopers, why stop there and not clone the AT-ST/AT-AT pilots Lea's comment about Luke's height could have been a reference to cloning, but it could also indicate that the Corps has strict requirements for height and weight. Another possibility is that Lea, like most Rebel scum, enjoys taking shots wherever she can regardless of whom she hurts. Just saying, kill many Bothans, bloody war crime! Destroy an under construction Death Star filled with thousands of human independent contractors and wreak havoc with the galactic economy just so the only chick in the galaxy can take over, huzzah!! Watch, someone's going to whine about how Alderaan was a peaceful planet of nerfherders with no weapons of any kind and accuse me of being an Alderaanian Holocaust denier.

    67. Re:Pray I don't change them further.... by macs4all · · Score: 1

      Read the article. Valve certainly hopes they can continue to sell most of their volume on Windows but they are stating on the record the Linux port is a hedge against a future where that won't be possible.

      If you think about it, it is almost certain that Steam on Windows is a dead product as soon as the lockdown hits x86. In a world of a single vendor app store Steam is, by definition, forbidden.

      Notice that, for now, Apple isn't even discussing locking OS X. They understand that step is an outright declaration of WAR! on a lot of the existing ecosystem. MIcrosoft is taking a huge risk but they pretty much have to because Win8 is one OS vs iOS and OS X.

      Not to mention that Apple would be DAFT (and they aren't daft!) to drive developers away from the platform, especially when it has (finally!) gotten them interested en masse.

      What is really going on is that Apple simply wants to establish the Mac App Store (much like the iOS App Store) as a safe haven, where users (remember them? The ones that actually BUY a developer's output?) can go and purchase software that not only is, to the best of Apple's ability to determine, malware-free; but employs what Apple considers to be "best practices" in its design. And one of those "best practices" is, to the chagrin of some developers, "sandboxing".

      And always keep in mind that Apple does not force OS X developers to use these guidelines; it merely means that those developers have to distribute their wares in what was not only the only way possible before the App Store, but one that most Slashdotters seem to think is better in the first place!

    68. Re:Pray I don't change them further.... by Guy+Harris · · Score: 1

      It won't be too long before all MacOS has become is the build platform to build iOS apps on.

      ...and the platform for users for whom iOS's simplification of the User Experience(TM) crosses their threshold of "simpler" in "Make things as simple as possible, but not simpler." (I'm one of those users - "sorry, only one window on the screen at a time" doesn't work for me, and neither does "documents should be organized by the application for which they're intended" rather than by "what they're about".)

    69. Re:Pray I don't change them further.... by tlhIngan · · Score: 1

      Note that "signed" does not imply "sandboxed". The default Gatekeeper setting means that, unless you do Special Stuff, applications downloaded from the Intertubes (by programs that set the "quarantined" extended attribute, at least; dunno if any applications that set it do so only if they were downloaded from an "external" site, for some definition of "external") can't be launched with a double-click (or, presumably, automatically through some code paths) unless they're from the Mac App Store or signed by a "registered developer", even if they're not sandboxed. There are ways (involving a context menu, i.e. Control+click, I think) to override that without changing the default setting.

      An interesting point - Gatekeeper does NOT restrict applications NOT downloaded from the internet (determined by an external attribute on the file).

      This could be when the lockdown happens, a golden opportunity for Open Source - by providing two ways to put programs on the new OS X if (a very unlikely if) Apple decides the only way to get stuff from the 'net is via Mac App Store. You see, all one needs to do is install the developer tools, then compile the program oneself.

      Mac OS X - binaries only via Mac App Store, source code otherwise (in the unlikely case Apple makes it MAS only. Notably - there are policy issues (Free to $1000 is too limiting for some apps that cost multiple thousands of dollars, Adobe, Microsoft, some stuff you can't do as a MAS app, etc).). Won't be long until someon resurrects Fink and other projects - the package manager would have to be passed around somehow, but then the whole world of open-source is at one's fingertips.

    70. Re:Pray I don't change them further.... by Stuarticus · · Score: 1

      You need something to wipe with, cape seems a good option if you're planning on doing it to millions of fans, always handy.

      --
      If you think someone isn't free to have a different definition of "freedom" you may be a tyrant.
  2. well by masternerdguy · · Score: 1

    they say the meek shall inherit

    --
    To offset political mods, replace Flamebait with Insightful.
    1. Re:well by wonkey_monkey · · Score: 4, Funny

      What was that about the cheesemakers?

      --
      systemd is Roko's Basilisk.
    2. Re:well by hsmith · · Score: 1

      Let them eat cake?

    3. Re:well by Anonymous Coward · · Score: 0

      Shut up big nose!

  3. Incoming by Anonymous Coward · · Score: 1
    Apple Defence Force!

    ASEMBLEEEEEE!!!!

    1. Re:Incoming by Anonymous Coward · · Score: 0

      form of a mac doesn't get viruses

    2. Re:Incoming by Anonymous Coward · · Score: 0

      form of a but windows is worse.

    3. Re:Incoming by Anonymous Coward · · Score: 0

      Shape of, "It just works"

    4. Re:Incoming by Anonymous Coward · · Score: 0

      form of a trojans aren't viruses so technically it's still true even if it doesn't make any difference to anyone

    5. Re:Incoming by MobileTatsu-NJG · · Score: 2

      Apple Defence Force!

        ASEMBLEEEEEE!!!!

      Has anybody else noticed that the Haterade Addicts are calling four meetings a day now?

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

  4. Snake Bites Own Tail by ackthpt · · Score: 1

    and it's not even Quezovercoatl

    I guess the squeezing of developers & customers has finally come around to hurt Apple, after such a promising start, too. Couldn't happen to a nicer company.

    --

    A feeling of having made the same mistake before: Deja Foobar
    1. Re:Snake Bites Own Tail by CanHasDIY · · Score: 1

      and it's not even Quezovercoatl

      I think you have your serpents of legend a bit confused

      --
      An enigma, wrapped in a riddle, shrouded in bacon and cheese
    2. Re:Snake Bites Own Tail by jbeaupre · · Score: 1

      He's referring to London Fog mythology.

      --
      The world is made by those who show up for the job.
    3. Re:Snake Bites Own Tail by Anonymous Coward · · Score: 0

      That particular motif is much older.

    4. Re:Snake Bites Own Tail by 93+Escort+Wagon · · Score: 1

      He's referring to London Fog mythology.

      Hmm... I don't see a raincoat reference anywhere.

      --
      #DeleteChrome
    5. Re:Snake Bites Own Tail by Anonymous Coward · · Score: 0

      Or perhaps http://en.wikipedia.org/wiki/Ouroboros ?

    6. Re:Snake Bites Own Tail by ultranova · · Score: 1

      I don't see a raincoat reference anywhere.

      They've been outlawed by the Olympic Committee as potential covers for terrorists.

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    7. Re:Snake Bites Own Tail by jbeaupre · · Score: 1

      Quezovercoatl

      --
      The world is made by those who show up for the job.
  5. Perhaps the walled-garden was bad after all. by sethstorm · · Score: 3, Insightful

    These are the things you get with the lack of openness - in favor of the One True Platform where everything must submit to the One True Experience

    --
    Twitter supports and protects racists - by smearing their critics with the "Hate Speech" label.
    1. Re:Perhaps the walled-garden was bad after all. by ackthpt · · Score: 1

      These are the things you get with the lack of openness - in favor of the One True Platform where everything must submit to the One True Experience

      And the fun bit(!) -> When so many people have bought Apps developed outside the sandbox and they won't run on the next i(thingy) so people are less likely to upgrade right away <- thus hitting the ol' Wall Street revenue expectations.

      Ah, what a tangled web the weave. Where's me popcorn?

      --

      A feeling of having made the same mistake before: Deja Foobar
    2. Re:Perhaps the walled-garden was bad after all. by Anonymous Coward · · Score: 0

      It shall be an interesting year. Suddenly, the App Store is not perfect. Developers don't think the MS App Store will be good either even before it has been opened. This shall be an interesting time, and very much fun to watch (but not to experience, we will pay for it after all).

    3. Re:Perhaps the walled-garden was bad after all. by Kohath · · Score: 1

      These are the things you get with the lack of openness

      Internet whining? You pretty much get that all the time, regardless of openness.

    4. Re:Perhaps the walled-garden was bad after all. by Guy+Harris · · Score: 1

      And the fun bit(!) -> When so many people have bought Apps developed outside the sandbox and they won't run on the next i(thingy)

      The apps being discussed here don't run on any "i(thingy)", as they don't run on the OS that "i(thingies)" run. They run on OS X, not iOS, and the App Store being discussed is the Mac App Store.

  6. App Store by Lord+Lode · · Score: 3, Insightful

    This summary contains the word "App Store" a few more times than necessary...

    1. Re:App Store by wonkey_monkey · · Score: 1

      Since all the usages are part of a quote, there's not a lot an editor can do. Inasmuch as the editors do anything at all, that is.

      --
      systemd is Roko's Basilisk.
    2. Re:App Store by Anonymous Coward · · Score: 0

      Well, if that's a problem, there's an app for that.

    3. Re:App Store by Volguus+Zildrohar · · Score: 3, Funny

      They didn't App Store it would App Store you so much.

      --
      When confronted with one problem, some think "I'll use recursion". Now they are confronted with one problem.
    4. Re:App Store by Em+Adespoton · · Score: 5, Insightful

      And it missed a line:
      "Disclaimer: Marco Arment, the creator of Instapaper, is likely more than a bit disgruntled with Apple, now that the functionality of Instapaper has been rolled into Safari."

      Apple has a history of driving away developers by incorporating their ideas into the bundled apps. Not many developers though... only those of really well thought out OS enhancements.

      While Marco does have a point, the timing of the statement smacks more than a bit of sour grapes. As a developer, he's known the sandboxing exemptions were temporary for, well at least a year. He's had more than a month since the sandbox closed its lid. I think he'll find that anyone developing heavyweight applications never even entered the App Store; they're still going strong on their own. The App store does great things for apps that are happy to live within the sandbox though; lightweight apps that have nothing to do with managing the computer but instead accomplish specific tasks.

      What Marco will find is that for every serious application developer leaving the Mac App Store, there are 50 App developers moving in -- some of them migrants from the iOS App Store, who are just adding a secondary target to their development builds.

      In my opinion, the App Store was never the place for non-sandobxed software in the first place. In time, Apple may create more sandbox features that will enable more heavy applications to re-enter the Store, but this will only be after the honeymoon period is over with the "App" crowd -- expect another year of shakedown before anyone doing complex OS tasks can "trust" the store.

      Kudos to Apple though for starting in restricted mode and slowly enabling more features -- and at the same time having a blanket exemption period for more serious developers to play with the store and see if it's right for them.

    5. Re:App Store by Anonymous Coward · · Score: 0

      Apple has a history of driving away developers by incorporating their ideas into the bundled apps. Not many developers though... only those of really well thought out OS enhancements.

      It's a good thing, too, or else to get a functional OS you'd have to buy and install dozens of utilities. Remember when the only TCP/IP implementations for Windows were third party? The ultimate goal is to create a great experience that users are willing to pay for, and anything that gets in the way tends to get railroaded. That's not a problem, that's progress.

    6. Re:App Store by shutdown+-p+now · · Score: 1

      What Marco will find is that for every serious application developer leaving the Mac App Store, there are 50 App developers moving in -- some of them migrants from the iOS App Store, who are just adding a secondary target to their development builds.

      The only problem is that those 50 apps that "move in" will still be unable to replicate the full convenience and power of 1 app that moves out...

    7. Re:App Store by sco08y · · Score: 1

      Apple has a history of driving away developers by incorporating their ideas into the bundled apps. Not many developers though... only those of really well thought out OS enhancements.

      It's a good thing, too, or else to get a functional OS you'd have to buy and install dozens of utilities. Remember when the only TCP/IP implementations for Windows were third party? The ultimate goal is to create a great experience that users are willing to pay for, and anything that gets in the way tends to get railroaded. That's not a problem, that's progress.

      Yup, better, when there were multiple 3rd party implementations for scanners and Bluetooth. Oh, you want to use your scanner with two apps? Suck it homeslice, the drivers you need can't be installed at the same time.

    8. Re:App Store by BitZtream · · Score: 0

      Heh, thats your bitch? The title makes a statement of fact about apple hurting devs yet the actual story or even the summary submitted does not make it a statement of fact but a possibility that may happen in the future.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    9. Re:App Store by Kalriath · · Score: 2, Informative

      And it missed a line:
      "Disclaimer: Marco Arment, the creator of Instapaper, is likely more than a bit disgruntled with Apple, now that the functionality of Instapaper has been rolled into Safari."

      Apple has a history of driving away developers by incorporating their ideas into the bundled apps. Not many developers though... only those of really well thought out OS enhancements.

      What you really mean is that Apple has a history of outlawing functionality of a popular app, then promptly rolling the feature they outlawed into their own software. They make Microsoft's history of steamrolling ISVs look positively friendly. In fact, Apple does exactly what everyone here complains about Microsoft doing - except they do it much more frequently.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    10. Re:App Store by Guy+Harris · · Score: 1

      What Marco will find is that for every serious application developer leaving the Mac App Store, there are 50 App developers moving in -- some of them migrants from the iOS App Store, who are just adding a secondary target to their development builds.

      Well, it's a bit more than that, if by "just adding a secondary target to their development builds" you mean "just tweaking the build targets in the project file without writing any new code" - AppKit and UIKit are different APIs.

    11. Re:App Store by Guy+Harris · · Score: 1

      What you really mean is that Apple has a history of outlawing functionality of a popular app,

      "Outlawing" in what sense? If you're referring to OS X apps (which is what Arment was discussing), a history of "outlawing" in the sense of "banning from the Mac App Store software that provides that functionality", that history dates back at most a couple of years, given that the Mac App Store was announced in October 2010. If you mean "outlawing" in the sense of "removing APIs that allow that functionality to be provided", that's a different matter (note that's "APIs", not "internal interfaces that people have figured out how to use and that Apple later decided weren't the right way of doing things and just nuked", which is perfectly legitimate behavior).

    12. Re:App Store by Kalriath · · Score: 1

      They've been doing it on the iTunes App Store since it launched. Look at, for example, that tethering app by NullRiver.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    13. Re:App Store by Guy+Harris · · Score: 1

      They've been doing it on the iTunes App Store since it launched. Look at, for example, that tethering app by NullRiver.

      OK, so you're not referring to the Mac App Store, as that was an iOS app. And whether they kicked it out of the iOS App Store because they wanted to do it themselves or because AT&T (the only iPhone carrier at the time) didn't want tethering allowed on the iPhone is another matter. Once AT&T said OK to tethering, it would be kinda silly for Apple not to build it in.

    14. Re:App Store by Em+Adespoton · · Score: 1

      True; it still needs porting, but the assets can stay the same. I probably dumbed it down a bit too much in that comment -- but it's still simpler than an all-out port between most platforms.

  7. A lot faster than I thought by Cute+Fuzzy+Bunny · · Score: 2, Insightful

    I figured a year or two before Steve being gone would doom the Appleistas. Happened a lot faster than I thought.

    Perhaps they'll have less profits to hide in tax structures in other countries so they don't have to pay Uncle Sam.

    1. Re:A lot faster than I thought by Desler · · Score: 4, Insightful

      Except there is no evidence that developers are "leaving in drones" neither from the linked blog posting or anything from the summary. That was just sensationalism added in to rile up the Apple crowd.

    2. Re:A lot faster than I thought by exomondo · · Score: 5, Funny

      Except there is no evidence that developers are "leaving in drones"

      If i were leaving i don't think a drone would be my preferred conveyance.

    3. Re:A lot faster than I thought by Anonymous Coward · · Score: 0

      I'd think this incarnation is what Steve would have wanted...control control control.
      Plus, it hasn't been that long. Wouldn't these requirements have been locked down under his reign? Software, especially something as complex as an App Store, doesn't happen overnight.

    4. Re:A lot faster than I thought by Kohath · · Score: 4, Insightful

      Who needs evidence? Apple is "in Trouble". Because someone has a complaint. No one ever had a complaint before. Ever.

    5. Re:A lot faster than I thought by steelfood · · Score: 1

      It happens occasionally.

      --
      "If a nation expects to be ignorant and free in a state of civilization, it expects what never was and never will be."
    6. Re:A lot faster than I thought by Anonymous Coward · · Score: 0

      Except that a bunch of good apps that used to be on the app store aren't there anymore. I guess the amount of shitty developers pouring their ported iOS junk into the store makes up for it but suffice to say the quality of the thing is going downhill for a lot of core software.

      You do of course know that all of Apple's own software has to cheat the rules right? None -- absolutely zero -- of their desktop apps are or can be sandboxed, and for stuff like Xcode and lion they simply resort to simply shipping the installer through the store rather than building support for this kind of stuff in from the beginning.

    7. Re:A lot faster than I thought by cpu6502 · · Score: 1

      But you forget that Steve was still alive when this Sandbox came about. It was either his idea or he approved its development. It's got Steve written all over it.

      --
      My AC stalker: " I personally agree with your posts most of the time, but that won't keep me from modding you troll"
    8. Re:A lot faster than I thought by Desler · · Score: 1

      Except that a bunch of good apps that used to be on the app store aren't there anymore.

      And by "a bunch" you mean a handful that in no way implies "droves" of developers leaving?

      You do of course know that all of Apple's own software has to cheat the rules right? None -- absolutely zero -- of their desktop apps are or can be sandboxed, and for stuff like Xcode and lion they simply resort to simply shipping the installer through the store rather than building support for this kind of stuff in from the beginning.

      No shit? How else do you expect something like XCode to work if it's sandboxed? You realize you a sandbox makes things like debuggers worthless, right?

    9. Re:A lot faster than I thought by Anonymous Coward · · Score: 0

      You do realize that this means that Apple is the only one who can put certain types of apps in the store? You do realize the implications?

    10. Re:A lot faster than I thought by ninetyninebottles · · Score: 1

      You do of course know that all of Apple's own software has to cheat the rules right? None -- absolutely zero -- of their desktop apps are or can be sandboxed...

      WTF are you talking about? Apple apps were the only one sandboxed in Leopard and they've been adding more and more in every release. Hell that's why OS X was immune to several of the service level exploits that hit Linux, Apple's version of the service was sandboxed.

      and for stuff like Xcode and lion

      You chose the primary IDE and a new release of the OS as your examples of Apple "Apps"? Seriously?

    11. Re:A lot faster than I thought by Guy+Harris · · Score: 1

      You do of course know that all of Apple's own software has to cheat the rules right? None -- absolutely zero -- of their desktop apps are or can be sandboxed...

      WTF are you talking about? Apple apps were the only one sandboxed in Leopard and they've been adding more and more in every release.

      For example, Preview and TextEdit, as well as several daemons, were sandboxed in Lion.

    12. Re:A lot faster than I thought by Kalriath · · Score: 1

      I suspect he's referring to Apple's App Store apps - things like Pages, Numbers, Keynote, Configurator, Final Cut, Logic, iPhoto, iMovie.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    13. Re:A lot faster than I thought by BitZtream · · Score: 0

      Xcode is on the app store and sandboxed.

      It also askes for permissions to do extra stuff outside the sandbox, and install things like command line tools and hooks for debugging permission without prompting every time.

      Which is funny because EVERY APP CAN DO THIS. The sandbox really isn't an issue if you bother to do what Apple says. For ever app thats been kicked out, I've figured out a legitimate way to get around it and stay on the app store.

      Its worth pointing out that Instapaper author really isn't pissed about sandboxing, he's pissed because his app is built into the web browser on the OS now, unfortunately slashdot is now nothing more than a money who so they warp the story into a flat out lie. Even the summary and the title show they are out for sensationalism. The title implies a fact that they are in trouble, where as the first sentence posses it as a question.

      There is a reason Cmdr Taco left.

      I would like to point out that I have an app on the app store that functions as a mail.app plugin, which is CLEARLY WELL outside what you would think is acceptable in sandboxing. You know, like me playing in an OS level apps application bundle rather than my own.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    14. Re:A lot faster than I thought by Guy+Harris · · Score: 1

      I suspect he's referring to Apple's App Store apps - things like Pages, Numbers, Keynote, Configurator, Final Cut, Logic, iPhoto, iMovie.

      To which "he" are you referring? The person claiming that "None -- absolutely zero -- of their desktop apps are or can be sandboxed..." or the person saying that "Apple apps were the only one sandboxed in Leopard and they've been adding more and more in every release"? If none of the Mac App Store apps are sandboxed - which may or may not be the case, depending on whether those apps still support Snow Leopard and on whether Snow Leopard supports sandboxing at the level that those Mac App Store apps need (e.g., whether all of the entitlements used by those apps exist in Snow Leopard) - I suspect Apple views that as a temporary situation for most of the apps, to be resolved in future versions of the apps (and, if new entitlements are required, future versions of the OS). I doubt the "...or can be sandboxed" part of the first of those claims. There might be some that can't, but I really doubt any of the components of iWork can't ever be sandboxed, for example.

    15. Re:A lot faster than I thought by Cute+Fuzzy+Bunny · · Score: 1

      Quite hilarious watching my original comment being modded up to 4 and back down to 1. Perhaps these threads should be exiled to a political forum?

    16. Re:A lot faster than I thought by Cute+Fuzzy+Bunny · · Score: 1

      I suspect that Steve had very little to do with day to day operations during the last six months, and he was officially on leave of absence for large portions of his final year and a half. While I'm sure he had say on a lot of things, my original comment had to do with the fact that previously, apple could really do no wrong as far as its customers and a large chunk of the press went. That no longer seems to be the case.

      This may be a bogus article, but in the last year apple got whacked with a lot of bad PR around their manufacturing and profit/tax schemes, they're getting nicked on malware hitting their machines and app store, their developers are displeased with some things, and they may have a couple of bad quarters while everyone waits for the iphone 5, which better be freaking awesome to make up for the waiting game.

      Be interesting to see how this malware thing works out. Among my friends who (IMO) waste a lot of money buying apple equipment, the reason why they parted with so much money is because they thought the machines were virus and malware proof. Of course, anyone who has any inkling about how computers work would know that there is no such thing as proofing against viruses and malware. So now that kimono is gone, see what they want to buy the next go-round...a $2000 laptop that can be attacked by viruses and malware just as easily as a $1000 ultrabook.

    17. Re:A lot faster than I thought by Cute+Fuzzy+Bunny · · Score: 1

      And its still going on!

      Hey modulators, I tend to do a fair bit of that around here as well, so let me offer a little advice. Moderation is about raising things up that lots of people would find interesting and funny, and suppressing stuff that adds no value or serves only to anger/frustrate/mislead a majority of readers.

      What it isn't is a position to air your personal grievances, express your fanboi-ism, or any other horseshit. I suppose thats why they don't have fixed moderators in great numbers here.

      My OP was a well formed opinion worthy of discussion. Its disappointing to see it turned into a tug of war between the fanboy moderator of the hour and the more reasonable.

      You might also be interested in finding out what happens when your moderation efforts are frequently undone by offsetting moderation...

    18. Re:A lot faster than I thought by Kalriath · · Score: 1

      The person claiming none. However, I strongly suspect that one or more of them actually are sandboxed.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  8. Agree by bhlowe · · Score: 1, Insightful

    I agree, sandboxing has been a bitch. Should be able to turn it off for apps the user trusts...

    1. Re:Agree by iluvcapra · · Score: 5, Interesting

      If you go back to the article Ament links to, their complaints are:

      No free trials
      No discounted upgrades
      No free upgrades if the prior version was purchased after a specific date
      No way to provide license keys that could be used on Windows (many of our customers use both platforms)
      No volume discounts or site licensing
      No access to customer information, which prevented us from validating orders, offering discounts, running promotions, newsletter signups, etc.
      Unclear refund policies
      Most importantly, we had to create another version of Postbox for the Mac App Store that removed features such as iCal support, iPhoto integration, and Add-Ons in order to comply with Apple’s Application Guidelines

      None of these, save the last one, have anything to do with sandboxing. The last one does, but I don't understand it, because access to the user's calendar and photos are explicitly-defined entitlements that you can access, all you have to do is check a box in Xcode. A sandboxed app cannot access the filesystem of the computer, except for paths specifically named by the user in an Open or Save dialogue (the dialogue boxes are run by a separate daemon that passes the paths to the client application over IPC, so you can't futz with it to pick open more of the user's fs than they specifically let the application see.) Obviously this is deadly to bulk renamers, but I don't understand the complaint in the context of document creation, utilities or accessories, games, or really anything but document indexers -- which would have to just be sold the old fashioned way, on a website.

      --
      Don't blame me, I voted for Baltar.
    2. Re:Agree by jcr · · Score: 1

      Oh, like this?

        If you’re sure the app is safe, you can manually override Gatekeeper by Control-clicking the app and choosing to open it.

      -jcr

      --
      The only title of honor that a tyrant can grant is "Enemy of the State."
    3. Re:Agree by Patman64 · · Score: 1

      Yeah, it seems to me this is more of a "The service being offered did not fit our needs, so we have ceased using it.". This is hardly a statement about how horrible walled gardens and sandboxes are. He even says it's a good solution for new Mac-only developers.

    4. Re:Agree by omfgnosis · · Score: 1

      That sidesteps Gatekeeper enforcement of user settings to prevent running apps which are either not signed and-or not from the App Store. It doesn't, as far as I'm aware, disable sandboxing if the app is sandboxed. Those are different things. Sandboxing restricts what data and resources an app has access to, whether it's signed or not, and whether it's from the App Store or not.

    5. Re:Agree by gnasher719 · · Score: 2

      I agree, sandboxing has been a bitch. Should be able to turn it off for apps the user trusts...

      The user can choose to install and run applications that are not sandboxed. Apple just doesn't sell or distribute such apps on the app store. Once an app works sandboxed, there is no point in being able to turn the sandbox off.

      But sandboxing is not only about the user trusting an app. I may trust that an app is not intentionally malicious. That doesn't mean it can't have bugs that could be exploited by a hacker, and at that point sandboxing means that the hacked application is _still_ restricted by the sandbox.

      And as a developer you can (and should) split your app into parts so that the complicated parts that are more likely to be attackable cannot actually do any harm. Like your image reading code that could be hacked by a maliciously designed image file would be sandboxed so that it can't do anything but return valid images, so an attacker would be stuck in a sandbox that can't actually do anything bad.

    6. Re:Agree by BitZtream · · Score: 0

      Mac App Store that removed features such as iCal support, iPhoto integration, and Add-Ons in order to comply with Apple’s Application Guidelines

      Which is funny considering the number of apps on the app store that have iCal support, iPhoto integration, and specifically add ons for other apps (I for one author an add on for mail.app that lives on the app store this very day, and apple has never even acknowledged that plugins exist for mail.app.).

      There isn't a problem, just shitty developers whining because they can't figure out how to do something, no one has bother to give them example code yet that they could copy rather than figure it out for themselves.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  9. He's talking about the new MAC app store by Spy+Handler · · Score: 3, Informative

    not the App Store most people are thinking of (the iphone/ipad one). TF summary is misleading.

    The mobile App store's always been restrictive, and it seems to have done okay... nothing to see here.

    1. Re:He's talking about the new MAC app store by Anonymous Coward · · Score: 0

      There's a Media Access Control App Store?!

    2. Re:He's talking about the new MAC app store by omfgnosis · · Score: 1

      Give Spy Handler the benefit of the doubt; they were using capitalization to emphasize "Mac", so as to distinguish it from the "App Store" (sans Mac) referring to the iOS version.

  10. Uh huh... by Anonymous Coward · · Score: 2, Funny

    According to Arment, the new sandboxing guidelines from Apple are pushing developers away in droves.

    Though nothing in his blog post actually says or even hints at this. But it's fun to pull things out of our ass, eh?

    1. Re:Uh huh... by v1 · · Score: 1

      Though nothing in his blog post actually says or even hints at this. But it's fun to pull things out of our ass, eh?

      I try to check out all the comments before posting a reaction to a summary, to make sure someone else hasn't already raised the point. And you have.

      "This is horrible, everyone hates it!"

      Who hates it? why?

      "Because it's horrible and I hate it!"

      Oh. I see. (clicks "ignore")

      --
      I work for the Department of Redundancy Department.
    2. Re:Uh huh... by Em+Adespoton · · Score: 2

      According to Arment, the new sandboxing guidelines from Apple are pushing developers away in droves.

      Though nothing in his blog post actually says or even hints at this. But it's fun to pull things out of our ass, eh?

      This also misses the points that there are no "new sandboxing guidelines" -- they've been the same since the App Store opened. The only difference is that now they're not just guidelines; they're being enforced -- and that after two extension periods.

  11. As an Apple hater, I disagree. by twocows · · Score: 5, Insightful

    I loathe Apple. They are probably one of the most detestable companies in the technology sector right now. I see them as a modern version of 90s Microsoft.

    But this? I think this is a move in the right direction. The added security benefits sandboxing brings far outweigh any negative consequences a few developers too lazy to implement something Apple's been telling them they need to implement for the better part of a year might experience (at least according to the OS X review a few days ago from Ars Technica). And it's not like these developers have no recourse; as long as they register with Apple or whatever, the default OS setting will allow users to go download those products from the vendor's website.

    There are plenty of reasons to hate Apple. Their push toward better security practices is not one of them.

    1. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 5, Insightful

      Until Apple decide it wants your software's market share and removes your App from the App Store because Apps that compete directly with official Apple products are not allowed.

    2. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      I'm just plan on saying "told you so", repeatedly throughout the coming years.
      It's not gonna be enjoyable.

    3. Re:As an Apple hater, I disagree. by twocows · · Score: 4, Insightful

      That's a reason not to use the App Store in general, not to protest their implementation of sandboxing and adding it as a requirement for App Store apps.

    4. Re:As an Apple hater, I disagree. by robmv · · Score: 1

      Security enhancements should always be welcome. For now they still provide an option to install applications that do not follow the Apple signing requirements and that is good. The problem is when Apple is forbidding APIs to be used if you do not distribute the application on the Mac App Store. I am pretty sure if Google or Microsoft start blocking APIs and make the exclusive to their applications on their store, some people will get mad (with justification)

    5. Re:As an Apple hater, I disagree. by ewieling · · Score: 2, Informative

      I loathe Apple. They are probably one of the most detestable companies in the technology sector right now. I see them as a modern version of 90s Microsoft.

      Apple will not reach Microsoft's level of evil until they have a monopoly. They don't. Not even close. I don't like Apple all that much, but the level of Microsoft's evilness in the 90's cannot be underestimated.

      --
      I really shouldn't have used someone else's email address for this account.
    6. Re:As an Apple hater, I disagree. by Bogtha · · Score: 2

      It's a move in the right direction, but the way Apple are going about it is harming developers and confidence in the App Store unnecessarily.

      I completely agree that sandboxing is a valuable requirement, and regardless of anybody's opinions on Apple's control over the ecosystem, they have used that control to cut out a lot of really shitty practices by software vendors, and this is another example of them using that control to push vendors in the right direction.

      The problem, though, is that the entitlements on offer are half-baked. There's a lot of software that legitimately needs more entitlements, and Apple haven't been responsive in catering to these needs. It wouldn't take much to handle this properly, but Apple are being too aggressive in pushing this forward prematurely. They are dropping the ball on this one, and it has the potential to sabotage the App Store before it's fully established itself.

      --
      Bogtha Bogtha Bogtha
    7. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      Maybe, but my application is one of those that cannot be sandboxed.

      Did you know there is no setting which allows an application to write files in a user selected folder, no you have to ask the user for every file to save manually.
      Which is hard when some of your customers want your application to record audio into 500 mono .wav audio files. Although I believe you can get a temporary exception from Apple, so you can change your application to comply, in other words pull it from the app store.

      Also I want to make screenshots and mail the screenshot,preferences file and log file to me, when the user has a problem he likes me to look at. Of course there is no exception for opening applications like that, so that is a feature that has to be removed from app-store version.

      I am very likely have to pull my application from the app store, but since I do not know the the email addresses of the customers who bought at the app store I can not easily offer an 'upgrade'-path to my non-app-store version.

      Sandboxing is wonderful, but not if there are so few options to tell the sandbox what the application is allowed to do.

    8. Re:As an Apple hater, I disagree. by preaction · · Score: 1

      Some programs are pretty much useless in a sandbox. Should I have to bundle together an editor, source control, and an interpreter in order for those programs to use the same files inside the sandbox? Should I do this for every language I want to develop in using that editor? Without the runtime, the files I'm editing are useless. Perhaps I could get away with just the editor and the source control, using the source control to escape the sandbox. Would Apple close that hole, or reject me from the app store for that reason?

    9. Re:As an Apple hater, I disagree. by gnasher719 · · Score: 4, Insightful

      The problem is when Apple is forbidding APIs to be used if you do not distribute the application on the Mac App Store.

      These are APIs that allow the user to store things on servers that Apple is paying for. So it's not just "using an API", it is "using infrastructure that is paid for by Apple".

    10. Re:As an Apple hater, I disagree. by robmv · · Score: 0

      The user is paying for their iCloud service (if use more than the free quota, if they need more moeny remove the low the free quota), why the developer must be forced to a store for that?. Do Google force developers using Google Drive APIs to use Google Play or Chrome Store? If I pay for Google Apps for domains, do every XMPP messaging client must distribute their app using the Google methods if they will connect to Google Talk server. There is no excuse for Apple blocking iCloud

    11. Re:As an Apple hater, I disagree. by laffer1 · · Score: 1

      Except there are whole classes of programs you can't buy. For instance, many popular disk utilities are not available on the app store or if they are, they only work on removable media. If I want to defragment my boot disk, I have to buy from the vendor directly. Few antivirus applications are available on the app store for the same reason.

      Most games on the app store are crippled too. The online gaming component is disable or similar restrictions are put on the games. Duke Nukem Forever or Rage are examples. You're better off buying games on steam.

      The app store is useful to buy apple apps, but I can't even get Microsoft Office on there. They need to encourage companies to sell products on there not the other way around.

    12. Re:As an Apple hater, I disagree. by dgatwood · · Score: 5, Informative

      Did you know there is no setting which allows an application to write files in a user selected folder, no you have to ask the user for every file to save manually.

      That's not true at all. The standard com.apple.security.files.user-selected.read-write entitlements can handle that very easily. All you have to do is use a standard open dialog to let the user choose a folder, and then write arbitrary crap into that folder or any subfolder within it. Then, save a security-scoped bookmark to that folder if you need to retain access to that folder on future launches. Where things get awkward with that arrangement is when the user copies those files to another machine or restores from a backup. At that point, you'll have to ask the user to open the folder containing the file "foo.wav" or whatever. Then, you can scour the files in there, create security-scoped bookmarks for all of them, and repeat for any other folders full of files.

      A much better solution for that problem is to store each project in a self-contained bundle (a folder with an extension, e.g. a .rtfd file, as supported by TextEdit). If you do that, everything just magically works, because instead of opening a project file, the user is opening a folder that contains everything related to a given project. For obvious reasons, that approach is strongly recommended unless you absolutely have to reference files outside of the project for some reason.

      Also I want to make screenshots and mail the screenshot,preferences file and log file to me, when the user has a problem he likes me to look at.

      That isn't allowed because you aren't allowed to see other apps' windows. It would be a fairly serious security violation if an app could take pictures of other apps that are running and then mail them to the app developer. The same goes for log files that contain data from other applications, preferences files written by other applications, etc. However, there is no reason you can't capture an image of each of your own windows, store a copy of your own log messages in your own file, or send your own preferences file.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    13. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      They are probably one of the most detestable companies in the technology sector right now.

      Why?

      I see them as a modern version of 90s Microsoft.

      How so?

    14. Re:As an Apple hater, I disagree. by jasomill · · Score: 3, Insightful

      Should I have to bundle together an editor, source control, and an interpreter in order for those programs to use the same files inside the sandbox? Should I do this for every language I want to develop in using that editor? ... Would Apple close that hole, or reject me from the app store for that reason?

      No, no, and no. Sandboxed applications have free access, forever, to files and folders you explicitly select, where "forever" can even include subsequent versions of the same app. Many vendors are running away from sandboxing "to improve user experience" in ways that directly conflict with the whole notion of sandboxing: accessing the user's SSH private keys without confirmation, using Apple Events and/or the Accessibility API to control arbitrary third-party applications, and so on. Apple's goal seems to be to maximize the number of applications that can be reasonably sandboxed without undermining the whole idea of sandboxing, using the App Store and iCloud as "carrots", because they're trying to address a problem Microsoft never did: most developers don't give a damn about the mitigation of security vulnerabilities in their applications. It's a hard problem, and discussions like Marco's will ultimately contribute to a better solution, but "give up sandbox requirements" isn't an endgame I'd like to see.

    15. Re:As an Apple hater, I disagree. by Em+Adespoton · · Score: 1

      Instapaper does something that doesn't fit inside a sandbox. It also does something that Safari, as of this week, also does by default.

      Soo... a feature that used to be open season that he profited from is now locked down and integrated into the OS. So he's been forced out of the Apple Store, and his product has been marginalized; all within a month.

      I think that's the bulk of the blog article right there; everything else is fluff.

    16. Re:As an Apple hater, I disagree. by GrahamCox · · Score: 2

      a few developers too lazy to implement something Apple's been telling them they need to implement for the better part of a year

      What, like Apple themselves? Sure, they have sandboxed some of their apps that are fairly self-contained, but the more complex ones CANNOT be sandboxed (i.e. iPhoto, iTunes) because they share data with each other.

      As an Apple developer, we are not "too lazy". Have YOU actually tried making a real-world app work with sandboxing? I have, at very, very great length. I eventually gave up, because our app, which is in fact quite modest, couldn't support of all of its features with sandboxing enabled. I could work around some but some were simply broken and with no possible way to fix them. Luckily our app is already on sale in the App Store and we can still put out updates without being forced into sandboxing for now.

      The other big problem with sandboxing is that, apart from being incomplete and very buggy, there's no way to enable it selectively based on OS version, so while Apple have been slowly addressing some of its issues with each OS .release, there's no way to allow an app to turn on sandboxing based on which version has the necessary support - without that the vast majority of the customer base would be unable to upgrade - their app would simply stop working properly.

      It really is an absolute shambles.

    17. Re:As an Apple hater, I disagree. by Anubis+IV · · Score: 1

      If you read the original blog post, you'll see that he's not talking about lazy developers, but rather the ones that are making advanced utilities and the like that simply are incapable of functioning if they are forced to abide by Apple's sandboxing rules. Even some normal apps are having features stripped from them as a result of the sandboxing, and it's not due to laziness, but rather due to necessity and the fact that those features are simply incapable of being used while sandboxed.

      Don't get me wrong, added security is a great thing, but Marco's entire point was heavily distorted by the summary, and the summary also failed to take note of the later clarification Marco made that offered some more nuance on the points he was trying to make. To say the least, he wasn't coming down on it as hard as the summary suggests, nor was he suggesting that this is a reason to hate Apple or leave them. He was merely pointing out that, for perfectly valid reasons, a number of developers have had to leave the Mac App Store, and that consumers are having more difficulty finding full-features versions of apps in the App Store.

      Speaking personally, I actually just had that happen to me earlier today. I discovered that some of the more advanced features in a piece of software I had downloaded for free from the Mac App Store were unavailable in that version of it. I instead had to download the off-Store version and install that one in order to unlock the more advanced functionality.

    18. Re:As an Apple hater, I disagree. by Kohath · · Score: 2

      They don't need an excuse. "It belongs to us and that's what we decided" is sufficient.

    19. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      Since when? There are multitudes of browsers, document editors, calculators, etc on iOS, at least. Is the Mac App Store really doing that, or are you just saying stuff because it sounds good?

    20. Re:As an Apple hater, I disagree. by thoth · · Score: 2

      Loathe? Detest? For what, building products people are willing to buy?
      They arent in the same solar system of evil as Microsoft in the 90s. They'd need to stifle competition through illegal methods... get some perspective and make your claim AFTER they get sued by the government and are found guilty and criminal.

    21. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      They have patents which Microsoft never really used with the same vigour. This gives them a state granted monopoly. Far more dangerous than a large percentage dominance in the market. Microsoft has lost a lot of that dominance in less time than patents will last.

    22. Re:As an Apple hater, I disagree. by mysidia · · Score: 1

      It's a hard problem, and discussions like Marco's will ultimately contribute to a better solution, but "give up sandbox requirements" isn't an endgame I'd like to see.

      No matter how you put it, ultimately there are apps that have to have exceptions to sandboxing.

      Antivirus scanners need to be able to scan things outside their little sandbox.

      Utilities for mounting a NTFS filesystem, so you can upload files to a USB stick and share with a windows computer, need the raw device access.

      So, yes, absolutely.. Apple should stop the idea of "sandboxing" as a hard requirement for being on the app store.

      They should have a procedure for getting exceptions, presumably a third-party audit to ensure the exception is actually required, and some means to carve out exactly the required exception.

    23. Re:As an Apple hater, I disagree. by Wovel · · Score: 1

      Evernote (from the AppStore). Can still take screenshots of anything.

    24. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      Where things get awkward with that arrangement is when the user copies those files to another machine or restores from a backup. At that point, you'll have to ask the user to open the folder containing the file "foo.wav" or whatever.

      I was thinking about a larger blockquote, but that choice bit above will suffice. "Those who don't understand UNIX are doomed to reinvent it - poorly." How they got to this point from Darwin is beyond me.

    25. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      The users pay for iCloud storage space, why should app developers?

    26. Re:As an Apple hater, I disagree. by shutdown+-p+now · · Score: 1

      One of the links actually gives a specific account of what an app does that sounds like it'd be mighty useful, but is not compatible with the sandbox:

      "Most importantly, we had to create another version of Postbox for the Mac App Store that removed features such as iCal support, iPhoto integration, and Add-Ons in order to comply with Apple’s Application Guidelines"

    27. Re:As an Apple hater, I disagree. by shutdown+-p+now · · Score: 1

      Not a single word in the article is about Instapaper, and he specifically links to another real product that was pulled from the app store because its developers refused to compromise on features they consider important to squeeze it into the sandbox.

    28. Re:As an Apple hater, I disagree. by dgatwood · · Score: 4, Informative

      It's actually pretty straightforward. The UNIX security model sucks. It assumes that attacks come from the outside, and is designed to protect the user from other users on the same system. In the UNIX model, everything run by a particular user has the same rights as the user. In practice, that just isn't a viable security model anymore.

      Consider this scenario: you have a web browser. When everything is working, you trust that the browser is not malicious, so you run it as yourself. Later, you go to a web page and, because of a bug in that browser, somebody is able to execute arbitrary code. Under the UNIX model, that browser can send all your files to a server in Croatia, encrypt them, and extort money from you in exchange for getting your data back.

      The only way to prevent such a scenario in a traditional UNIX permission system is to run each application as a separate user. That might be practical for a power user, but it would be insane for most folks. And if you ever wanted to open that JPEG file that you saved with the web browser, you'd have to go in and either change the owner (Finder running as root is a terrifying thought) or set really scary ACLs. No matter how you cut it, that's not user-friendly.

      A modern security model must be fundamentally built on the principle of distrust. Distrust everything. Any app could potentially become malicious at any time, whether because the app developer put in a backdoor or because somebody exploited a buffer overflow. It is, therefore, the responsibility of the operating system to not only protect the user from other users on the system, but also from flaws in other applications being run by the same user.

      The result is a sandboxing model, in which applications are allowed to open only files that the user has explicitly authorized them to open. Although the user sees a standard file open dialog, when running in a sandbox, the application is not in charge of displaying that dialog. Instead, a system daemon called pboxd (the "powerbox daemon") displays the dialog. When the user chooses to allow that application access to a resource, that daemon then extends the application's sandbox to allow access to that file. In this way, the application has access to exactly the files or folders to which the user has granted it access. No more, no less.

      Such a security model is really the only sane security model you can come up with. By using user intent rather than an arcane set of permissions, the user is able to open files in whatever application the user chooses, trusting the operating system to ensure that those applications do not have access to files that the user has not allowed those applications to open. This significantly reduces the benefits gained from attacking security holes in an application.

      That's not to say that some apps don't need broader access (e.g. Finder), but it is a worthwhile goal to minimize the number of apps with that level of access, as they are the juiciest targets for attack.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    29. Re:As an Apple hater, I disagree. by highacnumber · · Score: 1

      Overestimated?

    30. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      It can. The evil Apple is doing patent-wise is threatening future FRAND patents, licensing patents between competitors.

    31. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      Instead, a system daemon called pboxd (the "powerbox daemon") displays the dialog.

      So attackers then target that daemon as it has system-wide access? Marvellous.

    32. Re:As an Apple hater, I disagree. by tlhIngan · · Score: 3

      The user is paying for their iCloud service (if use more than the free quota, if they need more moeny remove the low the free quota), why the developer must be forced to a store for that?. Do Google force developers using Google Drive APIs to use Google Play or Chrome Store? If I pay for Google Apps for domains, do every XMPP messaging client must distribute their app using the Google methods if they will connect to Google Talk server. There is no excuse for Apple blocking iCloud

      Easy, to prevent abuse and malware spreads.

      First off, developers suck. Yes, that includes you and me. For every well-written to-the-API app, there's dozens of others that take shortcuts and cheat at things, usually in the name of "making release" or "fixing a bug".

      The sandboxing requirement was well known going into the App Store at least over a year ago. All developers knew about the deadline, and it was extended, twice as they weren't ready. Why? Because they didn't have to do it! But now that Apple forced them, they suddenly realize that they need to do it, and fast. It's unfortunately also Business 101 - even if you announce a change years in advance, remind them to the point of nagging, some company with something that's worked fine for all those years suddenly realizes you mean business and has to scramble to meet new requirements. Despite having years to get ready. Very few, if any, will actually try to get ahead of the curve and meet the new requirement ahead of time.

      As for limiting iCloud to App Store Apps - it's probably with sandboxing. Imagine you had a regular app that had a bug and used iCloud. A smart malware writer will exploit your app to infect a user's document stored on iCloud so even if the user wipes their mac, the instant they use the app, they're infected again because of an exploit in your app.

      Try diagnosing THAT as technical support. Sandboxed apps using iLcoud - well the app can get infected, but that infection is confined through the sandbox to that app only.

      Or imagine it's a different file - let's say a specially crafted file using some exploit in libjpeg or other imaging library. If a sandboxed app loaded it, it gets infected, but that infection is confined to that app only. If it was available to all apps, all it would take is a vulnerable one to infect *all* your Macs simultaneously through iCloud.

      The other alternative is to have Apple scan and delete infected files off their servers. But I'm sure that will go over really well with people.

      One final reason is well, everywhere you have the app, you have access to your files via iCloud, since all app stores Apple has are tied to iCloud now. Let's say you buy some nifty editor off the Mac App Store. You go to a new Mac, login and redownload the editor and boom, the files are there. If it was the other way, you'd have to find the editor's website, somehow manage to get the registered copy (hoping it's not machine-locked!) and then get at your files. Less convenient, while the other way puts more work on the developer, the user gets a much better experience.

      As for developers screwing their customers - two sides to the coin. Apple is withholding from developers the IDs of who purchased their apps, probably for the better (given all the hacks and stealing of customer databases, you'll probably fine many developers would have pretty shoddy websites vulnerable to SQL attacks, buffer overflows, plain text customer lists out in the open, etc. Hell, there's probably someone out there who stores their entire customer database as a series of emails on a publicly-accessible IMAP server. (You will easily find that while they can code up wicked stuff for an app, but then fail to take basic security precautions for their website...).

    33. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      I am sure I read all the documentation last year, I didn't remember anything about security-scoped bookmarks. Thank you for the tip I will look into it.
      As for screenshots, preferences and stuff I will need to make something that submits the data to a webpage or something, since you can't launch mail with those files I think.

    34. Re:As an Apple hater, I disagree. by ewieling · · Score: 1

      Correct. I wish slashdot allowed editing posts.

      --
      I really shouldn't have used someone else's email address for this account.
    35. Re:As an Apple hater, I disagree. by Guy+Harris · · Score: 1

      Instead, a system daemon called pboxd (the "powerbox daemon") displays the dialog.

      So attackers then target that daemon as it has system-wide access? Marvellous.

      I don't have a Lion or Mountain Lion system in front of me, but I think that pboxd is a "system daemon" only in the sense that it's a daemon supplied as part of the system, and that it's run as the user, not as root. So attackers could target it, but they wouldn't get root access if they succeeded, they'd just get the same access an un-sandboxed user process would have.

    36. Re:As an Apple hater, I disagree. by Kalriath · · Score: 1

      Correct. But these days malicious software doesn't actually need root access any more. Unsandboxed access is probably "good enough".

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    37. Re:As an Apple hater, I disagree. by Kalriath · · Score: 1

      The app store is useful to buy apple apps, but I can't even get Microsoft Office on there. They need to encourage companies to sell products on there not the other way around.

      You never will. The Behemoths (Microsoft and Adobe) will not sacrifice 30% of their sale price to Apple.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    38. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      Because it sounds good :(

    39. Re:As an Apple hater, I disagree. by jeremyp · · Score: 1

      Except that the features they want are available to a sandboxed app, except possibly iPhoto integration.

      Most of their list of issues seemed to be to do with the limited options for licensing the product e.g. the App Store allows only for free upgrades or full price upgrades.

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
    40. Re:As an Apple hater, I disagree. by dgatwood · · Score: 1

      So attackers then target that daemon as it has system-wide access? Marvellous.

      First, it's running as the user, just outside the sandbox. Second, it has a very small attack surface—all it does is accept a request for either a load dialog or a save dialog—which should make it very difficult to attack. Third, it is not a daemon in the traditional sense. You cannot connect to it except from a process running as the user. Thus, it should not be possible to compromise it until after you have already compromised some other process running as the user.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    41. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      And every single browser on iOS uses the same rendering engine and javascript engine because Apple won't let developers use their own implementations, and worse the third party browsers have to use the old slow javascript engine and not fast newer one Safari uses.

    42. Re:As an Apple hater, I disagree. by dgatwood · · Score: 1

      I am sure I read all the documentation last year, I didn't remember anything about security-scoped bookmarks. Thank you for the tip I will look into it.

      They weren't added until 10.7.3. They added a lot of enhancements to sandboxing in various Lion software updates. If you are basing your opinion of sandboxing on what existed way back at 10.7.0, you probably should go back and read the updated documentation.

      As for screenshots, preferences and stuff I will need to make something that submits the data to a webpage or something, since you can't launch mail with those files I think.

      Possibly correct. That said, launching Mail is probably the wrong way to do it anyway unless you want the user mucking with the message on the way to you. :-D

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    43. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      The only way to prevent such a scenario in a traditional UNIX permission system is to run each application as a separate user.

      Let me introduce you to an interesting filesystem flag called SetGID. Just because you don't know, it doesn't mean there is *no* way of doing access sandboxing. It's not trivial, but it *can* be set up automatically for new users by the system. It will, however, scale poorly.

    44. Re:As an Apple hater, I disagree. by Guy+Harris · · Score: 1

      Correct. But these days malicious software doesn't actually need root access any more. Unsandboxed access is probably "good enough".

      Which means Apple had better have made sure pboxd pretty secure against attack. It's probably easier to make pboxd reasonably secure than to make all their frameworks and all their own apps reasonably secure and ensure that third-party apps are that secure, at least as long as the languages being used for development allow code unfettered read-write access to the writable portion of the address space.

    45. Re:As an Apple hater, I disagree. by Guy+Harris · · Score: 1

      The only way to prevent such a scenario in a traditional UNIX permission system is to run each application as a separate user.

      Let me introduce you to an interesting filesystem flag called SetGID.

      I think he's quite aware of it. However, if the goal is to keep stuff that you run from getting access to files to which you have read access, set-GID doesn't help unless the permission system can say "a process with UID XXX only has access to this file if its group set includes group YYY", and the standard user/group/world permission set doesn't support that:

      $ ls -l /tmp/doesntwork
      ----r--r-- 1 gharris staff 7 Jul 28 14:41 /tmp/doesntwork
      $ id
      uid=XXX(gharris) gid=20(staff) groups=20(staff),...
      $ cat /tmp/doesntwork
      cat: /tmp/doesntwork: Permission denied

      Perhaps it can be done with ACLs; if I remember correctly, the way OS X ACLs work is that the first ACL rule that matches wins, so if you put a "group YYY has read permission" rule in front of "user XXX has no read permission" rule, that might do it. Whether that would count as "[a] really scary [ACL]" is another matter.

    46. Re:As an Apple hater, I disagree. by Guy+Harris · · Score: 1

      The UNIX security model sucks. It assumes that attacks come from the outside, and is designed to protect the user from other users on the same system. In the UNIX model, everything run by a particular user has the same rights as the user. In practice, that just isn't a viable security model anymore.

      The key is "anymore", so it's perhaps better stated as "the UNIX security model is no longer sufficient" - and I'd rephrase that as "the time-sharing security model is no longer sufficient", as that model predates UNIX and continues to exist in some present-day operating systems other than UN*Xes. It was pretty good for machines at that time, but, in a world with lots more application developers, more naive users, and access to the Intertubes being common, it's not so good any more.

    47. Re:As an Apple hater, I disagree. by maxwell+demon · · Score: 1

      Slashdot does allow editing posts. It's just that you have to edit it before you submit.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    48. Re:As an Apple hater, I disagree. by dgatwood · · Score: 1

      ...in a world with lots more application developers, more naive users, and access to the Intertubes being common, it's not so good any more.

      I'm not sure I agree with that. There were always a high percentage of naïve users. I remember the UNIX users of a couple of decades back, and sure, some of us were compiling our own tools and stuff, but 90% of them were just professors running PINE (which had at least a couple of remote security holes over the years). And the larger number of developers actually makes things better, not worse. The more apps that serve a particular purpose, the fewer users that use any one of them, and thus the fewer users that will be affected by an attack on it. And UNIX boxes were almost always networked.

      What's different now is not so much that the security model is no longer adequate, but rather that the target has become juicier, so it is now worth attacking UNIX users where it was not worth bothering with them before. Twenty years ago, if you cracked access to a UNIX box as an ordinary user, you pretty much got the ability to read one person's email, impersonate that person on ytalk, and once in a blue moon, maybe find something slightly interesting, but most of the time, you'd fail. So if you cracked a UNIX box, you tried to get root access because you usually needed to look through dozens or even hundreds of accounts to find anything of value.

      These days, that same ordinary user account is now the sole account on somebody's home computer, and it nets you the user's bank account info, personal files, and the ability to inject code into the user's web browser to let you sniff his or her login passwords. And that user is probably now doing his or her banking online, which wasn't even a possibility twenty years ago. And now instead of a security hole affecting tens or hundreds of thousands of users, it could potentially affect hundreds of millions.

      If anything, the risk of most types of exploit is lower now than twenty years ago because far less code is written in pure C, which reduces the risk of buffer overflows pretty dramatically. The problem is, it only takes one mistake, and because the stakes are so much higher, there are lot more people looking for that one mistake.... :-)

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    49. Re:As an Apple hater, I disagree. by Kalriath · · Score: 1

      Slight correction for you - it's sandboxd which is the golden ticket target - that's the core of the security model. All that attacking the powerbox daemon will do is give you write access to sections of the disk you wouldn't otherwise have. Attacking the sandbox itself gives you free reign.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    50. Re:As an Apple hater, I disagree. by Guy+Harris · · Score: 1

      ...in a world with lots more application developers, more naive users, and access to the Intertubes being common, it's not so good any more.

      I'm not sure I agree with that. There were always a high percentage of naïve users.

      That's only one part of it. If you don't have a lot of malware out there, and you don't have Intertubes access to provide a bigger attack surface, the naive users matter less.

      I remember the UNIX users of a couple of decades back,

      UNIX isn't 20 years old. UNIX is over 40 years old, and the security model is even older, dating back at least to Multics, and possibly earlier (I forget how TOPS-10 handled permissions, for example).

      And the larger number of developers actually makes things better, not worse.

      O RLY?

      The more apps that serve a particular purpose, the fewer users that use any one of them, and thus the fewer users that will be affected by an attack on it.

      And, if the percentage of developers who are malicious is constant (or increases over time), the more developers, the more malicious developers.

      And UNIX boxes were almost always networked.

      O RLY? Not when I started using UNIX. UUCP, for example, didn't show up until V7 in 1979, and most UNIX sites didn't have ARPANET access back then.

      What's different now is not so much that the security model is no longer adequate, but rather that the target has become juicier, so it is now worth attacking UNIX users where it was not worth bothering with them before.

      So are you saying the Multics folks should have anticipated drive-by downloads?

      Twenty years ago

      The UNIX security model wasn't invented 20 years ago, it was invented more than 40 years ago (given that UNIX didn't invent it).

    51. Re:As an Apple hater, I disagree. by Anonymous Coward · · Score: 0

      I suggest you seek therapy. Ranting about hating Apple is juvenile and comparing them to 90's Microsoft shows you now nothing about either Apple or 90's Microsoft.

    52. Re:As an Apple hater, I disagree. by dgatwood · · Score: 1

      UNIX isn't 20 years old. UNIX is over 40 years old...

      That was an arbitrary number, and was not intended to imply that UNIX had only been around for twenty years. The point of that number was to show that naïve users are not a new problem in the UNIX world.

      And, if the percentage of developers who are malicious is constant (or increases over time), the more developers, the more malicious developers.

      True, but protecting against malicious apps isn't the intended purpose of sandboxing. A malicious app, given a choice, would probably not choose to ship as a sandboxed app in the first place.

      Besides, if the percentage of developers who are malicious is constant, the percentage of users who happen to choose the malicious app should at best remain constant. And the more apps you have out there, the harder it will be to come up with a trojan that looks different enough from other apps with great reviews to convince people to try it. That should actually reduce the percentage of people affected by malicious apps. And increasing the number of apps should also decrease the percentage of users successfully attacked by buffer overflow exploits and similar, because of wider technodiversity.

      To the extent that the percentage of developers who are malicious increases over time, that breaks the equation, but such a change is likely to be caused by the targets becoming juicier. :-)

      O RLY? Not when I started using UNIX. UUCP, for example, didn't show up until V7 in 1979, and most UNIX sites didn't have ARPANET access back then.

      Let me restate that more precisely. UNIX boxes being networked is not a recent phenomenon. That said, networking isn't required. The old "Hi, this is Chris from the helpdesk. Could you type a diagnostic command on your terminal for me? Okay. Type rm -rf *" prank dates back as far as I can remember, and is in part caused by a lack of privilege separation between different tasks that the user can perform. :-)

      So are you saying the Multics folks should have anticipated drive-by downloads?

      No, and I'm not saying that the UNIX designers necessarily should have, either. What I'm saying is that the weaknesses were always there; they simply weren't known or fully understood, and they didn't matter all that much because there weren't enough malicious coders looking for them.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

  12. Uh oh... by Anonymous Coward · · Score: 0

    What would Jobs do?

  13. A big fat.. by Anonymous Coward · · Score: 0

    DUH!

    He's just realizing this now?

    It's what I've been saying all along. If you can't install and/or run it without relying on someone else's servers, you don't own it. That's why I NEVER buy anything that uses any kind of online activation, or uses a mandatory downloader to install the program. If any software vendor wants my money, they have to provide me with an offline installer that I can run even on a computer that I have no intention of ever connecting to the internet. If I buy something, I want to know that I'll be able to transfer it later to another device even if the company who sold it to me and all the middle men in between disappear off the face of the earth.

    And yes, that applies to Steam, too.

    1. Re:A big fat.. by Culture20 · · Score: 1

      Am I posting AC in my sleep?

  14. Like Walmart..... by cpu6502 · · Score: 4, Informative

    Apple probably doesn't care. When one merchandiser leaves, another one will gladly take its place.

    --
    My AC stalker: " I personally agree with your posts most of the time, but that won't keep me from modding you troll"
    1. Re:Like Walmart..... by cpu6502 · · Score: 1

      And I doubt the customers will care either. If Walmart stops selling HTC televisions, do people just quit walmart? No they buy whatever brand is available. Same with the Apple Store; people will just buy what they can. So I disagree with the comments below: http://www.marco.org/2012/07/26/not-just-geeks

      BTW instapaper's "read later" doesn't work in Opera.
      Would be nice if he fixed that.

      QUOTE: "My argument was more nuanced: many previously-acceptable apps have been effectively kicked out of the App Store because theyâ(TM)re incompatible with the current implementation of sandboxing, and this hurts the customers of those apps enough that they will lose confidence in buying nontrivial software from the Store in the future. For this reason, I, as a customer, have lost confidence. Furthermore, the increasing number of good, useful apps not permitted in the App Store will prevent it from becoming ubiquitous, therefore harming Apple's presumed long-term goals."

      --
      My AC stalker: " I personally agree with your posts most of the time, but that won't keep me from modding you troll"
    2. Re:Like Walmart..... by PNutts · · Score: 1

      I hope that guy's crazy is sandboxed.

    3. Re:Like Walmart..... by marcosdumay · · Score: 1

      And everybody knows that developers are fungible.

      (But then, we have no evidence that they are living the app stopre.)

    4. Re:Like Walmart..... by Anonymous Coward · · Score: 0

      That, and his blog sucks.

  15. Apple needs to take care of developers by Anonymous Coward · · Score: 0

    This is how it's done: http://www.youtube.com/watch?v=KMU0tzLwhbE

  16. Backwards, more will go to app store by SuperKendall · · Score: 5, Interesting

    As a developer I see what he is saying.

    But as a user the changes only make it MORE likely I would look in the app store first for something. I know something from there will work along with the system security restrictions.

    With more people looking in the app store, the simple truth is more developers will have to service that market somehow or lose users (or at least not grow at the same rate as the mac install base does).

    Apple has already changed some ways in which sandboxing works, to accommodate some application needs. And they will do more of that going forward - but historically Apple implements overly strong security to start with, and then whittles it away as required instead of letting users get used to an overly permissive model.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:Backwards, more will go to app store by Anonymous Coward · · Score: 0

      > But as a user the changes only make it MORE likely I would look in the app store first for something. I know something from there will work along with the system security restrictions.

      Yes, for a standalone application. But there's a whole class of utility software which only exists because it plugs into other software in ways which the app store doesn't allow. (e.g. from TFA: "integrations with iCal, iPhoto, Dropbox, Evernote, and more") As more eyeballs are glued to the store, this stuff will be harder to find.

      The Windows 8 store lets developers put a page up, even if the app isn't store compatible. Seems like a decent compromise.

  17. The problem is... by Anonymous Coward · · Score: 4, Informative

    Developers think "Great, I can release an App Store version... I just need to remove x and y." So they do that, and people buy the App Store version. Then the developer realizes his App Store version now can't do Z, which makes it much harder to keep making in parallel with his native version. So he stops updating the App Store version. App Store customer sees non-App Store version getting updates and gets angry.

    1. Re:The problem is... by Kohath · · Score: 1

      World ends. Because hypothetical customer wants something he doesn't automatically get. Hypothetically.

  18. Yup by Anonymous Coward · · Score: 0

    I've felt that Apple has been doing a good job of alienating developers ever since such ostentatious shit such as demanding that 30/70 pay cut off of any profits that could be construed as an 'In-App Purchase', coercing them to either not do business with their platform, or take their deal up the yahoo. Speaking from my own experience, where I had a voice over IP application for a now-defunct company dropped last year from the store for that reason after working just fantastically for a number of months up until that point. They wanted us to fork over 30 percent of our profits, on a prepaid VOIP service where we accepted shit like liberty reserve & bitcoin, where the only function of the application was to connect a call to the cell phone from the VOIP servers to the phone through an HTTP request which connected the call through an incoming call to the cell phone running the app which made the request (thereby skipping outgoing call minutes/outgoing longdistance rates/etc etc along with DID services and all the other stuff that the company offered). Simply not anywhere near economically feasible, but apple stood their ground that this was what the deal was going to be. Fuck alienating developers - Charging an individual or a company money to open up an app store account and then fucking over them and their customers who enjoyed their services with that kind of shit has left me at the point where I laughed when Steve Jobs died. As an aside, the fact that Apple's computer platforms have never been inherently apt to writing code and creating things (especially now with iPads etc) kind of tells me that they're not just alienating developers, they're also making the whole profession that much more obscurantist in their offerings of it, as some have argued. Can't write a fucking iphone app on a fucking iphone. In fact, I am glad I had mine broken when I took it out camping and had some drunk friend break it while she was using it as our only light with a working battery.

    1. Re:Yup by Anonymous Coward · · Score: 0

      Also, I got sick of people asking "So hows working FOR APPLE?!?" all the time. I still get that fucking question, actually.

    2. Re:Yup by Anonymous Coward · · Score: 0

      What was the app?

  19. Not a "power user" OS anymore. by Anonymous Coward · · Score: 1

    Customers may take the same route (i.e. straight to the exit, without even grabbing their coat), at least for the more empowered users.

    Case in point: I've purchased "Light Compressor" on the AppStore. Simple application to combine multiple exposure pictures to create HDR images. For some reason, the developer decided that Lion was required - why exactly he needs Lion still escape me. Upgrading to (now) Mountain Lion with my 2008 Macbook Pro would need me to reevaluate all the software I use, most probably requiring more upgrades. Sorry, I'm not going to spend tens if not hundreds of euros to be able to use a 3 euros one. Sad thing is, when I paid for it, it was perfectly running with Snow Leopard.

    Plus, now that Apple is turning OSX into a kind of IOS with some desillusions of grandeur, and taking the "we know better what's good for you" route, I personally will leave the platform as soon as Snow Leopard stop working for me and migrate back to Linux. I just wish I'd have not left in the first place.

    Note that I think Apple and Microsoft are completely out of touch with their customer: if people need "simple" computers, they'll go with tablets these days. But there's still a lot of people who need to _work_, and for those, oversimplifying the laptop/desktop computer is counter-productive.

    1. Re:Not a "power user" OS anymore. by Anonymous Coward · · Score: 0

      I do all of my work on a Mac and I've never needed to install anything from the App Store.

    2. Re:Not a "power user" OS anymore. by Anonymous Coward · · Score: 0

      I upgraded my wife's 2008 MacBook to Lion with with no issues. In regard to Mountain Lion the upgrades I've seen are required to take advantage of ML's new feature. The old versions work just fine. Don't blame Apple for the decisions of cheap app developers. There's plenty of cheap apps in the app store that do the same thing.

  20. Cool story by Anonymous Coward · · Score: 0

    Now go tell that to the unaware masses who will still be using the appstore.

  21. How will 'the halo effect' come into play? by Voyager529 · · Score: 4, Insightful

    Many, MANY people buy Macs because they believe that they are better/more stable/more secure than the Windows machines they've used for the past decade. Whether they are or are not is an endless Slashdot debate that is completely tangential to my point, because what's at question here is the perception, not the reality.

    If people perceive the Mac to be the stable part, software that doesn't work will likely be blamed on the developer, not Apple. To them, a sandbox is a place young children play in, not a computer security model. A developer trying to explain this to someone who truly doesn't understand the security model will make himself look foolish to the customer, not enlighten the customer.

    The App Store will still be used by many Mac users in the same way Origin is used by EA customers. Few (if any) EA customers desired Origin, it's just necessary for Battlefield 3, Mass Effect 3, and The Sims. Similarly, even if many Apple developers ditch the App Store, the fact that Final Cut Studio, Logic, and Aperture are available through it will keep a huge demographic begrudgingly using it. Adobe is probably the one company who can likely keep a working trigger finger on Apple preventing conventional software installations, but their pushing their 'Creative Cloud' model may weaken their grip on said trigger. Ableton and Serato may be in a position to help pick up the slack a bit, but they definitely don't have the same level of clout.

    Finally, long time Mac incumbents may be wary of the Mac App Store, but newcomers who love their iPhone/iPod/iPad may be more inclined to start at the App Store since that's "where software comes from". It's part of the vertical solution that they feel they bought from Apple. The question will be whether developer A's FOO_APP skiddishness in being included in the App Store will be the golden opportunity for similarly-functioning FRA_APP to eat its lunch. Again, Adobe may be able to keep itself afloat with selling stuff through adobe.com/journeyed/cdw/staples, but searching the App Store through functionality puts developers on much more even levels for those that would be affected by the sandboxing and not having a legal team at their disposal to go RIAA on their posteriors.

    1. Re:How will 'the halo effect' come into play? by SplashMyBandit · · Score: 3, Interesting

      I just upgraded my MacBook Pro from OS X 10.7.4 Lion to 10.8 Mountain Lion. Unfortunately this change brought a new version of OpenGL (great!) but Apple removed the PBuffers they had deprecated some time back. That broke the software I've been working (using th JoGL OpenGL bindings). While on one hand you can argue that Apple deprecated PBuffers on their platform so tough luck to me. On the other hand both AMD on Windows and Ubuntu Linux still have working PBuffer implementations and my software still works on those platforms.

      As a developer it makes me a bit unhappy Apple brought in a lot of Cloud stuff (that I personally have zero interest in) while removing small but useful features that are actually widely used. Backwards compatibility matters a lot, which is one of the great strengths of Windows but Apple are less keen on it. As a developer (the point of this article) it now means that until the JoGL library catches up OS X has moved from a first-class target for my game to second class behind Linux and Windows (where I know the development effort won't be slowed by fairly needless breaking changes). This is because I can't guarantee that the effort I make to get things going again on OS X won't be nullified with further (IMHO unnecessarily strict) changes as new OS X versions are released on their yearly cycle. Sure, I have the technical chops to patch JoGL myself, but it is something I don't have to do for Windows and Linux, and is a diversion of effort for me actually *getting the important stuff done*.

      nb: I must be a luddite. I'd much rather get my software directly from the vendor rather than the straightjacket of the App Store. I just know getting stuf through the App Store will be problematic whenever Apple decides that it is in their interest (not mine) to replace the App Store with something else. All technology changes, eventually, but Apple's timescale for change is probably much faster than mine since I just want to get stuff done => future trouble, so I avoid using App Store where I have alternatives.

  22. New sand boxing guidelines? by hsmith · · Score: 5, Informative

    Apple hinted to sandboxing being mandatory at WWDC11, they announced it would happen later that year, then forced everyone to a few months ago. So, where does this "new" come from exactly?

    1. Re:New sand boxing guidelines? by Mabhatter · · Score: 1

      Because the Sandbox is including things Apple WANTS to do for itself. Things are added to the sandbox because Apple wants to KICK SOMEBODY OUT to eat their lunch, and not just technical reasons.

    2. Re:New sand boxing guidelines? by Anonymous Coward · · Score: 0

      What a complete load of shit. Apple is not kicking anybody out to eat their lunch.

      When Apple adds something to the sandbox, it's a sign they're making developers' lives easier, not harder! See, when they do that, they're adding new entitlements (capabilities which a developer may request to use). You appear to believe they're adding new restrictions, which betrays a comical lack of understanding of what sandboxing is about on your part.

      This is at least the second or third post I've seen from you where you assert (without giving any justification) that Apple's sandboxing technology is some kind of super evil plot to backstab their developers. The thing is, that's just dumb. Say a dev sells 1000 copies of an app through the App Store at $1 each. The developer gets $700, Apple gets $300. If Apple forces that guy out of the App Store, Apple gets $0 instead of $300. If Apple also "eats their lunch" by writing their own version of the same thing and integrating it into the next OS X release, Apple still gets $0, but they have to pay their own people to develop test and debug the app, and that puts them tens of thousands of dollars (at minimum) in the red.

      Hint: they will only ever do this if it's an important enough app that they think it will sell noticeably more computers to have it on every one.

      Hint #2: they do not need to kick the developer off the app store to "eat their lunch".

      Hint #3: even if you assume they want to boot someone, why the fuck would they ever do it by messing with the sandbox, which affects all developers? They control the app store, you know! They don't have to use the stupidest way possible to get rid of a specific app or developer they don't like.

      It's like you sincerely believe Apple is a moustache-twirling James Bond movie villain who does stupid shit which is obviously doomed to backfire just because the villain is Evil with a capital E. The real world is not like the movies, kid.

  23. just finding this out now by slashmydots · · Score: 2

    They're just realizing this now? A walled garden controlled by one single company that gives you zero control whatsoever might maybe have some undesirable results? Did they think Apple wasn't in complete control when they bought their iOS device or something?

    1. Re:just finding this out now by Guy+Harris · · Score: 1

      They're just realizing this now? A walled garden controlled by one single company that gives you zero control whatsoever might maybe have some undesirable results? Did they think Apple wasn't in complete control when they bought their iOS device or something?

      Who said anything about iOS here? Hint: the answer is not "Marco Arment", give that TFA is titled "The Mac App Store’s future of irrelevance" (emphasis mine). You did read TFA before commenting, right? (If you trusted the /. summary and didn't RTFA, the phrase that comes to mind is "you must be new here"; summaries don't always do TFA justice, hence "RTFA".)

  24. What I've seen by jbolden · · Score: 4, Interesting

    What I've seen is that many apps are starting to have 2 versions:

    a) The internet version
    -- designed the way the developer wants
    -- paid upgrades
    -- weak or weaker tie to iOS version

    b) The app store version
    -- designed the way Apple wants
    -- free upgrades (or rarely 100% rebuy upgrades)
    -- strong tie to the iOS version via. iCloud

    That's a really interesting choice. So far I've always gone for the internet version because the app store worries me. I like the idea of iCloud integration, but most of what I want I could get though dropbox and sym/hard links. I could get the update management the more traditions way (http://www.macupdate.com/desktop/) but frankly all the apps check by themselves at this point mostly.

    But I don't know the App store is "in trouble". I think there is likely to be a fork in what you get where. The App store might have lots of inexpensive simple applications, free demos, desktop support for phone apps and other apps that are single purpose while the retail side focus on the $20 on up apps which are more versatile. I don't think it is good that the market is forking creating two software ecosystems with different tastes.

    1. Re:What I've seen by Anonymous Coward · · Score: 0

      via. iCloud

      "Via" is not an abbreviation: it is Latin an the root of the English word "way".

      Putting a dot in "via iCloud" is wrong.

    2. Re:What I've seen by Anonymous Coward · · Score: 0

      Do you have an example? I'd like to see this delivery bifurcation.

    3. Re:What I've seen by jbolden · · Score: 1

      Voodpad by flyingmeat is a great example.

      Omni's software particularly Omni Focus.

  25. Only on Slashdot by Starteck81 · · Score: 5, Insightful

    I love that people on here bitch endlessly about how insecure OSes are. Then Apple makes a move to require devs to code in a more secure manner, result? They freak out. Did I miss anything?

    --
    "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed H
    1. Re:Only on Slashdot by epyT-R · · Score: 0

      well if the os was secure, apple wouldn't pitch this additional layer in the first place..

    2. Re:Only on Slashdot by Kergan · · Score: 2, Interesting

      +1000. Arment's comments and the OP's summary are utter bull crap.

      Moreover this is a one-time thing, one long in the making, postponed several times in the past two years or so, and Arment knows it more than any other -- being the author of an iOS app.

      There's really nothing to see here. Consumers are basically told: "We're improving security by requiring stuff in the app store; we're dropping apps that aren't secure enough by our standards as a consequence." Period, end of story. Move along, nothing to see.

    3. Re:Only on Slashdot by AzN1337c0d3r · · Score: 0

      Yeah, it's the dick move that they made to require devs to code in a more secure manner. If the model wa so much better, then everyone should be heads over heels to adopt it. But it's not.

    4. Re:Only on Slashdot by sl3xd · · Score: 2

      You apparently aren't familiar with the practice of defense in depth...

      No OS is secure; not even OpenBSD, where they painstakingly audit every line of code.

      Fort Knox's security isn't just because of the vaults in the gold depository - it's the army base, filled with soldiers, each of which is a layer of security (some good, some not so great), as well as an armored battalion that surrounds the depository.

      Apple's sandbox is (surprise, surprise) an implementation of mandatory access control - like SELinux or AppArmor. The difference is that Apple holds the keys, because, quite honestly, nearly all users are horrible at determining what kind of permissions are 'safe' for any given program. (Just look at Android - where programs typically have to ask for access permissions, and users blindly give away far more access than is required to work).

      While it's a bit of a sore point for those of us who can actually use mandatory access control, it's important to realize that MAC shouldn't be a toy that only the most skillful users can employ. This is a step that brings it to everybody.

      --
      -- Sometimes you have to turn the lights off in order to see.
    5. Re:Only on Slashdot by drinkypoo · · Score: 1

      While it's a bit of a sore point for those of us who can actually use mandatory access control, it's important to realize that MAC shouldn't be a toy that only the most skillful users can employ. This is a step that brings it to everybody.

      We've had AppArmor for a long time. These days Ubuntu actually delivers a bunch of profiles, too. Cups won't load if apparmor is misconfigured, for example, but there's actually a bunch of them now where I remember it used to pretty much just be cups

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:Only on Slashdot by epyT-R · · Score: 1

      I'm well aware of it in fact. I just don't buy into ignorance-is-bliss for users. Nor do I buy into apple's excuses that claim to justify removing more and more control from them for the sake of security when it's really about institutionalized control freakery intersecting with profit motive. The power you say osx (and by extension, all real desktop systems) has is directly derived from having absolute control when desired. when this is taken away, the power isn't being brought to these people because they had it already, instead, it's being taken away.

      It is possible to set up sane defaults that protect most of the system and still let users do as they wish with their own file structures. the stuff being piled on with 10.7 and 10.8 goes much further than that. The basic unix security model that's been around for ages is good enough balance between usability and security. extra sandboxing of user binaries doesn't really solve the problem because, like the os, it could have vulnerabilities too. however, it does make it harder for a user to get a binary from someone on the net and run it willingly. of course, apple (and microsoft, and google and anyone who wants control) do want this for obvious reasons.

      I find it odd when supposed experts here proclaim stuff like this because the people apple et al are looking to control are not the users, because they have them controlled already. they want to control YOU, the developers.

    7. Re:Only on Slashdot by Anonymous Coward · · Score: 0

      I'm well aware of it in fact. I just don't buy into ignorance-is-bliss for users. Nor do I buy into apple's excuses that claim to justify removing more and more control from them for the sake of security when it's really about institutionalized control freakery intersecting with profit motive. The power you say osx (and by extension, all real desktop systems) has is directly derived from having absolute control when desired. when this is taken away, the power isn't being brought to these people because they had it already, instead, it's being taken away.

      The funny thing about you saying this is that users of OS X still have absolute control.

      It is possible to set up sane defaults that protect most of the system and still let users do as they wish with their own file structures. the stuff being piled on with 10.7 and 10.8 goes much further than that. The basic unix security model that's been around for ages is good enough balance between usability and security.

      Well, now we know you're an idiot.

      The traditional UNIX security model was designed to solve the problem of how to protect the users of a multiuser big-iron machine from one another, in an environment where it could safely be assumed that nobody (and no code) was truly malicious. (Because everyone allowed access to the machines was trusted.)

      That security environment has essentially nothing in common with today's. Most of the computers which need protecting have exactly one user account. If that user runs Firefox and inadvertently browses to a site hosting an unpatched remote exploit, the attackers win. Sure they might not be able to get root, but do they care? No. Not when their goal is to sniff passwords typed into websites, or to steal financial data, Social Security numbers, addresses, contacts, or whatever. Not if they're out to create a botnet. Much of today's malware simply doesn't need to bypass UNIX security to get its job done.

      extra sandboxing of user binaries doesn't really solve the problem because, like the os, it could have vulnerabilities too.

      Sandboxing is enforced by the OS, you dunce. And that thing you typed there is an idiot's argument. Fucking everything can have vulnerabilities. Should we just throw our hands up and say "welp, no matter what we write, it might be flawed, so let's just not do anything!"?

      No, we shouldn't. Instead we should figure out how to contain the problem, make it easier to solve. That's what sandboxing is about. It uses a small amount of simple and extremely heavily audited code to reduce the damage that higher level application software (which is much harder to fully audit due to complexity and size) can do when it is compromised. That is a real gain. Can anybody reduce the probability of vulnerabilities in sandboxing code to 0%? No, of course not. Can they get a lot closer to 0% than, say, WebKit, with its 1.3 million lines of C++ code excluding comments and whitespace? OF COURSE THEY CAN. You know how many Mac applications use WebKit these days?

      however, it does make it harder for a user to get a binary from someone on the net and run it willingly.

      No, as a matter of fact, it doesn't do that at all. The only thing which makes it harder to run a random binary from the 'Net in OS X 10.8 is code signing, not sandboxing. I realize you aren't very clear on all this security stuff, but those two things are not the same thing.

      Also, we're not talking about a great deal of "hard". Most developers already started signing their code months before 10.8 hit (or already were, if they were distributing via the App Store). As for unsigned apps, users can whitelist one merely by right clicking it and opening it from the contextual menu instead of double clicking. Or, if they want no protection under any circumstances, they can go into the system's Security preference pane and click one radio button to tel

  26. 1990s Apple All Over Again by EmagGeek · · Score: 0

    This same thing happened the last time Steve Jobs left. The company destroyed itself from within with one bad business decision after another.

    1. Re:1990s Apple All Over Again by Guy+Harris · · Score: 1

      This same thing happened the last time Steve Jobs left. The company destroyed itself from within with one bad business decision after another.

      As far as I know, the decisions in question were made when Jobs was still alive and in a position to be consulted, although he might've been too ill to say "no" vigorously enough if he really though the Mac App Store restrictions were a bad idea.

    2. Re:1990s Apple All Over Again by Anonymous Coward · · Score: 0

      See, here's the thing about dictators like Steve Jobs. Everyone follows along as long as he is in a position of strength. The moment there is weakness, other start to jockey for position in the eventual demise, and start doing their own thing.

      A well Steve Jobs doesn't approve of iPhone 4s... or "the new iPad," or any other product that is just a slightly changed version of the last - in a big cash grab.

      Steve Jobs wanted nothing less than revolution in each product release, and he didn't get that for the last 3 years he was there.

    3. Re:1990s Apple All Over Again by Guy+Harris · · Score: 1

      Steve Jobs wanted nothing less than revolution in each product release, and he didn't get that for the last 3 years he was there.

      And he did get it prior to 2009? (Note that Snow Leopard development started before 2009 and the decision to make it a mostly clean-up-the-innards release was made before 2009. As for the "he didn't get that for the last 3 years he was there", presumably you're not counting the no-spinning-media-available versions of the MacBook Air and MacBook Pro, as the hard drive option for the MacBook Air was, at least if the Wikipedia page is to be believed, dropped in the Late 2010 MacBook Air.)

  27. Marco may have a point by 93+Escort+Wagon · · Score: 5, Interesting

    Problem is, I read the linked post and can't tell if he's right or wrong. He refers to developers leaving, he refers to customers being burnt, he refers to sandboxing exclusions... but he doesn't give a single example to illustrate his point!

    So what exactly are you talking about, Marco Arment?

    --
    #DeleteChrome
    1. Re:Marco may have a point by Kohath · · Score: 2

      Without more specifics, it's just random internet whining.

    2. Re:Marco may have a point by Anonymous Coward · · Score: 0

      The developer cannot really say what his application can do, for example an application cannot write into a file (unless they are in the Document, Music, Video, Pictures folders in the home directory), unless the user explicitly saves each and every file (The standard Open File Dialogue box API opens up the sandbox). That is not going to work when a user wants the application to create a few hundred large files on an external disk.

    3. Re:Marco may have a point by larry+bagina · · Score: 1
      here is an example:

      Notes for the App Store version of Acorn which is now sandboxed:
      The magic Acorn uses to automatically change the file type popup as you type in the Save sheet no longer works, for your security.
      Using JSTalk to open up images that have not been recently opened will fail.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    4. Re:Marco may have a point by ashpool7 · · Score: 2

      Developers leaving:
      Postbox (in linked article)
      Clipstart
      TextExpander
      and more he didn't list because he didn't think providing anything beyond Postbox was necessary if you've a small developer paying attention in this space. I think he listed some more on his podcast.

      Customers being burnt:
      Himself, and anyone else who bought Postbox from the Mac App Store

      Sandboxing exclusions:
      If you have to have these enumerated, then you aren't the target audience. This is a blog post for developers, not a persuasive news article. The audience will believe/not believe the article based on their own experiences which are not enumerated, but frequently exist ephemerally over twitter and buried small developer blog posts. If you need to have this "sold" to you, then don't worry about it. Solid enough facts for you will bear out in time. This is more prognostication based on developer perspectives.

    5. Re:Marco may have a point by Mabhatter · · Score: 2

      The best example is Growl. They were an open source project for notifications developers needed. They saw Apple building the App Store and buttoned ( and closed) up their project to be a "team player" for the Apple team. The whole saga of the App Store, then the Sandoxing, then Apple copying some of the features.

      Now they're stuck in a place where they can release a version on the App Store but it is so narrow that it doesnt get many more features than the notifications built into Mtn lion. Non-app store apps can't use the app store version of Growl because Growl is sandboxed. The non-app store version of Growl can see the non-Sandbox apps, but can't be sent notifications from App Store apps. Basically BOTH versions of the App got knicked and there's nothing the Dev can do.

    6. Re:Marco may have a point by Kalriath · · Score: 1

      What exactly are you talking about? There is no non App-Store version of Growl (barring the "build it yourself" version - and boy is that a bitch to do). And the App Store version is shipped with an XPC which allows other apps to talk to it fine.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  28. Will Apple's own "apps" run in their sandbox? by Animats · · Score: 4, Interesting

    Will iTunes run in the "sandbox"? QuickTime? Safari? Keynote? Numbers? FinalCut "Pro"?

    1. Re:Will Apple's own "apps" run in their sandbox? by Anonymous Coward · · Score: 0

      They already do.

    2. Re:Will Apple's own "apps" run in their sandbox? by iluvcapra · · Score: 4, Informative

      A lot of those do. Mail does, the mothership process of Safari does not, but it's "Web Content" processes, the ones that present URLs, do. Quicktime Player does. Facetime and the Reminders app do, the Calendar does not, TextEdit does, the productivity apps don't -- it's pretty much hit or miss, I don't think there's any agenda to it, they just update the apps when they get around to it. I know they'd rather have most of their user-facing apps in a sandbox, so they can't be used as an exploitable surface to their underlying services (the camera API, the filesystem, the sloppy blob that is Quicktime...). Several OS processes run in a sandbox as well, like the metadata indexer and the pasteboard daemon, because they have to crunch through gobs of roudy and arbitrary data and are rather intimate with the underlying system.

      But the sandbox and entitlements are about maintaining a chain of trust. If you don't trust the developer, in this case the organization known as Apple Inc, you shouldn't be running anything they make, starting with their OS and hardware, so the question is sorta mute.

      --
      Don't blame me, I voted for Baltar.
    3. Re:Will Apple's own "apps" run in their sandbox? by Anonymous Coward · · Score: 0

      *moot

    4. Re:Will Apple's own "apps" run in their sandbox? by Anonymous Coward · · Score: 0

      Final Cut "Pro" no longer exists. It's now Final Cut X, which is a souped up version of iMovie. Apple has abandoned anything having to do with the 'pro' market for the much more lucrative consumer market.

    5. Re:Will Apple's own "apps" run in their sandbox? by Guy+Harris · · Score: 1

      Final Cut "Pro" no longer exists. It's now Final Cut X, which is a souped up version of iMovie. Apple has abandoned anything having to do with the 'pro' market for the much more lucrative consumer market.

      I think that's why the person to whom you're responding put "Pro" in quotes.

  29. Cynicism wins, again. by billcopc · · Score: 4, Insightful

    As a newcomer to the Mac, I was not at all interested in the App Store. Maybe I'm too cynical, but goddamn it, I'm proven right too often to change my ways. The App Store does not solve any existing problems for me, as a user. If I can find some app in their, then I could have Googled for the author's web site just as easily. I actually prefer apps that self-update, rather than having to open the inflexible App Store client. I don't need a 3rd party getting between me and the developer, isn't that the whole point of a global network ? We don't need no stinkin' middlemen!

    Another peeve is how their delivery method makes it difficult to back up the installation files. I don't want to redownload the dumb thing every time I set up a test box, or follow their annual OS upgrades (from scratch - fuck inline updates!) For regular users, I'm sure the experience is seamless, but as soon as you start messing in a terminal, the messy parts become painfully apparent. It's kind of like that last bit in Portal, where you break out of the test area and run around the broken-down maintenance hallways.

    It's a fine model for the iPhone/iPad, but desktop/laptop computers have a long legacy that predates this sort of integration and far greater diversity in how people use them. Tell me how to use my computer and I'll tell your company to go fuck itself.

    --
    -Billco, Fnarg.com
    1. Re:Cynicism wins, again. by Anonymous Coward · · Score: 0

      Tell me how to use my computer and I'll tell your company to go fuck itself.

      if you believe that for a second.. you wouldn't have bought a mac

    2. Re:Cynicism wins, again. by iluvcapra · · Score: 1

      The App Store does not solve any existing problems for me, as a user.

      It's meant to solve Apple's and Apple developers' problems, not yours -- it's more reliable, less crackable, and cheaper (up front) than eSellerate or Kagi.

      Name one thing in the terminal that's "messy," as opposed to merely "different" from the way Linux, IRIX or SunOS works. All of those look pretty "messy" in the terminal, if you've only used one of the others.

      --
      Don't blame me, I voted for Baltar.
    3. Re:Cynicism wins, again. by Anonymous Coward · · Score: 0

      if you want buy swtor credits ,you must go to http://www.oscargamer.com/Show_game.asp?gameid=81 .of have discount.

    4. Re:Cynicism wins, again. by am+2k · · Score: 2

      Another peeve is how their delivery method makes it difficult to back up the installation files.

      Uh, just copy the applications from /Applications to somewhere else? Mac App Store apps aren't allowed to ship with anything else than what's lying there.

    5. Re:Cynicism wins, again. by Guy+Harris · · Score: 1

      Name one thing in the terminal that's "messy," as opposed to merely "different" from the way Linux, IRIX or SunOS works. All of those look pretty "messy" in the terminal, if you've only used one of the others.

      Presumably you're referring to

      Another peeve is how their delivery method makes it difficult to back up the installation files. I don't want to redownload the dumb thing every time I set up a test box, or follow their annual OS upgrades (from scratch - fuck inline updates!) For regular users, I'm sure the experience is seamless, but as soon as you start messing in a terminal, the messy parts become painfully apparent.

      which isn't saying "playing around in the terminal is messy" (much less "messier than any other UN*X"), it's specifically referring to installing Mac App Store apps. I'm guessing he's saying "trying to back up the installation files from the terminal is messy" or "trying to install Mac App Store apps on a test box, from the terminal, is messy" or something such as that.

    6. Re:Cynicism wins, again. by billcopc · · Score: 1

      Wasn't my choice. I got it to do IOS app development for work. That said, I think the hardware is great, but the software is absolute rubbish.

      Frankly, if I weren't developing mobile apps, I'd wipe the damned thing and put Linux on it like my previous laptop. If they keep backing users into a corner, I just might do that and run their nerfed OS in a virtual machine - far from ideal, but if that's the only way I can pay the bills without going postal, then so be it.

      --
      -Billco, Fnarg.com
  30. I'm pretty much done with the iPhone period. by Nexion · · Score: 2

    I've had the iPhone since shortly after they first introduced it to the market. In that time I purchased many apps, but few paid apps have failed to disappoint. Making things worse Apple allows developers to convert a 10$ app into a "free" app with in game purchases. Particularly disappointing was Oregon Trail. The only thing I found appealing on early Apple computers (I had a PC so I was spoiled) when I found them in my school. I payed almost 10$ for that iPhone app, and it was worth it when I bought it as it was VERY close to the original, as I remembered it. Greedily the developer converted my paid app to a "free" one and completely ruined the game adding content not in the original to prompt users to pay for in game items that shouldn't have even been there. Apple then removes an app from the store that puts a spotlight on shady apps.

    Apple, IMHO, isn't very customer oriented. Well, unless the customer is other businesses and we are the product.

    1. Re:I'm pretty much done with the iPhone period. by Anonymous Coward · · Score: 0

      That sort of thing actually happens a lot more on Android because their users are less likely to purchase apps. You also can't blame anyone but the app developer for doing crappy things like that. They should have simply released an ad-supported "lite" version, and kept the paid app separate. They probably couldn't figure out how to build both off the same codebase and didn't want to keep merging changes across the two versions.

    2. Re:I'm pretty much done with the iPhone period. by Guy+Harris · · Score: 1

      I've had the iPhone

      Wrong App Store. He's complaining about the Mac App Store, not the iOS App Store.

    3. Re:I'm pretty much done with the iPhone period. by Nexion · · Score: 1

      True, and if I did get a droid to replace my iPhone I would likely not buy apps anymore. Mostly due to my perception that android apps are malware infested, almost to a majority.

      I think I'll go back to my phone being mostly just a phone with a few built in apps from a trusted (ha ha) provider. It is somewhat sad you you see Google as a "trusted provider".

    4. Re:I'm pretty much done with the iPhone period. by Nexion · · Score: 1

      I think we need to switch to fostering relationships with trustworthy companies and pay for their software, as I do on the PC. I know this is what OP was say'n and that much I can agree with completely.

  31. The main problem and simple solution by rabtech · · Score: 4, Insightful

    Right now the Mac app store makes no distinction between system/developer utilities and regular consumer applications. As a result, the list of available entitlements are too narrow. Regular users are baffled by the file system and getting it out of their faces is a great idea. Locking down apps is also good from a security perspective for most apps and users.

    Apple just needs to make a special more rigorous review process for these sorts of apps and only allow those apps to request admin access or touch the file system outside the sandbox. In fact only the Developer and Utility categories need allow this sort of thing.

    On a related note, Apple needs something like Windows' contracts so apps can specify the types of data they can provide or accept and let the system manage the interaction. This gives a safe clean way for apps to share data... The primary drawback of Apple's current "share nothing" model.

    --
    Natural != (nontoxic || beneficial)
    1. Re:The main problem and simple solution by Anonymous Coward · · Score: 0

      Regular users are not baffled by the filesystem. It's very simple and very straightforward. If a pre-schooler can 'get it', like my kid did, anyone with any kind of normal mental capacity should also be able to get it. By high-school, or 14, they should be learning to program the computer, but nah, they're taught to use MS Office instead. Something's gotta give, because a large part of our society is crazy-lazy and mentally retarded because of the laziness.

  32. Sandboxing? Some background please? by Stiletto · · Score: 1, Insightful

    He seems to be butthurt over something called "Sandboxing," but throughout his entire rant, he fails to actually explain to his readers what this Sandboxing thing is and how it affects developers. All he offers is some jargon about "incompatibility with the current set of sandboxing entitlements" whatever the heck that means.

    He might as well be ranting over Apple's "leafbowl" restrictions or their policy of "chicken frying" developers. Without some background, who knows what he's talking about with his jargon?

    1. Re:Sandboxing? Some background please? by larry+bagina · · Score: 3, Insightful

      Sandboxing is a standard security term. And it's a fairly stupid one at that. It's more like you're in prison. But the prison warden doesn't want you to talk with other prisoners and plan a riot, so you're put in solitary confinement and there's limited input/output (food through a hole, mail is censored, talk to your lawyer once a week, etc). That's sandboxing. (I guess whoever came up with the term had a bad childhood that involved bing locked in a room with sand on the floor). A normal app can read/write to any file anywhere (assuming appropriate permission). A sandboxed app can only read/write files with explicit user permission (open/save dialog or dragging the file icon). For many applications, that's fine. But it doesn't play well with a lot of utilities or power tools. And some standard apps can't implement advanced features since they no longer have permission to do that.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    2. Re:Sandboxing? Some background please? by shutdown+-p+now · · Score: 2

      If you're reading Slashdot, you're expected to know what "sandboxing" is in general, or at least be able to look it up on Wikipedia etc. And the guy's blog is obviously meant for readers of that blog and should be taken in context, which is OS X software development.

    3. Re:Sandboxing? Some background please? by Guy+Harris · · Score: 1

      Sandboxing is a standard security term. And it's a fairly stupid one at that. It's more like you're in prison. But the prison warden doesn't want you to talk with other prisoners and plan a riot, so you're put in solitary confinement and there's limited input/output (food through a hole, mail is censored, talk to your lawyer once a week, etc). That's sandboxing. (I guess whoever came up with the term had a bad childhood that involved bing locked in a room with sand on the floor).

      The rationale for the term is that each app is given a "sandbox" (note that the article title isn't "Sandbox", and says "A sandpit (Commonwealth countries) or sandbox (US/Canada) is a low, wide container or shallow depression filled with sand in which children can play."; if it's a term specific to English-speaking North American, that could be part of the problem here) in which it can play without messing up anything outside the sandbox. (

      And, yes, there's a Wikipedia page for the technical use of the term.)

  33. NOT ABOUT iOS by mj1856 · · Score: 3, Informative

    The summary is misleading. The article is about the MAC app store for desktop applications. Was anyone else left scratching their heads about how the heck they would deploy iPhone apps to the public without the app store?

    1. Re:NOT ABOUT iOS by Anonymous Coward · · Score: 0

      Yeah, thanks for that clarification... I'm an iOS dev and was scratching my head wondering what I change I could possibly have missed from the latest SDK... Took scrolling half-way down before I overcome the poorly written summary...

      Wonder what percent of app store business is Mac vs iOS??

  34. I believe we'll fly ourselves, thank you!! by Anonymous Coward · · Score: 0

    >> developers are "leaving in drones"

    Yeah .. that's just the thing as somebody already pointed out developers are leaving in DROVES not drones ...
    because you see drones are exactly the kind of thing we hate. Sitting in a drone remote controlled by someone
    means we're not at the stick, somebody else is. Just like with the app store. It's their app store, we are meant to
    be their tenants. And those digital landlords may have an agenda, they may want to cut into our
    profits or squeeze us out of the market completely in the end. They are put in a position where they can tell us what to do
    and what not to do and we have no choice but to comply -- or else they crash the plane.

    Thank you, we'll fly ourselves! We've been selling software for decades before Apple, Google or (Microsoft) came along
    with their app stores.

    1. Re:I believe we'll fly ourselves, thank you!! by Desler · · Score: 1, Flamebait

      *yawn* Yes, I made a spelling mistake. OMG let's alert the New York Times! You knew exactly what I meant.

  35. Big trouble . . . by RazorSharp · · Score: 1

    Man, what's Apple going to do when all these developers leave them to go develop applications to put in Ubuntu's repository and the mobile Windows 8 store?

    Last time I checked, Apple's app store is where the money is. Developers don't work on what's convenient unless they're hobbyists. If they're in it for the money they go where the money's at. Does Manager X care that Developer Y has a philosophical disagreement with Apple? Nope.

    Personally, I like the idea of sandboxing. It provides stability and security, two things that will wane as Apple's market grows. I can boot into Linux whenever I want unfettered access to anything and geek out. When I want efficiency and basic functionality, OS X please.

    --
    "From the depths of my skeptical and rationalist soul, I ask the Lord to protect me from California touchie-feeliedom."
  36. Sounds a little butt hurt by thetoadwarrior · · Score: 1

    No one forces you to use the Mac app store and sandboxing is a good thing. I hate to tell him it's only going to increase across all systems. Sandboxing apps isn't going away.

  37. Subtle observation.. by 3Cats · · Score: 1

    My Pop is 73, asked me to help him buy a "tablet" the other day because he wants to keep his sheet music on it. He plays ukulele. I'm a dyed in the wool linux and android user, he's an old mainframe engineer from the 70's. He's not unintelligent but has had a bit of a decline in mental acuity so after much soul wrangling I steered him towards an iPad. He loves it. Simple, "intuitive" ( for him ) just his speed. He immediately downloaded "Onsong" after I helped him research it and off he went, merrily importing chords and music.

    Here's the observation- if regular users / geeks abandon Apple for unwalled gardens, it won't be readily apparent because there are always going to be older people like my Pop buying Apple products for the ease of use and simplicity. Just like there's always gonna be an older AOL user out there. But there may be no serious revenue stream in it for Apple. Older people use devices differently than most of us.

    See, my pop is not interested in any more apps. He's found the one thing he wants to use an iPad for and he's DONE. I showed him how to read his gmail on it on the web, he flat refuses to read a book on it, doesn't care about buying music ( he prefers to listen to ukulele examples on youtube) doesn't play games, doesn't care about facebook, twitter, instagram or anything else. He uses his laptop for his finances... he even wants to unlink his credit card from the appstore so "hackers" won't steal his card number.

    So Apple managed to sell him an iPad and *one* app. I can guarantee you he will use that one app and be perfectly content till the battery stops charging.

  38. Re:The more you tighten your grip... by steelfood · · Score: 0

    This is only true if you're writing an app that delivers a function. If you're writing a game, or some other user entertainment app, you're never really in danger of this.

    So if you're writing an app that integrates Twitter and FB and other social networking sites or some such, you might end up among the disgruntled. If you're writing a game, or you're the company running the social networking site, then you're probably ok.

    Though at some point in time, people are going to start heading for the exits when they realize their app selection is inferior to say, Android's app selection. Which is why Apple's fighting tooth and nail trying to keep Android phones from being sold.

    --
    "If a nation expects to be ignorant and free in a state of civilization, it expects what never was and never will be."
  39. OSX development $1000/year/seat that's why!! by Anonymous Coward · · Score: 0

    Why should I have to register with Apple? I'll tell you why because I've had a little advanced "insight" into what direction Cupertino is going.
    We're looking at a business model that will be along these lines just like the Xbox or the Playstation but in the end even more intrusive. Get this:

    1. OSX development to cost > $1000 / year / seat
    2. Developers to be required to hold certifications for the iOS/OSX release they're targetting
            This is to be enforced by having devs sign into Xcode with their personal apple id.
            This item alone has me upset the most, since I'm a freelancer _I_ have to pay to stay current on the certifications,
              the customer wont have an account I can use to work with unless they're taking it from another dev which I don't see
            how that will work.
    3. Developers to be background checked.
            Yes, you got that right, felons need not apply and wont be developing OSX software. Nor will people with bad credit.
            (how are you going to afford the certification fees in the first place, but hey)
    4. All **source** code to be validated by Apple online regardless if it's internal use / personal
            and binaries signed in the cloud

    I've been developing for OSX the past 5 years now and I've never felt so betrayed and backstabbed as by the
    control freaks in Cupertino. I say fuck them and shove it!!!!!

    Sure having a sandbox is a great idea but not when the only entity that's really in control over it is Apple. Then it's just
    another instrument to force both developers and customers to comply.

    1. Re:OSX development $1000/year/seat that's why!! by medcalf · · Score: 1

      Wow, what complete and utter FUD! Except that none of that is true, good points.

      --
      -- Two men say they're Jesus. One of them must be wrong. - Dire Straits
    2. Re:OSX development $1000/year/seat that's why!! by Anonymous Coward · · Score: 0

      Well I'm not expecting you or anyone to climb into the bathtub get drunk and slash your wrists over
      what what I'm saying but do watch for it. None of this will happen overnight, and they're not nearly
      there to execute on most of it. Just look at their training /certification program. It'll be a long while before they
      can impose that extra developer tax.

      The only thing I can see them do right now is increase the existing $99 yearly "club" fee to say $199.
      I don't see them pulling free Xcode anytime soon, people do need gcc to compile opensource and
      that's a fight they probably don't want to fight just yet. Maybe what they'll do when they pull it, is to supply
      a free gcc compiler and darwin headers, without Cocoa, Carbon etc. Hey it's not like I got the entire
      map of the road to tyranny here, just where they want to arrive at.

      So believe it or not, ripley, Apple has always from its earliest day had a hunger for controlling its market
      and the success they had with the ipad/iphone just fans the flames of that appetite.

    3. Re:OSX development $1000/year/seat that's why!! by Guy+Harris · · Score: 1

      Well I'm not expecting you or anyone to climb into the bathtub get drunk and slash your wrists over what what I'm saying but do watch for it. None of this will happen overnight,

      And some or all of it might not happen at all.

    4. Re:OSX development $1000/year/seat that's why!! by Anonymous Coward · · Score: 0

      Why should I have to register with Apple? I'll tell you why because I've had a little advanced "insight" into what direction Cupertino is going.

      No you haven't, you've made some shit up, assumed the product of your imagination is true, and then gotten pissed off at your own paranoia. It's amusing, but please, get help. Apple hasn't even hinted at doing any of the crazy shit you're claiming is a done deal.

  40. Maybe by mosb1000 · · Score: 1

    Maybe, but the whole point of the App store is that it's supposed to be secure and safe for users. Sandboxing is a part of that security, even if lazy developers don't like it. The world has changed, people are expecting software to be written securely now, if developers can't come to grips with that, they're the ones who will be left out in the cold, not Apple.

  41. More money for me.. by MikeFM · · Score: 1

    Let the idiots leave. Users love free upgrades and buy lots more software (I do). That way you know the developer isn't going to pull a Microsoft on you where you keep paying just to make it work but it never does.

    --
    At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
  42. Now Tim Cook begins to sound like Ballmer by Anonymous Coward · · Score: 0

    in response to question about the walled garden you just get DEVELOPERS!, DEVELOPERS!, DEVELOPERS!, ...Resistance is futile you will work for the APPLE, Resistance is futile you will work for the APPLE, Resistance is futile you will work for the APPLE,

    1. Re:Now Tim Cook begins to sound like Ballmer by Guy+Harris · · Score: 1

      in response to question about the walled garden you just get DEVELOPERS!, DEVELOPERS!, DEVELOPERS!, ...Resistance is futile you will work for the APPLE, Resistance is futile you will work for the APPLE, Resistance is futile you will work for the APPLE,

      Umm, Ballmer was talking about third-party developers in his music video. The Microsoft equivalent to the Apple page to which you're pointing is here.

  43. Regarding Valve... by Gordo_1 · · Score: 2

    Notice how Valve is already running for the exits?

    You may not have noticed, but the main reason Valve (and specifically Gabe Newell) feels that Windows 8 is the worst thing ever hoisted on humanity may have something to do with the fact that Windows 8 has a built-in facility (the Metro app store) that has ability to overtake the virtual monopoly that Valve has built with Steam for the digital delivery of PC games.

    Win8 is really a shot across the bow of Valve's business model. They'd better have a plan B in place -- and no, Linux is not a viable plan B.

    1. Re:Regarding Valve... by PopeRatzo · · Score: 4, Insightful

      You may not have noticed, but the main reason Valve (and specifically Gabe Newell) feels that Windows 8 is the worst thing ever hoisted on humanity may have something to do with the fact that Windows 8 has a built-in facility (the Metro app store) that has ability to overtake the virtual monopoly that Valve has built with Steam for the digital delivery of PC games.

      Win8 is really a shot across the bow of Valve's business model. They'd better have a plan B in place -- and no, Linux is not a viable plan B.

      Valve will be fine. They'll just have competition.

      Did anyone ever believe that Valve would never face any challenges from competitors? As long as they keep delivering value, they'll continue to do well.

      The notion that success can only mean you are #1 in your sector is one of the things that's hurting business in what passes for capitalism in the 21st century. Like an old commercial used to say, number 2 has to try harder, and even though most corporations don't like it, "trying hard" is supposed to be part of the deal. We've had too many corporations who have believed "trying hard" means killing all your competition via the legal system instead of the marketplace.

      --
      You are welcome on my lawn.
    2. Re:Regarding Valve... by marcosdumay · · Score: 0

      Linux is not a viable plan B.

      Linux is not a plan B. Linux is a threat that will put the game in a chess-like stalemate, and guarantee that Microsoft won't make Steam not work (Lotus Office style) at Windows 8.

    3. Re:Regarding Valve... by Gordo_1 · · Score: 1

      I doubt it. Unless Valve is able to miraculously get big name games ported to Linux on a consistent basis (not to mention having Linux capture more than 1% of the desktop market) it's not going to be the kind of serious alternative that keeps Microsoft honest. Don't get me wrong, I buy every Humble Bundle, but that's not the kind of games that Linux needs.

    4. Re:Regarding Valve... by marcosdumay · · Score: 1

      Valve doesn't need an increase in Linux market share, but, yes, they'll need to port the games.

      If Linux is a viable gamming plataform, despite nobody using it, MS won't be able to lock Steam out of Windows. If MS does so, people will start to use Linux, and MS loses way more than they gain. Valve still loses more than MS, but that shouldn't matter for MS.

    5. Re:Regarding Valve... by Anonymous Coward · · Score: 0

      Who knows, Valve might be big enough to pull it off. And Apple + Linux on the desktop could definitely win against a game free Windows.
       
      People kind of hate Windows, not much but enough to leave it at their office.

  44. For those that don't remember the 80s... by Charliemopps · · Score: 1, Flamebait

    For those that don't remember the 80s...

    This is what apple does. They create a market. They hype it to the point that they have a rabid consumer base that has no clue what's really going on. Then they change the rules and jack up the price to rake in the profit. Is there really any reason anyone would ever chose an apple device based on its technical merits?

  45. meh by Anonymous Coward · · Score: 0

    people always whine about apple's closed policy on hardware, software, and everything. They fail to realize this offers a huge advantage of greater compatibility and streamlined user experience. If you want open hardware/software there are plenty of alternatives. Most people reading this probably don't buy their software anyways they just steal it.

  46. Mod parent up. by bussdriver · · Score: 1

    Apple has always jerked around developers with changes larger than this one; also they don't mind upsetting loyal customers either.

    The TFA is a troll, the new sandboxing policy is something developers should have been able to do for at least a decade and expecting them to do it now makes sense. Part of development should involve sand boxing; merely following the documented API is not enough the scope of use of those system calls should have always been specified in a technically useful format.

    1. Re:Mod parent up. by shutdown+-p+now · · Score: 1

      The problem with app store sandboxing is that there are many things that you simply can't do from within the sandbox, even perfectly reasonable ones that provide for useful end user features. He lists a few, like iCal and iPhoto integration. So it's not just a matter of rewriting things to conform to the new APIs or guidelines - you have to actively shed features from the app, in effect making it less powerful/useful.

      Of course, Apple's own apps integrate just fine, because they aren't really bound by these requirements...

    2. Re:Mod parent up. by Guy+Harris · · Score: 1

      Of course, Apple's own apps integrate just fine, because they aren't really bound by these requirements...

      Except for the ones that are bound by those requirements, such as Preview and TextEdit (and some daemons) in Lion, and those plus several others in Mountain Lion.

    3. Re:Mod parent up. by shutdown+-p+now · · Score: 1

      Sure, for those apps where the sandbox work, they use it. The point is that they can skip it where it doesn't make sense.

    4. Re:Mod parent up. by Guy+Harris · · Score: 1

      Sure, for those apps where the sandbox work, they use it. The point is that they can skip it where it doesn't make sense.

      As can third parties, if they're willing to avoid the Mac App Store. The difference with Apple is not that they get to choose what to sandbox - others can as well - the difference is that they get to put un-sandboxed stuff, such as the OS and developer tools, in the Mac App Store in special packages. How big a problem that is depends on to what extent third-party software loses out by not being in the App Store. It's probably a Good Thing if most applications and daemons are sandboxed, including those from Apple, so to some degree it's a Good Thing if people are encouraged to write code that can run in a sandbox, but there needs to be an "escape hatch" for people who want software that does stuff that can't be done in a sandbox and are willing to trust the developer of that software not to have written malware and to have written software that's "safe enough" from attack. (And, yes, I think it'd might be a Good Thing to allow that for iOS apps - and Metro apps - as well.)

  47. The big deal about sandboxing by goombah99 · · Score: 5, Informative

    I suspect people reading here dont' have a clue about sandboxing or what a BFD it is. Sandboxing is massively overdue. It's been available for years and years in OSX but there has been a zero adoption rate. I came across it in Xgrid, an apple application which relied heavily on it.

    Xgrid is a job server that lets other people run jobs on your computer---safely. How the heck do you do that safely and still have left an environment that can do anything at all. You can't do this with linux permissions or firewalls. But you can with sandboxing. in sandboxing you specify in detail what resources every application has access to. What parts of the file system it can't see even if it has unix permissions. What parts of a network it can access. How much memory it can use. etc... It's a universal wrapper that can be created for every program.

    Since firefox can be wrapped it's insane to use any browser without wrapping. If some roque plug in contains the ability to do something nasty you dont' care because it can't. it can't access resources it needs. You are essentially shutting down bad behaviour not bad apps.

    So why is it not default?

    Cause it's annoying to set up. If you take shortcuts in your application based on giving it more privledges than it needs you get punished by the sandbox.

    lazy developers hate it.

    time to force the issue. it's good for consumers.

    It doesn't do anything for apple, other than make the OS better.

    --
    Some drink at the fountain of knowledge. Others just gargle.
    1. Re:The big deal about sandboxing by Mabhatter · · Score: 4, Interesting

      The problem is that Apple has not developed system wide functions to replace many of the things they are taking away... And for the things they are replacing, they are going for the heavy-handed iOS approach and locking devs down to only sharing specific Apple-approved file types. Basically having the computer act like a "system" is dead in favor of manual apps. The idea of using Apple Script to string your own custom workflow of little apps is right out the window.

      Add insult to injury, Apple seems to be preemptively "Sherlock-ing" their most prosperous Mac Devs about one OS version BEFORE Apple copies them. now they are pulling apps and leaving USERS in the lurch without features they had yesterday.

    2. Re:The big deal about sandboxing by Anonymous Coward · · Score: 0

      I don't want to play in the apple sandbox.

      Someone took a shit in there and didn't even bury it.

      I suspect furrys.

    3. Re:The big deal about sandboxing by Anonymous Coward · · Score: 0

      I'm extremely glad that app must now not write turd all around the system and that are forced to pack user data in subgle files instead of scattering it all over the folder

      Sincerely, a clueless customer.

    4. Re:The big deal about sandboxing by Kalriath · · Score: 1

      Xgrid? You mean that feature they removed from Mountain Lion. Yeah.

      Everything you knew about OSX Cluster Computing is now worthless.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    5. Re:The big deal about sandboxing by Anonymous Coward · · Score: 0

      I think you don't know what Sandboxing in OS X really is. It's just well-known MAC plus a few support API calls by the OS to allow developers to do what they used to do.

      Yes, in theory it makes applications more secure against other applications. In practise, it's just a half-baked security measure that annoys developers and costs them unnecessary time (remember, laziness is a programmer's virtue), whereas malware writers will easily circumvent it, because OS X like every other consumer OS is open with security holes like a Swiss cheese.

      MAC was never intended for global access restrictions of this "sandboxing" style, it's strength only really shows up in very individual and fine-grained access control implemented on the basis of verifiable security policies and admininistered by a real, full-time system administrator.

      My 2 cents.

    6. Re:The big deal about sandboxing by serviscope_minor · · Score: 1

      You can't do this with linux permissions or firewalls.

      No, but you can so it with SELinux or Apparmor.

      --
      SJW n. One who posts facts.
    7. Re:The big deal about sandboxing by Anonymous Coward · · Score: 0

      The problem is that Apple has not developed system wide functions to replace many of the things they are taking away...

      Can you actually give specific examples, or are you just repeating "sky is falling" paranoia based on surface skimming of the controversy?

      (yes, I know real developers have complained about specific things. However, if you follow what they are saying the message is not 100% "Apple is taking things away and doing nothing", it's more like "Hey they actually responded in some cases and helped us out, but there are still things they need to do".)

      And for the things they are replacing, they are going for the heavy-handed iOS approach and locking devs down to only sharing specific Apple-approved file types.

      That's complete bullshit. There are no restrictions on file type. If you really believe there are, go through this document (it's not very long, it's a relatively high level overview of sandboxing) and tell us where exactly it says "Thou shalt use only these Approved filetypes, and if you do not, you are a jerk and shall be snuffed out".

      https://developer.apple.com/library/mac/#documentation/Security/Conceptual/AppSandboxDesignGuide/AppSandboxInDepth/AppSandboxInDepth.html

      Basically having the computer act like a "system" is dead in favor of manual apps. The idea of using Apple Script to string your own custom workflow of little apps is right out the window.

      This is also complete fucking bullshit. It's down right now so I can't give a specific link, but at:

      https://developer.apple.com/videos/wwdc/2012/

      if you have an Apple developer account (the free kind, no need to pay $99), you can watch Sal Soghoian's talk (Sal is Mr. AppleScript going waaaaay back) about the interaction of AppleScript with all the new security stuff. The short version, from my memory: when you, the user, are writing your own scripts or using Automator to make your own custom workflow of little apps, there are no restrictions. That's right, none.

      Add insult to injury, Apple seems to be preemptively "Sherlock-ing" their most prosperous Mac Devs about one OS version BEFORE Apple copies them. now they are pulling apps and leaving USERS in the lurch without features they had yesterday.

      What a load of bull. Apple isn't "pulling" apps over anything related to sandboxing. New submissions have to be sandboxed, but as far as I know old ones are grandfathered.

      And the whole "Sherlock-ing" thing? You have got to be kidding me. Sherlock was on version 2 before the indie application you're thinking of was released. Said indie app was explicitly derivative of Sherlock, right down to its name (Watson). It took the basic Sherlock application design and extended it to do more things (narrow types of Internet search such as movie show times). In the meantime, Apple was working on Sherlock 3 with essentially the same capabilities...

      Did that dev get a raw deal? Sure, but it's hardly as bad as people like you played it up to be. But more important than that, the whole mindset you're operating from is stupid and wrongheaded. When a small developer writes a thing, it does not mean everyone else in the world is permanently enjoined from doing their own take on it. That makes about as much sense as saying that just because Agatha Christie wrote some cracking mystery novels featuring Miss Marple, the elderly spinster amateur detective, nobody else may ever write books in which octagenarian ladies solve crimes.

      Apple actually often makes acquisition offers to small developers when they want to integrate software like Watson. But in Watson's case, that wouldn't have been a very good deal for Apple since they already owned an app which did most of the same things, and they may have already been working along similar lines on their own initiative before they even saw Watson. Guess what happens when it's not a good business deal to acquire rather than continuing in-house work?

  48. What a poor article. by toddmbloom · · Score: 0

    Just because a couple of developers are whining doesn't mean Apple is in trouble.

  49. ungulate ululations by epine · · Score: 1

    Aesop weeps.

    The early Latin version of Phaedrus begins with the reflection that "Partnership with the mighty is never trustworthy".

    But wait, there's more.

    It then relates how a cow, a goat and a sheep go hunting together with a lion. When it comes to dividing the spoil, the lion says, "I take the first portion because of my title, since I am addressed as king; the second portion you will assign to me, since I'm your partner; then because I am the stronger, the third will follow me; and an accident will happen to anyone who touches the fourth"

    Welcome to the Soprano sandbox.

    the App Store is no longer a reliable place to buy software

    You've read the earnings reports and you're still thinking Puma concolor and not Panthera yeti?

  50. Often? by issicus · · Score: 1

    '"Arment also comments on the 'our way or the highway' attitude Apple often takes in these situations and how it may be backfiring this time around.""
    hasn't apple always been like that? in fact I think that maybe what their business model is based on.

  51. Remember when "apps" were called "programs"? by ukemike · · Score: 1

    Remember when "apps" were called "programs"?

    --
    -- QED
    1. Re:Remember when "apps" were called "programs"? by PacoSF · · Score: 1

      I think there's a significant difference between apps and programs.
      An app, you don't have to install -- or even find the folder where you've downloaded it. And you don't need a manual or much configuration to start using it immediately.
      For the majority of people, this difference is huge.
      Arguably, contributing to the success and massive growth of mobile app store/market place in the past few years.

       

    2. Re:Remember when "apps" were called "programs"? by ukemike · · Score: 1

      Hey we are talking about OSX here, not like we're talking about iphones. It's been a loooong time since I had to know where a program goes to install it on windows. Download the .exe or .msi and double click on it. And it's still a program.

      --
      -- QED
    3. Re:Remember when "apps" were called "programs"? by PacoSF · · Score: 1

      you're right, the whole idea of labeling programs as "apps" has confused me once again.
      it's a bullsh*t transitional phase we're in right now.
      moving on.

    4. Re:Remember when "apps" were called "programs"? by lpq · · Score: 1

      That was when they actually did something substantial rather than just being increasingly inane ways to waste your time...

    5. Re:Remember when "apps" were called "programs"? by maxwell+demon · · Score: 1

      No. However I remember when they were called "applications" (and applications, daemons and all other types of executables were collectively called programs).

      --
      The Tao of math: The numbers you can count are not the real numbers.
  52. Re:The problem is... Apple wants to sell APIS by Anonymous Coward · · Score: 0

    You could always explain why that is so:

    "Please note: This is the Apple AppStore version of XYZ called XYZ/A. This version of XYZ is restricted in functionality for improved security.
      Click here to learn more about restrictions in XYZ/A. You are also licensed to use the full version of XYZ called XYZ/F. You can download XYZ/F
      here. Some future enhancements of XYZ may not become available in XYZ/A at all and some XYZ enhancements may be made available for XYZ/A
      at a later point in time after they were released for XYZ/F."

    Then in the App whenever they want to do something they can't do in XYZ/A they get this as a popup.

    Not that Apple is going to like that either it does not jive at all with their (shitty) plans. The idea is they want to start selling APIs at some point. Huuuu
    you want to sell a remote desktop application ... okay that means you want to connect to port tcp/1555 (made that one up too lazy to check what the
    default rdp port is). We'll sell you access to that port on remote machines for a one-time fee of $22,000 or we'll take $.06 for each copy you sell,
      Remember you need to use our cryptography, we'll rent you 5 user certs for $.35 cents. Sorry we just offer them in quantities of 5,10
    20 and unlimited. Huuuu your application uses SSL, no self-signed certificates signed for the next 30 years allowed, they're not secure, you need to get
    one signed from an approved CA.

    Uuuuh you're saying you want to sell a remote desktop application for accessing the OSX desktop and you need access to intercept video. Sorry those
    API's are completely off limits to third parties for security reasons, also keep in mind there already is Apple Remote Desktop.

    if Apple gets their way the future will be very bleak.

  53. Translation: I don't own an iPhone .... by Anonymous Coward · · Score: 0

    ... but I'm going to claim I do then regurgitate some BS crap I read somewhere.

  54. Another human failure by turkeyfish · · Score: 1

    Apple, the new Microsoft. Greed gets in the way, no matter what.

  55. Re:The problem is... Apple wants to sell APIS by Guy+Harris · · Score: 1

    Not that Apple is going to like that either it does not jive at all with their (shitty) plans. The idea is they want to start selling APIs at some point.

    Your idea is that they want to start selling APIs at some point. Whether that's Apple's idea is another matter.

  56. Re:The problem is... Apple wants to sell APIS by Kalriath · · Score: 1

    You could always explain why that is so:

    "Please note: This is the Apple AppStore version of XYZ called XYZ/A. This version of XYZ is restricted in functionality for improved security.

      Click here to learn more about restrictions in XYZ/A. You are also licensed to use the full version of XYZ called XYZ/F. You can download XYZ/F

      here. Some future enhancements of XYZ may not become available in XYZ/A at all and some XYZ enhancements may be made available for XYZ/A

      at a later point in time after they were released for XYZ/F."

    Then in the App whenever they want to do something they can't do in XYZ/A they get this as a popup.

    Nope. Because the App Store doesn't give the developer the details they'd need to validate the identity of a customer as someone who actually is a customer. So we end up in the case where the developer is selling an app-store version, and a non app-store version, and you have to buy each one seperately.

    Now, there are companies like TechSmith who apply the trust principle (if you buy an upgrade license off them, they trust that you purchased an original license from somewhere, App Store included) but no developer is going to just give you a link to a full version of their app that has no way of validating whether you purchased it in the first place.

    --
    For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  57. What problem? by Clsid · · Score: 1

    After reading the article, I couldn't help but get the feeling of somebody whining about changes, like you know, people getting old. The reason I mention this is two-fold, I have been using the App Store quite extensively and I think it's a great idea to a big issue with Mac software, especially overseas, Mac software availability at retail stores. With the App Store I get an upgrade central which is very neat, kind of like Curse for World of Warcraft add-ons.

    Now the other reason I see this as whining is because I learned how to program with Visual Basic 3, and everything was fine and dandy until VB6. When .NET arrived, the changes were so extensive that I felt it was a new language not worth learning, so I jumped shipped to the "holy grail" of programming at the time Java and C++. Recently I had to work on a VB.NET project, with the idea of either improving upon it or migrating it to something else. So after all was said and done, I now realize how foolish I was about rejecting some of those changes. They truly did improve the language in many ways that I wasn't able to grasp before without being exposed to C++ or similar languages. So I believe Marco Arment will eventually figure it out that the only way possible is forward, even if you don't like the changes and even if they truly suck.

  58. I am pretty sure that in about two years... by mark-t · · Score: 0

    ... there will not be any choice.

    The options for Mac developers will be to either sell their app on the app store, or else only make it available to jailbroken devices - and although I won't refute the popularity of jailbraking on portable devices, on a device like a full-fledged desktop computer, I'd suspect that jailbraking would be far less common, because one would probably no longer be able to obtain important updates to system software, and security is a potentially far more serious issue on an internet-connected desktop computer than it is on typical handheld devices.

    While it's certainly true that a lot of Mac developers will leave Apple behind when this transition occurs, I think that the number of remaining loyal Mac users will keep no small number of them behind - and like iOS itself, may also draw the interest of other software houses that had not previously been interested in that platform.

    1. Re:I am pretty sure that in about two years... by Guy+Harris · · Score: 1

      ... there will not be any choice.

      And I'm reasonably confident that there will be. Apple appear to think that there are OS X machines and iOS machines, and that, whilst there are many things that both of them can do, they have different purposes - iOS machines being for users who prefer a simpler, but more limited, User Experience(TM), and OS X machines for users for whom that's not good enough.

    2. Re:I am pretty sure that in about two years... by mark-t · · Score: 1

      I would like to hope so... but I've just got this nagging feeling that Apple's going to try and do this anyways. When it finally does start to hurt them, they'll ultimately lighten up on the policy, of course, but by then it will probably be too late, and the Mac platform may meet a premature end.

  59. They were called "Applications" ... by Lazy+Jones · · Score: 1

    "program" is a more generic term - see Application Software on Wikipdia

    --
    "I love my job, but I hate talking to people like you" (Freddie Mercury)
  60. Good by GameboyRMH · · Score: 1

    There's still hope for MacOS to remain open and limit the spread of the curation disease onto the desktop.

    --
    "When information is power, privacy is freedom" - Jah-Wren Ryel
  61. Apple is the new TSA? by Anonymous Coward · · Score: 0

    Apple says "our way or the highway."

    The TSA says "our way or the highway."

    The highway is becoming an increasingly popular option of late!

    1. Re:Apple is the new TSA? by Guy+Harris · · Score: 1

      Not until you have to let them grope your junk before you can become a developer. (And I don't mean that metaphorically. If it doesn't involve somebody from Apple wearing rubber gloves, it doesn't count.)

  62. You might rethink that by Sithech · · Score: 1

    As a newcomer to the Mac, I was not at all interested in the App Store. Maybe I'm too cynical, but goddamn it, I'm proven right too often to change my ways. The App Store does not solve any existing problems for me, as a user. If I can find some app in their, then I could have Googled for the author's web site just as easily. I actually prefer apps that self-update, rather than having to open the inflexible App Store client. .

    The Mac app store gives real users many advantages:

    • One place to go to keep all applications updated.
    • One purchase let's you install on all your macs for no added expense.
    • The app has been code reviewed by Apple and certified virus free, privacy-respecting.
    • Reviews of the app are available to review. You get to feedback your own review to the world too.
    • You don't have to give payment detail, such as credit card info to a developer.
    • You don't have to give your personal info to a developer, who may resell it or have it hacked.
    • No need to keep backups of apps, you can redownload free after nuking your system.

    The downsides:

    • Developers get more money than if they sold in physical stores, but less per unit than if they sold direct on their own website.
    • Developers can't hide adware or malware in their apps or app websites.
    • Apple knows what you bought.
    • Developers that don't want to let you run on all your machines for one price won't sell in the app store. Example: Microsoft Office for Mac.
    • Apps in same category are directly competing. It's like putting all the cereal in one aisle, the consumer has more choice visible. But if you're not in the app store, it is like selling in a farmer's market. Customers have to find you.
    1. Re:You might rethink that by billcopc · · Score: 1

      Good points, but they come with a steep price. Updates now take a long time to trickle through the system, the same as IOS apps. Privacy is a thing of the past. This does absolutely nothing to curb piracy (nothing ever will). It creates a huge bottleneck since any downtime at Apple results in downtime for everyone.

      Given the many hells I have suffered as an IOS developer, over the past year alone, I have a less than rosy view of Apple's reliability. I've lost several weeks to major blunders on their part, around only two pieces of software. I have absolutely no faith in their ability to oversee tens of thousands of third-party releases.

      --
      -Billco, Fnarg.com
  63. Choice by etinin · · Score: 1

    What is really different in this case is that customers have a choice. They cannot choose whether to buy or not from the app store when it comes to iOS devices.

    --
    "I decided I could write something better than everything out there in two weeks. And I was right." - Linus Torvalds
  64. Given the limited options, flamebait is close. by Anonymous Coward · · Score: 0

    I own just about every Apple computer they've made since OSX hit the streets, as well as iPad, iPod, and AppleTV. No iPhone. :) I'm a developer, too. Two projects in the fire ATM, one large and still under dev, the other on the street and doing well. Both are OSX.

    I was a huge fan of OSX for years. Pretty happy with rev one of IOS, too.

    But both environments are going visibly downhill. OSX is being aimed at appliance land, actually trying to lose its status as best combo of *nix and a GUI in favor of "you can't run that" and "let's blank your monitors, you don't need those!"

    IOS... bigger, slower, buggier. 1980s-era crippled folder system. Half the apps I have that used to be 100% stable have become unstable (on iPad v1) Maybe more than half. Some won't even start any longer. There there's the whole "no memory cards" sensibility. What seemed acceptable in v1 for a tablet design right out of the gate is now looking positively prehistoric.

    I didn't really mind the price premium because I felt I was getting value for it. I put up with the clueless "main screen only" menu bar, using hacks to fix that. I threw the one-button mice in the drawer without ever taking them out of the plastic. I replaced the typist-hostile chiclet keyboards. I tolerated the crippled resize handles and really weird idea Apple had for what the window buttons should do.

    Why? Simple. OSX was so good elsewhere, I really developed a case of "not even going to consider anything else" based on its many, many strengths.

    But sandboxing... no. Not going there. Not even //slightly// interested as a user //or// a dev. As a dev, not particularly interested in trying to jump through Apple's hoops over what can be in the app store, or not, either.

    Something else... over the years I've noticed they're not very good about fixing OS bugs. They're perfectly happy to ship a version of the OS with a problem, sometimes quite serious (UDP socket bug, color profile stall bug, bogus console error bug) and then... perhaps... fix it in a later version of the OS, but leave everyone even with the previous version hanging.

    So just FYI: the issues here are real. And //that// is why fact-free defenses of Apple are getting modded down.

    1. Re:Given the limited options, flamebait is close. by Guy+Harris · · Score: 1

      I tolerated the crippled resize handles

      Fixed in Lion, so that accidental resizing of a window when you're trying to select some text near the edge of the window is a completely cross-platform experience. (I forget whether I've done that on Windows, GNOME, or both, but when the ability to resize windows from the sides first showed up during Lion development, I started doing that on OS X as well.)

      (That's not a reason not to have resize-from-the-side - resize-from-the-side lets you, for example, more easily resize along one axis without affecting the size along the other axis - it's just a small case where the advantages are accompanied by disadvantages.)

    2. Re:Given the limited options, flamebait is close. by Guy+Harris · · Score: 1

      IOS... bigger, slower, buggier. 1980s-era crippled folder system.

      If by "crippled folder system" you mean "silo for each app, with no subfolders in a silo", that's "early 1980s" at best; I think MS-DOS 2 (introduced in 1983) had subdirectories in FAT, as did HFS (introduced in 1985). (And workstation OSes had them since Day One, but most people didn't have UN*X workstations as their personal computers....)

      I'm curious how many documents for a given app you need to have before "no subfolders in a silo" breaks down, and whether Apple just figured "anybody with that many documents should just use a Mac".

      Something else... over the years I've noticed they're not very good about fixing OS bugs. They're perfectly happy to ship a version of the OS with a problem, sometimes quite serious (UDP socket bug, color profile stall bug, bogus console error bug) and then... perhaps... fix it in a later version of the OS, but leave everyone even with the previous version hanging.

      Yes, they're annoyingly strict at times about what bug fixes they allow into a software update. (I'm assuming by "later version" you mean "later major version", so that a bug in 10.x gets fixed in 10.x+1 but not in any 10.x.y software update.)

  65. Folders by Anonymous Coward · · Score: 0

    If by "crippled folder system" you mean "silo for each app, with no subfolders in a silo",

    Under IOS, a folder can hold 20 apps. No more. It can't hold subfolders at all. So, say you have 21 applications of one type, for instance games: you need two folders on the work surface now, such as games1 and games2.

    I think the point of a folder system should be that you could have a games folder containing all your games, and perhaps inside that you might have "shooters", "board games", "tower defense", etc." But at *least* you should be able to put your games in one place. Same point for every other class of app. IOS's folder system is one tiny, dysfunctional step above not having folders. It makes organization a problem, it's inconvenient, and it's wasteful of the limited organizing space you have on a tablet. It's a failure of vision.

    1. Re:Folders by Guy+Harris · · Score: 1

      If by "crippled folder system" you mean "silo for each app, with no subfolders in a silo",

      Under IOS, a folder can hold 20 apps. No more. It can't hold subfolders at all.

      And it can't handle anything other than apps.

      None of this is new, though; it's been that way since "folders" were introduced, and, before that, you couldn't even put apps into some form of organization fancier than "screens in Springboard".

      IOS's folder system is one tiny, dysfunctional step above not having folders. It makes organization a problem, it's inconvenient, and it's wasteful of the limited organizing space you have on a tablet. It's a failure of vision.

      And the underlying OS and file system support directories inside directories inside directories (good grief, it's UN*X with HFS+ as the underlying file system, for crying out loud), but no, you can't expose that to users, their head would explode or something. Also, grandpa.

  66. Worst article ever by Mephesh · · Score: 1

    I'm so over people posting articles and not reading them properly. Is this merely a rush for quick fame on slash dot? Slow down! Calm down! Read the article thoroughly before posting it on slashdot. Not reading a a post by SoulSkill ever again.