Forgot your password?
typodupeerror
Android Apple

Wozniak To Apple: Consider Building an Android Phone 249

Posted by samzenpus
from the building-with-the-enemy dept.
snydeq writes "Apple co-founder Steve Wozniak has some advice for Apple CEO Tim Cook: consider offering a phone based on the rival Google Android platform. Speaking at the Apps World conference in San Francisco, Wozniak made the suggestion of an Apple Android device when responding to a question about the fate of the faltering BlackBerry platform, saying that BlackBerry should have built an Android phone, and that Apple could do so, too. 'BlackBerry's very sad for me,' Wozniak lamented. 'I think it's probably too late now' for an Android-based BlackBerry phone. Apple, Woz said, has had some lucky victories in the marketplace in the past decade, and BlackBerry's demise may provide a cautionary tale: 'There's nothing to keep Apple out of the Android market as a secondary phone market.'"
This discussion has been archived. No new comments can be posted.

Wozniak To Apple: Consider Building an Android Phone

Comments Filter:
  • Re:first (Score:4, Insightful)

    by Anonymous Coward on Thursday February 06, 2014 @07:14PM (#46179637)

    There are a lot of snarky comments in the “fuck beta” threads right now, and reading what little has been posted by soulskill, the admins actually think that they are being unfairly targeted by a mob mentality. This is a problem because the issues here will likely get managerial attention at Dice soon and if the executives see what looks like a bunch of juvenile shite in the comments, they are likely to buy into that false world view. If that happens, then Beta will be pushed through and Dice will think of themselves as victims of Anonymous or whatever.

    For this reason, I wish to lead a call for all users to spend the time from now until the boycott on the 10th to repost this as soon as a new story is posted.

    ----------------------

    Dice: Frankly, many of us want a new design, Classic is broken in so many ways. But beta is terrible, and this is what is wrong:

        * The value that Slashdot brings to its users is not in its articles. Frankly, the articles are terrible. The value that Slashdot provides is a discussion forum for self-selected nerds.

    * As such, it is vital that you remember that the community is not just an audience, it is also your primary content creator.

        * Your new redesign does not allow the community to create (or even consume) content because:
                        - It makes it impossible to follow discussions in the comments sections. This is largely because of the max-width on window and the fact that of the space left over is taken up by a useless sidebar. The vertical spacing is also overdone.
                            - Slashdot has a fragile but effective moderation system. Your changes make it impossible for readers to leverage that system to read a high quality discussion and ignore the trolls.
                        - It disregards conventions of the community. UIDs matter. We’re nerds. We understand that you need to attract a younger audience, but for a lot of us (including the younguns) it is thrilling to see a post from somebody who has been there from the beginning.

        * In the last 24 hours Soulskill has bitterly commented that the community has been involved since October and that they also get emails supporting the new design; only the comments are an echo chamber. This comment demonstrates a deep incompetence in your development team. Soulskill should have been citing A-B testing numbers. A-B testing is cheap, easy and effective but instead you are taking stabs in the dark.

        * Your ability to attain user acceptance is dismal. A number of years ago, when Taco needed to modernize the site, he solicited the community for designs, and awarded the best designer and used that design. That is how you leverage a community and gain their acceptance: incorporate them in the design process. As a bonus, you won’t have utterly useless redesigns that will either ruin your website or have to be scrapped.

  • Fuck Beta! (Score:1, Insightful)

    by Striek (1811980) on Thursday February 06, 2014 @07:18PM (#46179689)
    That is all.
  • Re:Beta Sucks (Score:3, Insightful)

    by Princeofcups (150855) <john@princeofcups.com> on Thursday February 06, 2014 @07:28PM (#46179815) Homepage

    Beta Sucks
    Join the boycott Feb 10-17.
    If Beta is still here on the 18th I will not return.
    Do not fix what is not broken.

    Please stop with this boycott nonsense. It accomplishes nothing except letting you "think" that you are doing something when you are powerless to do anything.

  • by excelsior_gr (969383) on Thursday February 06, 2014 @07:35PM (#46179905)

    I was very interesting in reading what the slashdot crowd would have to say on this topic and on the opinion of Woz. However:
    1. The slashdot crowd is too pissed of with Beta, so all they do is keep complaining about it, and,
    2. If they didn't complain and Beta was rolled out in silence then I would still not be able to read what the slashdot crowd had to say on the comment of Woz, because the discussion section of Beta sucks.

    So, pretty please, with sugar on top, take back the fucking Beta.

  • mystifying... why? (Score:4, Insightful)

    by jinchoung (629691) on Thursday February 06, 2014 @09:16PM (#46181263)

    android provides two things:

    - free, ready to go OS
    - app ecosystem

    apple already has both. using their existing OS incurs no additional cost. and it is a framework that they already know how to work around.

    even if they wanted to make a dirt cheap phone based off of an iphone 3gs, it would be a matter of making hardware that would fit the bill as secondary market product. they ALREADY HAVE the os and ecosystem.

    so WHY... in the WORLD... would apple do that? why in the world would woz say that?

    and i come at this as a pc user with an android phone... this is truly mystifying.

  • Re:Fuck Android (Score:5, Insightful)

    by maccodemonkey (1438585) on Friday February 07, 2014 @01:09AM (#46183009)

    To get our iPhone app on iTunes' App Store will be an absolute frickin nightmare compared to the ease of getting our Android version on the Play Store and all the early signs are that the Objective-C/iOS API will be much more of a pain in the ass than the Android API.

    I know both the Android and iOS APIs.

    There are some things each API does better than the other. And one is written in Obj-C and one is written in Java. HOWEVER...

    The iOS API is much more consistent than the Android API. Sure, it's Obj-C. And you have to learn Obj-C. And you might complain that Obj-C is new and different and not Java (which does NOT make it a bad language. Different != bad.) But if you know Obj-C, and if you know Java, the iOS API is just generally more sensible and easy to use. I would not define the iOS API as a pain in the ass. You'd call it a pain in the ass, but then again, I know it, and you don't.

    The Android API has several advantages. The Activities concept is a nice thing the iOS 6 and later APIs are just starting to play with. But they also make several boneheaded decisions. Rotating the device creates a new activity? WTF? Fragments? Fragments are nice but they're window dressing on a broken concept that iOS at least got right the first time. And native code support on Android is... lacking. Yes, you can technically do it, but not without jumping through a lot of development hoops you don't have to with the iOS tools. It would be nice if Android at least shipped with some Neon optimization code paths. And low latency audio on Android? Nope, still not there. Great if you're playing back or recording an audio file. Not great for much else. And don't get me started on all the bizarre OpenGL issues that iOS doesn't have.

    I don't mean to trash on Android too much. What I'm basically saying is I'm having trouble taking this seriously as a level headed comparison when it's basically "I spend a lot of time with Android, I know it, and I like it. I don't know iOS, and it seems totally crazy to me!" The iOS APIs are basically child APIs of what shipped in OS X, and from there what shipped in NeXTStep. A lot of developers have spent a lot of time with the APIs over the last 20 years. It's not like these are bizzaro APIs that came out of nowhere that have never been peer reviewed, iterated on and improved, or worked with for long periods of time. Which is more than I can say for the Android APIs.

  • by Vintermann (400722) on Friday February 07, 2014 @04:36AM (#46183817) Homepage

    There's a reason why you can't just strip out FAT support, a reason those patents are so obscene. It's a de-facto standard, and you need it for compatibility with lots and lots of stuff.

    The actual technical worth of the FAT filesystems is zero. They are dumb, slow, they fragment, and lacks essential features. You can have strictly superior systems for free. But due to network effects, it's very hard to get rid of as the lowest-common-denominator filesystem, that can be read on every Windows and OSX and dumb little flashcard-reading gadget.

Everyone can be taught to sculpt: Michelangelo would have had to be taught how not to. So it is with the great programmers.

Working...