Adobe acknowledges InDesign issue with latest MacBook

“We’re taking this issue very seriously,” he said. “I wish we had more to share at this time but I’ll be sure to share what comes down the line from the engineers relating to solutions or any workarounds they can find.”

Good for them for acknowledging the issue.



  • http://twitter.com/hypothesard Hypothesard

    As usual with Adobe, This Major Bug, will Maybe be fixed in the next Major update… (CS7)

    That’s Adobe World Class Mac Development for you…

    If only there was some real competition…

  • Kriztyan

    Adobe, always blaming Apple for it’s short comings. How is it that if an API was removed from 10.7.4, it does not affect my Mac Pro running the same OS version. I think the problem is Adobe and in it’s typical fashion, they are deflecting the issue. Why was Flash so crummy on the Mac? Again, Adobe blamed Apple. Why is Acrobat so insecure, Apple? Never Adobe.

  • Dave

    Meanwhile,

    Apple, for the last several weeks, has been featuring its Podcasts App in the App Store. Sounds like a great idea…

    Except that the app is a total disaster.

    When it works, it’s slow, laggy, and buggy. Usually, though, it just hangs with a gray screen.

    READ the reviews. They’re scathing.

    Yet no one in the tech press is talking about this.

    Why is Apple getting a pass?

    • http://twitter.com/Moeskido Moeskido

      A tech press review that doesn’t quite reach your level of hyperbole, but it’s not glowing either:

      http://www.macworld.com/appguide/app.html?id=1224399&expand=true

      • Dave

        How are these two issues related?

        Adobe gets kudos for acknowledging broken software. Apple? Podcasts is still taking one of four “Featured” slots on the App Store – for a totally broken product.

        The MacWorld article was clearly written after maybe an hour or two of use. The problems seem to arise after a day or two.

        I’m not talking about harping about skeumorphism or poor interface design choices. I’m talking about… the thing plain-old DOESN’T WORK.

        No follow-up from MacWorld.

        You think my post was hyperbole?

        Did you even bother to read the reviews on the App Store?

        Please take just a few minutes to page through the hundreds, perhaps thousands, of scathing reviews. Then you can can me “hyperbolic” if you want.

        The thing is a disaster.

        And so, I repeat, why is Apple getting a pass.

        • http://twitter.com/Moeskido Moeskido

          I avoid reading App Store reviews for the same reason I try to avoid Youtube comment threads. Lots of angry, hyperbolic children complaining about non-sequiturs, drowning out the legitimately useful information. Not always a terribly great sampling.

          “The thing is a disaster.” Nope, no hyperbole here.

          That said, I have no opinion about this Podcast app, because I have no need for it. It sounds like among the first of many attempts by Apple to hand off the overburdened list of tasks that iTunes currently performs, and will probably take several iterations to work well. I can wait.

          Adobe, like Apple, is very selective about which of its many mistakes it openly acknowledges. But by all means let’s carefully choose the anecdotes that best fit our current emotional state.

          Yes, Macworld magazine could have been a lot more thorough about that review—that’s true about a lot of their initial coverage of any new item—but I have a feeling that their more publicly accessible staff will add to it over time, in interviews and podcasts.

          • Dave

            ["The thing is a disaster." Nope, no hyperbole here.]

            I tried it. It worked for me, then it completely stopped working. I thought to myself, “is it just me?”

            So I went to look at the reviews. There are literally thousands of people who have experienced the same thing. Among these are hundreds who have submitted thoughtful, detailed comments in their reviews.

            You have no interest in even taking a minute to see this for yourself, so I guess we’ll have to agree to disagree.

            I will, however try to make my “disaster” description more clear to you.

            If an app completely does not work for thousands of people, I call that a disaster in terms of possible outcomes for an app.

            It is not a disaster in any other sense. And your insinuating otherwise is consistent with your continuing to call my comments hyperbole without even looking at the evidence that I have offered.

            I’ll call that “lazy.”

            I stand by my original premise:

            Why is Apple getting a pass on this clearly broken app and continuing to “feature” it in its App Store?

          • http://twitter.com/Moeskido Moeskido

            Lots of people are annoyed. You’re angry. I get it.

            But it’s an app. It’s not an explosion at a nuclear power plant or the collapse of an entire economy. People will be inconvenienced by this app and then mostly move on.

            Even within the scale of personal computing, Podcast’s failure to work properly is hardly on the level of, say, a major security breach or a buggy OS update. Calling it a “disaster” is attention-seeking hyperbole.

            Unless you have specific other words for events which actually hurt large numbers of people.

            The tech press will catch up to the reality.

            And it’s still not the subject of the article above.

          • Dave

            OK, so you’re not lazy. You’re just disingenuous.

          • http://twitter.com/Moeskido Moeskido

            And you’re histrionic.

            Tell me something. If a genuinely, terribly disastrous event were to occur to iOS users—say, an entire lot of iPhones spontaneously combusted while in use—how would you describe it?

            And who would listen to your opinion about it, knowing what you already consider “disastrous”?

          • Dave

            [And who would listen to your opinion about it, knowing what you already consider "disastrous"?]

            Anyone who knows how to read things in context.

          • Dave

            …and, btw, I find it really funny that, given your last few posts, you’re calling me “histrionic.”

          • http://www.tumblr.com/blog/his-divine-shadow His Shadow

            I find it funny that you are clearly unaware of the definition of “histrionic”.

    • http://www.tumblr.com/blog/his-divine-shadow His Shadow

      I put as much stock into user reviews as I do in your ability to keep things in perspective.

  • Dave

    From Jay Yarrow, of Business Insider:

    “Hopefully Apple fixes all the bugs in the podcast app, because it’s reportedly removing podcasts from iOS iTunes, forcing people to use this app isntead. If this is what people have to deal with, it’s going to be a disaster [emphasis mine].

    Spinning it out further, I really hope this is an isolated, one-off goof from Apple. If this is the future of its software and its apps, the company is in a lot of trouble. This podcast app is horrendous.”

    (google “Apple’s Podcast App Is Horrifically Bad”)

    Thanks to you, now I’ll know to tune him out if he starts blabbering about “events which actually hurt large numbers of people.”

    • Dave

      oops. that was supposed to end up way down below, where the columns are getting really narrow. ;)

    • http://www.tumblr.com/blog/his-divine-shadow His Shadow

      You’ve referenced a hyperbolic “report” by Business Insider laden with conditionals to support your own histrionics.

      Congratulations. You’ve completed the first requirement for Disqus Clown Colledge. Next you’ll be calling Dan Lyons and Apple expert.