Slashdot Mirror


Software Developer Explains Why The Ubuntu Phone Failed (itwire.com)

troublemaker_23 quotes ITWire: A developer who worked with the Ubuntu Phone project has outlined the reasons for its failure, painting a picture of confusion, poor communication and lack of technical and marketing foresight. Simon Raffeiner stopped working with the project in mid-2016, about 10 months before Canonical owner Mark Shuttleworth announced that development of the phone and the tablet were being stopped.
Raffeiner says, for example, that "despite so many bugs being present, developers were not concentrating on fixing them, but rather on adding support for more devices." But he says he doesn't regret the time he spent on the project -- though now he spends his free time "traveling the world, taking photographs and creating bad card games, bad comics and bad games."

"Please note that this post does not apply to the UBPorts project, which continues to work on the phone operating system, Unity 8 and other components."

137 comments

  1. It's easy by Anonymous Coward · · Score: 4, Insightful

    The Ubuntu phone failed because it's a fucking stupid idea. People want smartphones with a large base of popular apps.

    1. Re:It's easy by Zontar+The+Mindless · · Score: 1

      They weren't helped by the fact that existing players in the market would not allow ports of their apps.

      --
      Il n'y a pas de Planet B.
    2. Re:It's easy by Anonymous Coward · · Score: 0

      Like the iPhone which had only preinstalled apps and no App Store when it was first released 10 years ago?

      Or do we chalk that up to "religion" - the shifting sands of reason at Slashdot concern me.

    3. Re:It's easy by Duckeenie · · Score: 2

      That is what's commonly known as passing the buck.

    4. Re: It's easy by Anonymous Coward · · Score: 1

      Both apple and Android started somewhere.

      Big difference is both of them focus on UX. You can't just make a program, it needs to be something people want to use. If this was, then the power of open source could have helped it. Instead, people didn't want to use it because the experience sucked, so it died early.

    5. Re: It's easy by Anonymous Coward · · Score: 0

      If there is no monetary incentive to port the app, then what is the purpose? Ubuntu phone was a stupid idea just like unity desktop.

    6. Re:It's easy by ShanghaiBill · · Score: 3, Insightful

      existing players in the market would not allow ports of their apps.

      An obvious solution would be to use the Android ABI, so no port would be needed. Barring that, they were doomed from the start. If a behemoth like Microsoft couldn't break the Apple/Android duopoly, then Canonical never had a chance.

    7. Re: It's easy by Anonymous Coward · · Score: 2, Insightful

      No, we chalk that up as the world now is not 10 years ago.

    8. Re:It's easy by Opportunist · · Score: 3, Insightful

      When nobody has it, neither do you. If everyone has it, so do you.

      Old school MMOs had few, if any, quests, lots of grinding, horribly long travel times, insanely slow progression, really, really painful death penalties and no instanced pre-packaged content. But I dare you to make one like this today.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    9. Re:It's easy by allo · · Score: 1

      You never have this from the start. But somehow you need to start. Ubuntu Phone had its chance, because there is a lot of user base, which wishes android was more open (not from the source licence, but from the development process and restrictions like locked bootloaders).
      Okay, a lot not like "a lot of iphone users", but like "Hey, we're not selling sour beer there are many people who really like our idea right from the start"

    10. Re: It's easy by Anonymous Coward · · Score: 0

      Agreed. If you're a mobile developer with a popular app why would you want to bother having to develop and support yet another version of your app that runs on yet another platform when there ar very few users? There is no incentive to spend the time and money. It's a chicken and egg game. You've got to have a platform with a lot of users for developers to take notice and support the platform and you've got to have a lot of popular apps to get a large base of users. That is the long way of saying you've got to be there in the beginning of a new consumer computing paradigm in order to compete. Either that or you've got to be Microsoft with the X Box and have enough cash to afford to lose billions of dollars year after year to create a market for your products where one doesn't already exist.

    11. Re:It's easy by 91degrees · · Score: 1

      It does feel like that old thing of a solution looking for a problem. We want our phones to do certain things. They do so already. Ubuntu can do the same, but not as well.

    12. Re: It's easy by Anonymous Coward · · Score: 0

      This. Smartphones are "done" technology right now. You're Android or iOS. I know they targeted low income countries where the flagship smartphones are a fantasy to own, but in that market Android rules because those people want devices to reach into the rest of the world.

      It's not entirely a "fools errand" to work on the tech, but it was never going to sell. Maybe in another 5 years there will be a "technology disruption event" that changes the game and gives new players even footing. But even then it's a gamble to be one of 20 entrants when only 2-3 will win.

    13. Re: It's easy by Anonymous Coward · · Score: 1

      mmos arent phones. quit being stupid.

    14. Re: It's easy by Anonymous Coward · · Score: 1

      I don't think that would even work for the smartphone market. Microsoft spent easily $25+ billions on Windows Phone and fell flat on its face.

    15. Re: It's easy by kurkosdr · · Score: 3, Insightful

      There is a solution to that: It is called "being (mostly) compatible with an established API". This brings porting to the realm of bugfixing instead of the realm of a rewrite. For example, DOS was mostly compatible with CP/M and GNU/Linux was mostly compatible with Unix. Even Windows was compatible with DOS and Mac OS X was compatible with Mac OS 9 (via emulation, but provided users with a transition path). Very rarely does an OS with a completely new set of APIs (and not compatible to anything old APIs) becomes successful. The first Mac OS, Amiga OS, Symbian S60, Symbian UIQ, iOS and Android are the only examples that come to mind, and they all happened immediately after a new UI paradigm emerged in the industry. Canonical did the same mistake Microsoft did: The expectation that all devs will retool to support an OS with totally incompatible APIs that was late to the market (years after the new UI paradigm emerged). The Xbox example is irrelevant because game console APIs are expected to not be backwards compatible in general.

    16. Re:It's easy by thegarbz · · Score: 1, Interesting

      If a behemoth like Microsoft couldn't break the Apple/Android duopoly, then Canonical never had a chance.

      Just to be clear this solution is not something that simply needs money at it, and Microsoft's failure was not resources. In every case the failure was just shit products.

      Remember when blackberry owned 100% of the smartphone market? No one would ever topple them especially not a phone with no buttons.
      Remember when Apple ate their lunch and then was the only smartphone player in town with a product worth owning? That Android thing is just a toy in comparison and one with no apps or developers.
      Remember how Android was the most popular Smartphone OS on the market....

    17. Re:It's easy by Desler · · Score: 1

      And what incentive did they have to care about Ubuntu Phones? It had less marketshare than BB10 and Windows.

    18. Re:It's easy by exomondo · · Score: 1

      The Ubuntu phone failed because it's a fucking stupid idea. People want smartphones with a large base of popular apps.

      The other way to succeed is to have some really killer feature, something that is hugely innovative and disruptive. Many users can do what they need with a few basic applications and a web browser so if some competitor came along with a feature that was really compelling to people then they may have a chance. Ubuntu Phone (and Windows Phone, webOS, Maemo, Meego, etc) didn't offer that, they weren't necessarily bad operating systems, they were just more of the same.

    19. Re:It's easy by exomondo · · Score: 4, Insightful

      Windows Phone wasn't really a "shit product", in fact none of the real competitors to the smartphone market were. They were just late entrants to an established market that offered no compelling feature/innovation.

      Like you say, Apple upended the Blackberry/Windows Mobile duopoly with compelling innovation, Android then made that new paradigm accessible to everybody. The same is true of the desktop, Linux on the desktop is by no means a "shit product" but its usage share is low because it doesn't have that one thing that users say "yes, I will abandon my current computer and learn a new way of doing things because this feature makes my desktop computing so much better", that is what happened with cell phones when iOS/Android were introduced.

    20. Re:It's easy by Anonymous Coward · · Score: 0

      You never have this from the start. But somehow you need to start. Ubuntu Phone had its chance, because there is a lot of user base, which wishes android was more open (not from the source licence, but from the development process and restrictions like locked bootloaders).

      No! Nobody gives a shit about that, that is precisely *why* it failed. Canonical thought people wished that but the reality was that no, they didnt.

    21. Re:It's easy by Anonymous Coward · · Score: 0

      I still think Ubuntu phone a terrific idea and I want it to install from UBports on one of my devices. I don't want flashy apps. I really like the scopes idea. I want privacy [and also being the cool guy with a strange phone OS].

    22. Re:It's easy by Anonymous Coward · · Score: 0

      Windows Phone wasn't really a "shit product", in fact none of the real competitors to the smartphone market were. They were just late entrants to an established market that offered no compelling feature/innovation.

      Like you say, Apple upended the Blackberry/Windows Mobile duopoly with compelling innovation, Android then made that new paradigm accessible to everybody. The same is true of the desktop, Linux on the desktop is by no means a "shit product" but its usage share is low because it doesn't have that one thing that users say "yes, I will abandon my current computer and learn a new way of doing things because this feature makes my desktop computing so much better", that is what happened with cell phones when iOS/Android were introduced.

      People hate microsoft already, but have had it crammed up their ass with the alternative being overpriced apple hipsterwear.

      Of course they don't want it on their god-damn-phone.

    23. Re: It's easy by Opportunist · · Score: 1

      The same problem applies: You have a product that people want. Whether it sells depends on whether your competitor has a superior product. If he doesn't, you needn't either.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    24. Re: It's easy by Anonymous Coward · · Score: 0

      The iPhone succeeded because it was a paradigm shift and shattered the market from the malaise it was in. Android survived because it immediately realized that the phone game had changed and shifted from building s blackberry clone to an iOS clone. Both were early in the game, today neither of them would really have a chance as a new phone OS coming into the market.

      The tech gap is just to high where nobody would be willing to use the original iPhone now. At the time though that wasn't the case, but it will be hard for a new company to make ground without another tech shift.

      That said the huge benefit to people isn't so much the OS but the wealth of software now available to them from developers, making the gap even bigger.

    25. Re:It's easy by ChunderDownunder · · Score: 1

      Yes, I know I'm in the minority but as I've said in previous discussions, Continuum/Convergence would be that killer feature, provided they solve the "app gap".

      A 64bit machine with a octo-core processor and 6GB of RAM, as found in flagship phones of today is plenty powerful enough for my needs as a consumer. (if not a monster workstation for professional purposes). Hook that up to a KVM switch and we're set, so at which point I ask myself why would I need a x86-powered desktop machine with worse specs at home as a depreciating asset?

      A solution to the "app gap" problem, Anbox, was in an early development stage. It runs Android in a container, displaying Android apps in the Unity launcher.

    26. Re: It's easy by jezwel · · Score: 1

      There is a solution to that: It is called "being (mostly) compatible with an established API".

      This is why Win10 on ARM running Win32 'natively' could be disruption for certain groups. We've had some of our internal groups asking when we were going to be looking at this type of hardware to replace their PCs and mobiles. Myself I'm wondering my MS is taking so long to get product out.

    27. Re:It's easy by nnull · · Score: 1

      It wasn't exactly a stupid idea. It sold beyond their expectations. The lack of production models to sell to customers pretty much killed them. You went to the web store and you literally couldn't buy one. There was quite a lot of enthusiastic people that wanted one but couldn't get one.

      It was definitely a nice replacement for Android and IOS. If they bothered to get it onto the Meizu 6 (Which everyone was waiting for), it would have been fine. It's too bad now we won't ever see it again, which sucks, because I liked it. Piss poor management pretty much killed the Ubuntu phone, not the market.

    28. Re:It's easy by rtb61 · · Score: 1

      Nope. Quite simply Google was far better at marketing and good provided supplier pressure on manufacturers, enough to dominate the market with Apple, who are again extremely skilled marketers to come second. Why did Canonical fail, why did M$ fail, simply they could not stand up against Google and most important they failed to breach the upgrade market. Sick of Android on your phone, buy this USB stick, plug it into your phone and turn it into an Ubuntu phone (they should have focused on the cross grade market, rather than an entire phone, guaranteed to win the older phone market, the no longer upgraded phones, millions upon millions which are still floating out there and the ones that could cross grade to Ubuntu would be worth more on the second hand market).

      Choose the appropriate market, adjust your product offering to that market, market appropriately, get you foot in the door and leverage it for all you are worth to get the rest of you in.

      --
      Chaos - everything, everywhere, everywhen
    29. Re: It's easy by MichaelSmith · · Score: 1

      Unity made sense at the point when gnome decided dump their user base and start from scratch. Gnome is more mature now so it makes sense for Ubuntu to stop work on Unity.

    30. Re:It's easy by Anonymous Coward · · Score: 0

      existing players in the market would not allow ports of their apps.

      What does that even mean? What players? And what do you mean by "allow ports"? I'm sure there's a reasonable answer I'm overlooking.

    31. Re: It's easy by Anonymous Coward · · Score: 0

      Both apple and Android started somewhere.

      Yup. iOS started as an OS for a tablet before it was for the iPhone, and Android started when Eric Schmidt showed his pre-release iPhone to Andy Rubin.

    32. Re:It's easy by TheRaven64 · · Score: 4, Informative

      Remember when blackberry owned 100% of the smartphone market?

      Nope, I remember Nokia owning 76% of the smartphone market and Blackberry having most of the high-end corporate segment.

      --
      I am TheRaven on Soylent News
    33. Re:It's easy by TheRaven64 · · Score: 1

      When the iPhone shipped, other phones supported apps. There were a bunch of things that the iPhone couldn't do that existing Nokia phones did out of the box (SIP calls over WiFi, contact and calendar sync over Bluetooth, for example), but installing third-party apps was not one of the ones that users cared about. I'd installed a few apps on my phone when the iPhone came out, but I didn't actually use any of them (not even the Doom port) on a regular basis and the process for installing them was sufficiently annoying that most users didn't even try. There were basically no successful companies making smartphone apps and selling directly to end users.

      The world has changed. Smartphone app development is a large sector of the software market and most smartphone users have several third-party apps installed. One of the most common reasons for being locked into iOS or Android is the use of an app with no direct port on the other platform. That's a very different market to be entering than the one Apple found with the first iPhone.

      Or, to put it another way: The first iPhone (even with updated hardware) wouldn't stand a chance of competing against a modern iPhone or Android phone.

      --
      I am TheRaven on Soylent News
    34. Re:It's easy by TheRaven64 · · Score: 1

      there is a lot of user base, which wishes android was more open (not from the source licence, but from the development process and restrictions like locked bootloaders

      How many of these are unhappy with LineageOS? I use it, with a stripped-down version of Google Apps that installs the Play store (for the two apps that I actually use from there) and nothing else. Almost all of the apps I use come from F-Droid. Why would I prefer an Ubuntu phone over this?

      --
      I am TheRaven on Soylent News
    35. Re:It's easy by Anonymous Coward · · Score: 0

      https://www.blackdesertonline.com/

    36. Re:It's easy by Anonymous Coward · · Score: 0

      People hate microsoft already, but have had it crammed up their ass with the alternative being overpriced apple hipsterwear.

      Of course they don't want it on their god-damn-phone.

      Then why is Microsoft so popular on the desktop?

    37. Re:It's easy by enrique556 · · Score: 1

      Nokia? Smartphone? The?

      Nokias were _feature_ phones so blackberry kinda did have 100% of the smartphone market IIRC.

    38. Re:It's easy by JohnFen · · Score: 1

      Because people have a large existing investment in Windows applications.

    39. Re:It's easy by TheRaven64 · · Score: 1

      The definition of a smartphone vs a featurephone is usually that a smartphone can run third-party apps. Most of the Nokia phones had this capability (my N70 and N80 both did, for example), and could run C++ or Java apps. Unless you want to redefine smartphone to mean 'is a Blackberry', in which case RIM had 100% of the smartphone market.

      --
      I am TheRaven on Soylent News
    40. Re: It's easy by Anonymous Coward · · Score: 0

      Thanks for that comment, recollecting Symbian phones such as the N95, oh how the mighty Nokia has fallen, and how the world has forgotten, or perhaps how fake news has rewritten history (Apple making the first smart phone, oh noes, it was Blackberry...)

      aRTee

    41. Re:It's easy by Shirley+Marquez · · Score: 1

      Nokia did and did not have a big share of the smartphone market. On the one hand, Symbian (Nokia's smartphone OS) allowed the installation of apps. On the other hand, there weren't all that many apps available, and many users either installed no apps at all or stopped at one or two. So there was a large base of theoretical smartphones but few that were actually being used in a way that we recognize as smartphone usage; most were effectively feature phones despite the presence of smart features in the OS.

      Symbian had little presence in the US. That's in part because Nokia did not make the manufacture of CDMA-compatible phones a priority, and even their GSM phones often weren't offered in versions that supported the North American frequencies for mobile phones. Nokia phones were popular in the US in the 90s but faded away around the turn of the millennium, and most of the Symbian models were never offered here. Ignoring a key smartphone market was a bad decision on Nokia's part.

      There was also Palm/Handspring. (Handspring was a spinoff of Palm that produced Palm-compatible PDAs and then pioneered smartphone/PDA hybrids with their Treo line. They were later reabsorbed by Palm.) They never had a large share of the smartphone market, but theirs was the first platform that people used in a way that is similar to modern smartphone usage, including installation of third party apps. Samsung also made Palm-based smartphones.

    42. Re:It's easy by allo · · Score: 1

      The play store is the bad part of the gapps. It brings google play services, which are always active in the background, access your location if you haven't turned off location completely, can install packages without your consent and much more.

    43. Re: It's easy by Anonymous Coward · · Score: 0

      mmos arent phones. quit being stupid.

      And you're not an ant. Quit being stupid.

    44. Re:It's easy by Anonymous Coward · · Score: 0

      People hate microsoft already, but have had it crammed up their ass with the alternative being overpriced apple hipsterwear.

      No. Slashdot-esque geeks hate Microsoft, the vast majority of people are totally indifferent toward them. In fact most are completely indifferent to the operating system altogether. Windows provides broad hardware and software support, that is the *primary* function of the operating system and Windows does that best. Indeed there are a great many things that Linux and macOS do better than Windows but the primary purpose of an operating system is to run programs on your computer.

  2. Phone leveraged mainstream success of Linuxdesktop by JoeyRox · · Score: 1

    Yeah, not so much.

  3. Haha by Anonymous Coward · · Score: 0

    Sounds like Linux right now. Who cares if systemd is s steaming pile of shit and that route and ifconfig are now legacy. Those tools weren't broken and worked fine for decades.

    1. Re:Haha by allo · · Score: 2

      route and ifconfig always were shit.

      route had a horrible syntax. "ip route" now has a syntax which is almost proper english and you can always use the same command and swap add for del to remove the very same route.
      ifconfig and multiple ips on one interface ... ohh this new idea, who needs it? Lets call it eth0:1 instead!
      iproute2 is a nice idea.

      systemd on the other hand started with solving a few problems (dependencies of initscripts, cgroups to assign ressources and reliably detect running processes and kill them if they are not stopping) and grew to a horrible monster. Nobody would object a cool initsystem. I remember the old days, when systemd came around with fancy bootcharts and fast booting and everyone saw it as the next cool thing.
      But they did not know when to stop. If this is successful, let's add that, it will be successful as well and we're knowing what we're doing, aren't we?

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

      route was just fine "route add default x.x.x.x" how is that horrible?

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

      This.
      Never had a problem learning the syntax.

    4. Re:Haha by 93+Escort+Wagon · · Score: 1

      Why the hate on systemd? I LOVE having binary logs I can't easily parse!

      --
      #DeleteChrome
    5. Re:Haha by bn-7bc · · Score: 0

      Yes the if:x notation to get multiple ipv4 adresses on an interface have allso struck me as starnge, pesonaly I suspect it originaly was done duoe to pacwards copatibility. when ipv4 originaly was designed the propaply did not see a need for multiple addresse on a single if, yime moved on and the need came (multiple https hosts on a single network connection (before SNI)) , noone wantetd to change evry bit of code in the ip stack thed delt with interfaces and ipv4 adresses so they just added a sub interface and reused evrything else. This is just a guess on my part but since this is no longer needed in ipv6 (heay add as many adresses as you want on an interface) it seems to me that it has to be som historical reason for it when we talk about ipv4. Caveat; I'm not a developer so I may (and probably am) way off, if you have more knowlage of the matter than me and hav the inklination to inform me and other readers of this thread, pleace do so

    6. Re:Haha by allo · · Score: 2

      this was the most common (and an easy) command. Did you ever do something more complicated?

    7. Re:Haha by exomondo · · Score: 1

      Why the hate on systemd? I LOVE having binary logs I can't easily parse!

      Can't you just convert them to text files then? I'm not familiar with systemd but I would be surprised if you couldn't convert binary log files into plain text log files.

    8. Re:Haha by dbIII · · Score: 1

      Not when the thing is hung up and needs to be booted off CD or something and then you look at the logs to see what happened last time. The problem appears to be more logging interval (ie. no logs for your fault at all).
      However, it's kind of stupid IMHO to have log files you can't read with simple tools. Yet another example of the different perspective from developers who grew up with MS Windows.

      It's just one of a laundry list of reasons it annoys people - the real problem is feature creep before getting the core of it right. Give it a few years after it stops creeping and there may not be anything to complain about.

    9. Re:Haha by exomondo · · Score: 1

      So assuming you can't just convert them (systemd doesn't include such a tool to read/convert log files?) could you not just augment systemd to output the same data to a text file as it encodes in the binary file? It's all open source.

    10. Re:Haha by dbIII · · Score: 1

      If you can employ a team of developers to do a fork, then yes, but it's easier to either still use it and hope it improves or use the earlier alternatives that it has yet to match.

    11. Re:Haha by dbIII · · Score: 1

      So assuming you can't just convert them

      Not really the issue at this point - a binary log of the event that actually exists is good enough, if annoying, but text based logs on the earlier systems which can append to log files are currently getting the job done better than systemd. Logging kind of still sucks despite having been deemed "good enough" and the binary nature of the logs has often been pointed out as one case of the very different mindsets involved. You've got to be very careful to make sure that nothing can cause a race condition to a binary log and make the entire thing unreadable. Lennart is not exactly a careful sort of guy so that bit of unneeded juggling with chainsaws keeps getting pointed out as an example of systemd being not the sort of init system some people want.
      Personally I'm biased due to the rushed implementation of it on CentOS7 breaking a few things - I don't think users should have to unplug their mouse if they want their computer to boot among a few other systemd implementation glitches at when that distro was new. With some of them I had utterly no idea what happened due to the logging halting before the problem, and others I had to backtrack to the problem via other means - disabling services one by one until it worked.

    12. Re:Haha by JohnFen · · Score: 1

      and grew to a horrible monster. Nobody would object a cool initsystem.

      A million times this.

      If systemd were just an init system, I could get on board.

    13. Re:Haha by exomondo · · Score: 1

      Im not suggesting a fork, just a patch of a couple of lines that you could apply to redirect logging to a text file. You dont need a team for that.

    14. Re:Haha by dbIII · · Score: 1
      The logging is a bit of mess due to being given a very low priority so no, a little more than that, especially since what little you get can be output as text in the end anyway (if the fault isn't something that hangs systemd before it logs that is). The poster way above was just dumbing down the problem by stating "I LOVE having binary logs I can't easily parse". The problem really is having enough logging to make it worth parsing the logs in whatever form they happen to be - stuff vanishes before being written when things really mess up in some distros with systemd. From Lennart:

      the journal is configured by default to store logs only in a small ring-buffer in /run/log/journal, i.e. not persistent. This of course limits its usefulness quite drastically but is sufficient to show a bit of recent log history in systemctl status

      On the positive side they have been fixing things, but they seem to still be creeping in scope faster than they can fix what they have.

    15. Re:Haha by dbIII · · Score: 1

      Im not suggesting a fork, just a patch of a couple of lines that you could apply to redirect logging to a text file. You dont need a team for that.

      I posted a few times but wasn't really clear enough - there already is stuff like that (that took a hell of a lot more than a couple of lines) from third parties who came in to clean up that little bit of Lennart's mess from outside of systemd.
      It's a mindset difference - to Lennart it's perfectly OK to expect the user to type in "journalctl -b" on a running system to read a log instead of providing a log file that someone can read after booting from other media if they want to find out why the system wasn't starting up, and also he sees a few things that would normally be logged as not so important (hardware faults are not so important if your objective is developing code). He spent all that time writing a snazzy little log reader as a cool and trendy bit of development work instead of doing something very simple and more useful when things actually go wrong. When questioned about it his response was "We are writing an OS here for the general purpose, not just a toy for a clique of kernel developers." So it's done, he's moved on, he doesn't want to change logging so its either has to be done from the outside (which works to an extent) or a fork adding a lot more functionality in that area.

    16. Re:Haha by exomondo · · Score: 1

      This really does seem like a fundamental problem with the community or development methodology. If one person can completely upend the system to the point where it requires a team of developers to make something like logging work again that is a very bad thing. I hate to think about the myriad of other things that would end up in the "too hard" basket if somebody or some corporation decided to go in a different direction.

    17. Re:Haha by dbIII · · Score: 1

      Not exactly "one person" - one person with RedHat completely and firmly behind him - and even then others have chipped in to get syslog to poll Lennart's logging system to produce readable files that can be used even if the system won't start so it's not all bad.
      The other distros just don't have the resources so accept whatever work RedHat does.

    18. Re:Haha by exomondo · · Score: 1

      Well I always see the sort of thing that you wrote, that it's all Lennart's fault, not RedHat. Regardless it means the desktop Linux community is controlled by corporations like RedHat because, as you say, the distros do not have the resources to actually maintain themselves without RedHat.

  4. Want the list? by Voyager529 · · Score: 4, Insightful

    1. Not solid through US carriers.
    2. Focus on low cost hardware; no "flagship phone".
    3. Primary benefits were ideological; no new features or distinction over incumbents.
    4. No integration with a movies/music/tv ecosystem.
    5. Practically no existing market to leverage.
    6. Dependency on browser over App Store model.
    7. No focus on a migration path. ...so yeah, there were seemingly no advantages and lots of disadvantages to moving.

    1. Re:Want the list? by Anonymous Coward · · Score: 0

      2. Focus on low cost hardware; no "flagship phone".
      4. No integration with a movies/music/tv ecosystem.
      6. Dependency on browser over App Store model.

      Not all of those are disadvantages. Well, for me anyway.

    2. Re:Want the list? by freeze128 · · Score: 1

      Regarding #3 - Why does *EVERY* new phone need to have new features? I would be perfectly happy with a cell phone ecosystem that doesn't constantly change all the time. Two year lifetime of a cell phone doesn't seem to be enough.

    3. Re:Want the list? by Anonymous Coward · · Score: 1

      They already have a cell phone for people like you. It's called John's Phone.

      http://www.johnsphones.com/store/johns-phone-bar/item46

    4. Re:Want the list? by OzPeter · · Score: 1

      They already have a cell phone for people like you. It's called John's Phone.

      http://www.johnsphones.com/store/johns-phone-bar/item46

      I want one just for the sake of having it!

      --
      I am Slashdot. Are you Slashdot as well?
    5. Re:Want the list? by Anonymous Coward · · Score: 0

      8. The name was gay.

    6. Re:Want the list? by Darinbob · · Score: 1

      Look at the summary, it's biased already. "Developers were not concentrating on fixing them", with regards to bugs. Developers work on what they're told to work on. There's a management failure here of not setting the right priorities and not putting in gatekeepers to make sure they're being paid attention to. I don't know of any developer that gets the chance to ignore the stated priorities and instead spend the day working on more fun stuff without getting laid off when the company finds out.

    7. Re:Want the list? by murdocj · · Score: 1

      I'm confused... my Android phone was a somehow old model when I bought it over a year ago, and I expect to have it for a couple of more years. If I don't screw around with it I don't expect it to degrade. Why would it be limited to a 2 year lifespan?

    8. Re:Want the list? by Voyager529 · · Score: 2

      Regarding #3 - Why does *EVERY* new phone need to have new features? I would be perfectly happy with a cell phone ecosystem that doesn't constantly change all the time. Two year lifetime of a cell phone doesn't seem to be enough.

      You missed the point entirely.

      I agree that the continual rearrangement of furniture in the Android market isn't exactly a 'feature'. However, the point was that the Ubuntu phone needed a differentiator other than "open source OS" to differentiate it from iOS and Android, if it was going to give people who already own a smartphone a reason to switch. "It's cheaper" wouldn't be it, because cost-sensitive customers can already get sub-$100 Android phones already, either through low end units from the carrier, or by getting "last season's" hot phone in the secondary market. Ubuntu doesn't have an ecosystem to leverage in the same way Apple leveraged the iTunes Music Store to create incentive when the iPhone was first released, so that wouldn't help.

      I'm not talking about the Galaxy S-series phones needing a new gimmick every year to the point of regression, I'm saying that if Ubuntu wanted to make inroads, there needed to be something superior to what existed at the time. With no apps, no music/movies, no hardware specialties, no incumbent market to leverage, and no carrier deals, it was DoA. Microsoft had millions of dollars, an overconfident CEO, a history of industry strongarm tactics, the Nokia name and hardware, and the Zune/Xbox ecosystem, and *they* couldn't get a half decent market share.

    9. Re:Want the list? by u801e · · Score: 2

      1. Not solid through US carriers.

      Why would that have to even be a requirement? People can buy other types of computing devices online and start using them. An unlocked GSM phone could work the same way. Order online, install the SIM, and start using it. The fact that people want to get phones through their carriers is the major reason why the cell phone market in the US was so far behind the rest of the world in terms of device features and capabilities until the iphone came along.

    10. Re:Want the list? by Anonymous Coward · · Score: 0

      Best part!

      The back of the phone features a small opening with an address book and pen

    11. Re:Want the list? by epine · · Score: 1

      "Developers were not concentrating on fixing them", with regards to bugs.

      You say tomahto, I say tomayto. You see inaccurate attribution, I see accurate observation.

      Relationships where observations can't be stated before taking on the burden of sorting out attribution are all but guaranteed to make the kitchen fridge cringe.

      If you can't separate the two, you can't agree to agree on the problem while agreeing to disagree on the solution, for the time being. Since "the" solution almost certainly involves personal change, there's simply no possibility you're obtained agreement on that front in a fifteen-minute raging kitchen bar fight.

      You are so screwed ... until the make-up sex doesn't work any more.

    12. Re:Want the list? by JohnFen · · Score: 1

      Yep. My phone is now 3 years old and going strong. I see nothing existing now or coming in the foreseeable future that makes it "obsolete" to me.

    13. Re:Want the list? by JohnFen · · Score: 1

      The fact that people want to get phones through their carriers is the major reason why the cell phone market in the US was so far behind the rest of the world

      Well, it's a major reason, yes. I agree. And I am constantly surprised by the number of people who don't even realize that it's possible (and easy) to buy a phone from someone other than their carrier.

      People are also fooled by the apparent economics of it. The contracts are arranged so as to make you think you're getting your phone super cheap through your carrier, when you're really overpaying fairly significantly. I understand if you can't come up with the full purchase price of the phone, I suppose, but it's yet another example of how being poor is very expensive.

  5. Who could've seen this coming? by Anonymous Coward · · Score: 1

    Linux was a successful exception to this type of effort for ONE reason: it was drop-in compatible with its competition. Linux was user-installable on commodity PCs that people already owned -and- it ran Unix, a popular OS that already had applications and a technical user base that was used to making tweaks to enable their apps to run on various Unix flavors. Linux was just another flavor.

    -nomsh

  6. They were just as shitty by Anonymous Coward · · Score: 0

    Nothing has really improved; it's all just gotten a different interface.

  7. people don't want crappy phones by Anonymous Coward · · Score: 0

    Us computer nuts have put up with a lot of crap across the years, but that's part of the appeal of our interest. But phones are for ordianary people, or people who at the moment of using the phone want just an ordinary sane experience. What I'll put up with on my computer, for instance, I'd never tolerate on my phone.

    So Microsoft and Linux phones were really stillborn. And who, with at least one working braincell, is suprised at this fact.

    You wanna mess around anyway- Andorid phones give you the power. You want the walled garden experience, you go Apple. A rubbish third option ain't needed or wanted.

    Anyway the main figures behind Linux are mentally unbalanced, and you wouldn't want to bump into any of them in a dark alley. Mostly mediocre coders with egos the size of planets, and zero people skills. The very opposite set of characterists needed to work on that most social of devices that just needs to work without excuses.

    PS I use a lot of open-source/free software on windows. Sometimes a really pathetic (and easy to rectify) bug has me search the dev forums- where I am horrified to see reports of said bug literally years back- and the devs telling the users to go eff themselves. As a happy but informed user of this type of software I just shrug- understanding the psychological issues the devs have- but psychology makes them 100% unsuited for working on devices like phones.

    1. Re: people don't want crappy phones by Anonymous Coward · · Score: 1

      To be fair, the difference between closed source and open source in that respect is that the open source guys will tell you, the closed source guys just won't bother fixing it.

    2. Re: people don't want crappy phones by BarbaraHudson · · Score: 1

      To the closed-source guys, it's a feature - it makes it easier to sell the next version (which may or may not fix the bug that annoys you, but that uncertainty never stopped people from buying it). And the new version will be "improved" by splitting off some existing handy features into a new "premium" "enterprisey" version, because "professional" doesn't mean what it used to.

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    3. Re: people don't want crappy phones by KGIII · · Score: 1

      I don't know, but I am pretty sure I can take Linus in a fight, dark alley or not. His wife, on the other hand...

      --
      "So long and thanks for all the fish."
    4. Re: people don't want crappy phones by murdocj · · Score: 1

      No

  8. Why do we care what he's up to now? by Anonymous Coward · · Score: 0

    Raffeiner says, for example, that "despite so many bugs being present, developers were not concentrating on fixing them, but rather on adding support for more devices." But he says he doesn't regret the time he spent on the project -- though now he spends his free time "traveling the world, taking photographs and creating bad card games, bad comics and bad games."

    Is this a story on the failings of the Ubuntu Phone project or how cool this person thinks they are now. Who fucking cares if they're now some instagramming douche bag.

    1. Re:Why do we care what he's up to now? by Zontar+The+Mindless · · Score: 1

      I think he's probably allowed to talk about himself in his own blog.

      --
      Il n'y a pas de Planet B.
    2. Re:Why do we care what he's up to now? by BarbaraHudson · · Score: 1

      At some point we should acknowledge that many people have quit the field over crappy projects that have left a permanent bad taste in their mouth, one job after another with sociopaths for managers or leaders, barely tech-literate "managers" who keep on insisting that the time to do something can be negotiated down without consequences in terms of quality, contradictory requirements, the cult of featuritis even when (not if) it damages the product, lack of a sense of being valued, shitty work environment, and less stressful or more fulfilling opportunities elsewhere.

      Even geeks and nerds eventually outgrow all the crap and want a real life. ("outgrow" in the sense that putting up with the bullshit for one more day will send them postal). Eventually the instinct for self-preservation kicks in.

      So the guy has found something else to do that he enjoys ... we need more stories that show that "yes, there ARE other options, and you may enjoy one of them more".

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  9. Features over stability has always been Ubuntus... by Anonymous Coward · · Score: 0

    way of working. What differs that from this?

  10. Re:Free market at work by Zontar+The+Mindless · · Score: 3, Funny

    You're basically another APK, only with (slightly) better punctuation.

    --
    Il n'y a pas de Planet B.
  11. Not a total loss by ISoldat53 · · Score: 4, Funny

    It can always serve as a bad example.

  12. Re:Free market at work by BarbaraHudson · · Score: 1

    But are the resources all that scarce? Seems to me we've gone from "on the internet nobody knows you're a dog" to "on the internet even your dog can be a 'developer' ".

    Resources get tight when you want someone to work on your for-profit project for free or at below-market rates. That's entirely normal - the previous hype of all things computer-related is over.

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  13. no he doesn't by ooloorie · · Score: 1

    "despite so many bugs being present, developers were not concentrating on fixing them, but rather on adding support for more devices."

    That's not why it failed. It failed because there was next to no demand.

    1. Re:no he doesn't by Chris+Mattern · · Score: 1

      That's not why it failed. It failed because there was next to no demand.

      Well, duh. That's why every new product failure fails: nobody buys it. The question is: why didn't anybody buy it?

    2. Re:no he doesn't by ooloorie · · Score: 1

      I'm sorry, let me spell it out: there was no demand for this kind of product. That is, people didn't buy it because it was a bad product, people didn't buy it because it was the wrong product.

    3. Re:no he doesn't by Anonymous Coward · · Score: 0

      > That is, people didn't buy it because it was a bad product, people didn't buy it because it was the wrong product.

      That's switching the definitions. Bad in this context means the some bad combination of product characteristics, quality, value (i.e. wrong product).

  14. Drivers and Compatibility was the Failure by Anonymous Coward · · Score: 0

    The Linux Nokia N900 and Sharp Zaurus used regular x11, you could compile desktop ARM Linux stuff pretty easily or chroot.
    Ubuntu Touch used a screwball OS and never got convergance working, it was worse IMHO than even Cyanogen which was not GNU Linux but at least you can install APKs and get some mainstream functionality. No x11, no pulseaudio or ALSA, no apt or rpm; it was a forever weird broken os which resembled the Ubuntu color scheme. And with the dearth of usable apps there was no wine like compatibility to install an APK to run a dirty Android bin app.
    Ubuntu Touch, I really tried but it was not suited to hacking, useful for only the most simple web browser only noob or the most godlike intuitive code hacker; though what a $#!t platform to be stuck on.
    I soldier on with an old N900 and an up to date bluetooth tethered tablet running LineageOS and Fdroid repos(no google anything but some APKs from APKmirror). I don't have a better solution, and I feel like we are farther from a good hackable mobile OS than ever before in the era of mainstream pocket computing.

  15. Thought it was lack of interest by Anonymous Coward · · Score: 0

    I thought it was lack of interest from any big hardware, app developer, or end user that killed Ubuntu mobile. Seriously you only have a small percentage of PC users running Ubuntu, how do you expect to sell a lot of smartphones with a OS most consumers don't even recognize?

    1. Re:Thought it was lack of interest by careysub · · Score: 1

      When you put it that way - being buggy cr@p was just icing on the sh|t cake.

      --
      Starships were meant to fly, Hands up and touch the sky - Nicky Minaj
  16. Yes and No by allo · · Score: 1

    Who cares about a bug free system, when there is only one crappy phone, where it works? Of course, the bugs should not be too extreme, but still adding hardware support has a priority as well. And bugfree systems are rare. Have a look at the mozilla bugtracker. And there are many serious problems, ten year old platform bugs and so on. But firefox mostly works and that's the important part. Abitious projects do not have the ressources to do everything perfect. And there are always more new bugs than fixed ones. If you're in a market as mobile phones or browsers, you need to keep up with features. HTML5 gets new features like every month. So when do you have the time to fix the minor bugs of the feature from a year ago? You start doing so, when people actually care and report they are having big trouble with them. Or when you got a bit of spare time. But now while the users are complaining, that netflix runs slower as it does on chrome.

  17. Linux's core problem. by petes_PoV · · Score: 1, Insightful

    "despite so many bugs being present, developers were not concentrating on fixing them, but rather on adding support for more devices."

    This could be a generic description for Linux in general. It is hard to get people who volunteer their time to do work (or is it really play?) on things they don't want to.

    Writing new stuff is fun. People will do that. Fixing bugs is hard work. It requires effort and thought and understanding. You can't persuade people to give up their time to do that, it's not fun.

    --
    politicians are like babies' nappies: they should both be changed regularly and for the same reasons
  18. Probably the same reason why Windows phone failed. by Casandro · · Score: 1

    ... you couldn't run the programs on it you expected from the platform. It could have easily attracted a market of more professional users if it wouldn't have tried to copy iOS and Android.

    There is a market for something like the communicator with modern hardware. Essentially a device which on the outside is a regular phone, and once you fold it up becomes a portable computer, complete with keyboard.

    The market for portable devices with an app-store is already full. However for some reason both Canonical and Microsoft are chasing it on both the portable and the desktop side. Both fail doing so, even though Microsoft should have known better since its Windows CE had a far greater market share than Windows Mobile.

  19. another problem: it was touch-only by Miamicanes · · Score: 1

    Another problem with Ubuntu's phone OS: its UI bought into the militantly-fashionable idea of eliminating all physical buttons & reducing the phone to a touchscreen for literally everything UI-related. From what I recall (circa summer 2013, at least), it didn't just ignore things like volume buttons for the OS's UI... it didn't even have an API for thirdparty APPS to read their state or react to button-state changes. It was insane.

    It's the same reason why Android & IOS (and Windows Mobile & PalmOS before them) never became popular alternatives to universal remote controls, even though everyone has a drawer full of old ones begging for some meaningful repurposed use at this point. A well-designed remote allows you to grope blindly, pick it up, and (at the bare minimum) raise & lower the volume, toggle mute, and pause/play/skip by feeling the shape of the buttons alone. An app that forces you to divert your full attention to its UI egregiously violates user expectations, and basically sucks to use. It's also why so many people have bought a Roku or Kindle Fire instead of a (slightly-cheaper) Chromecast... having touchscreen-control as an OPTION might be nice, but having it rammed down your throat as the ONLY way to control a device results in a miserable use experience.

    1. Re:another problem: it was touch-only by Hognoxious · · Score: 1

      Another problem with Ubuntu's phone OS: its UI bought into the militantly-fashionable idea of eliminating all physical buttons

      Is it fashion? I always thought it was cost-cutting.

      The effect's the same though. It's like an input method version of Gresham's law - a touchscreen will always drive out other devices.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    2. Re:another problem: it was touch-only by acrimonious+howard · · Score: 1
      This. I want more buttons not less.

      But if it were me, I would have repurposed the cheapest existing phone on the market. Try to get the price point as low as possible, and expect the market to be completely niche. Write code to make the phone work with a little polish for only the most basic needs, and let people make their own apps to do the rest. Spend as little money as possible on the project, and have everything open source - both aimed to guarantee that it never dies. Expect it to take a long time to gain any momentum. But I guess this sounds like more like a philanthropy project for the greater good (I want a secure linux phone instead of Android and don't get me started on apple).

    3. Re:another problem: it was touch-only by Miamicanes · · Score: 1

      Years ago, I had similar thoughts about PalmOS 6. Instead of flailing around trying to convince US carriers to offer a phone of unknown value running PalmOS 6, they should have worked with HTC to make it available as a consumer-reflashable guerrilla update for the HTC PPC-6700 (Sprint)/XV6700 (Verizon) (and whatever the GSM cousin of that particular model happened to be). I'm not sure about AT&T/T-Mobile/GSM-land, but I remember that the 6700 was one of the most popular "PDA Phones" *ever* offered by Sprint & Verizon. They would have probably lost money for that *year* & would have probably had to pay HTC a serious amount of money and offer them perpetual best-deal licensing rights for PalmOS going forward, but it would have given them a real shot at jumpstarting the PalmOS developer and software ecosystem (which had been languishing badly for about a year at that point).

      Hardware-wise, the 6700 wasn't much of a step down from the next year's phones... the next year's models were thinner & had more flash, but from what I recall, the RAM and CPU speed were basically the same.They definitely had bluetooth, wifi, and a camera, and I'm pretty sure they had the hardware onboard to do real GPS, too (never officially supported, but existing as a latent [albeit buggy and poorly-working] ability on the circuit board that HTC just ignored... from what I read, the GPS radio got overloaded by the CDMA/GSM modem when it polled the tower, HTC's engineers came up with a firmware fix that basically had the user manually trigger location updates that took the radio modem offline for up to a minute, but HTC's management nixed it because they decided no GPS at all was preferable to flaky GPS that only worked under specific & fairly ideal conditions). Worst-case, they would have had to put most of PalmOS on a miniSD card & required that the card remain inserted (or unceremoniously crash, if the user removed it anyway).

  20. Missed opportunity in B2B by MoleStrangler · · Score: 1

    I approached the (then) product manager responsible for the OS and proposed a fork in their route-to-market. My pitch was to create an OS for devices built for industry that were being sold running Microsoft® Windows Embedded Handheld 6.5 & Microsoft® Windows® CE and are still be actually sold today.

    At the time companies developing and selling devices were not investing in developing new MS mobile OS devices cuz the OS is long dead and the cost of creating new platforms (they still sell device platforms that are more than 6 years old). Also MS Windows Phone was consumer focused completely cutting out the industrial sector.

    So they were stuck in limbo with regards to a viable mobile OS.

    So I pitched the idea of approaching these companies with the idea of creating a common OS to get around their legacy issues, cuz at the time they were just dipping their toe into Android, and security back then was an afterthought for most.

    Talk about not knowing anything about their broader target market, it seemed to me the guys making the decisions were hoping to copy what Apple & Google did, slap a Unix label onto it and they would had a hit on their hands. Without any real depth of knowledge about the wider mobile market.

    The mass-market consumer doesn't buy Unix, its a niche market (still) outside business.

    iOS is Unix underneath but Apple (very wisely) keep that hidden and point the consumer at the shinny features and eye candy. They talk about iOS and give consumer friendly names to stuff like 'Metal' etc...

    But if you think about it, that's exactly what Ubuntu is really, yer they build some stuff along the way but nothing substantial. Don't get me wrong I use Ubuntu regularly and its my preferred distro. But it takes different skills to build something new.

  21. You're unquestionably a "ne'er-do-well" by Anonymous Coward · · Score: 0

    You're a "ne'er-do-well" Zontar The Mindless (good name for you). A do nothing zero douche (& you know it, loser).

    * Don't you have anything better to do, loser? Apparently not. Makes sense though - you have zero skills & zero to show for yourself...

    APK

    P.S.=> I love when you provide me the opportunity to shoot your lame ass down, lol - thank you! apk

    1. Re:You're unquestionably a "ne'er-do-well" by Zontar+The+Mindless · · Score: 2

      I love the fact that you have no other purpose in life than to scan Internet forums for occurrences of your initials, and knowing that I can summon you up anytime I want just by inserting them into a post. It's like the master whistling for his dog. HAND.

      --
      Il n'y a pas de Planet B.
  22. Have you tried turning it off and on again by Hognoxious · · Score: 1

    Are you a sysadmin? That'd be a pretty convenient excuse. "Well I would fix it, but ...".

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  23. It makes joe_dragon look like Robert M. Pirsig. by Hognoxious · · Score: 4, Funny

    starnge, pesonaly [...] duoe to pacwards copatibility. knowlage [...] hav the inklination

    I'd run that through babelfish if I knew what language it was supposed to be.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  24. Why Ubuntu Phone project failed? by najajomo · · Score: 1

    "A developer who worked with the Ubuntu Phone project has outlined the reasons for its failure"

    Ubuntu Phone failed because Canonical failed to engage with the developers and didn't do a deal with the telecoms to provide a rich user experience. Like apple did with the original Apple Phone Demo.

  25. Too slow in execution by Gojira+Shipi-Taro · · Score: 1

    From the start of the project, they were a bit behind Android. By the time there was a "product" (to be generous), it was far too late for a new player in the market. The android and apple markets were far too well established. They stood less of a chance than Blackberry did.

    --
    "Oh my God. This is terrible. This is the end of my Presidency. I'm fucked."; ~ Donald J. Trump
    1. Re:Too slow in execution by Anonymous Coward · · Score: 0

      It's almost like even a "free market" can only support a few basic designs or ecosystems because you need critical mass to be successful. So even with a better product (not saying this was) it is extremely difficult if not impossible to gain entry let alone compete. It's almost like an unregulated market always favors large companies who can afford to be the first entrants. We used to have a word to describe that, but of course it's not spoken in American economics classes anymore...

  26. Re: It makes joe_dragon look like Robert M. Pirsig by KGIII · · Score: 1

    Swahili, I'm pretty sure.

    --
    "So long and thanks for all the fish."
  27. Re:Free market at work by Anonymous Coward · · Score: 0

    The resource that is scare in this case is CASH.

  28. Re:Features over stability has always been Ubuntus by careysub · · Score: 1

    Exactly.

    Ubuntu being Ubuntu, Shuttleworth being Shuttleworth. T'was ever thus.

    --
    Starships were meant to fly, Hands up and touch the sky - Nicky Minaj
  29. Proof you're a druggie loon (from you) by Anonymous Coward · · Score: 0

    1st take your meds mentalcase https://slashdot.org/comments....

    &

    I see you're also a druggie too https://slashdot.org/comments....

    Going to make more sockpuppets to stalk & troll me with you loon https://slashdot.org/comments.... ?

    +

    Your sending me postcards with threats too https://slashdot.org/comments.... ?

    * You're a butthurt loon freak, plain & simple... you did it to yourself, loser...

    You're from SWEDEN the land of UBI slavery, which IS all that result from it, witness your "no go" zones w/ Muslims RAPING your women https://www.google.com/#q=Sweden+and+muslim+rape (you're all "not men" there, punk)).

    APK

    P.S.=> Still trying to live down how I shot you to pieces in the art & science of computing Mr. Butthurt https://slashdot.org/comments.... ?

    How about proving hosts & my program that builds them are useless too https://slashdot.org/comments.... ?

    See subject above - They're FACT & your fails made them so, lol!

    (I've done all that LONG ago & you haven't done squat of note... must hurt like hell, that truth, or you wouldn't be stalking me like the loser druggie mental loon you're proven to be in YOUR OWN WORDS in those links above, lol)... apk

    1. Re:Proof you're a druggie loon (from you) by Anonymous Coward · · Score: 0

      Give it up, dude. You were owned ages ago.

  30. Stopped because M$ told them too by Anonymous Coward · · Score: 0

    You know I'm right.

  31. Use existing hardware? by John.Banister · · Score: 1

    Usually one big problem I see with these projects is that it's difficult to both build a phone OS and come out with hardware at a manufacturing scale that allows selling the hardware people want at a price people can afford. Sony has some decently nice hardware involved in their Open Devices project. HTC also has released kernel source code. Maybe it would be valuable to bring the new OS first to one of these devices that already has market share and look into building mobile phone hardware later on in life.

    1. Re:Use existing hardware? by ChunderDownunder · · Score: 1

      Yes, it's hardly inspiring to plonk down 300euro (or whatever they were charging) for beta-level software on a Meizu or a BQ - I mean honestly who had heard of these manufacturers before? Using company money to purchase one as a developer device, perhaps, but for consumers to buy one for use as a daily driver, only the very keen.

      Sailfish's collaboration with Xperia seems interesting if Sony would do the legwork to assist in porting the OS to each and every device. That way the curious can buy an off the shelf phone with the option of reverting to stock Android if they please.

    2. Re:Use existing hardware? by John.Banister · · Score: 1

      I'm not sure Sony has to do the legwork if they provide access. If the people at Jolla are competent at writing software, porting shouldn't be too difficult for them. I think it's very cool that Sony is providing the access.

  32. Failing to learn from Microsoft's Mistakes by Prien715 · · Score: 1

    Remember how much we love how Microsoft decided to make a common interface across all platforms and resulted in making the Windows interface (particularly the now-usesless start men) worse? Mark Shuttleworth must have thought to himself. "You know, that strategy is absolutely going to work for Microsoft. And while we have neither the desktop market or the smartphone market, let's try it!"

    (And, as a guy who does UI work from time-to-time over a decade... Hundreds of apps that use Qt, but how many use QML? I remember when QML was introduced and thought to myself "Peope only use Javascript because it's the only language web browsers understand. Almost every desktop application on every platform is written in a type-checked compiled language for a reason -- catching more errors at compile time is a Good Thing (TM).. Why do I want to introduce Javascript into my perfectly good C/C++ code?")

    --
    -- Political fascism requires a Fuhrer.
  33. No one needed it... by BrendaEM · · Score: 1

    The Ubuntu phone was a me-too thing. No one asked for it, wanted it, or bought it.
    And yet, Ubuntu ran their game into the ground supporting Unity, and for what?

    Let this be a lesson to all the me-too, flash-in-the-pan bullshit instigators.

    --
    https://www.youtube.com/c/BrendaEM
    1. Re:No one needed it... by Anonymous Coward · · Score: 0

      Worse: They threw away most of the community chasing that pipe dream. :(

      p.s. If anyone reading this is a time traveler planning on going back to 2009, please stop Unity before it happened. Thanks.

    2. Re:No one needed it... by Anonymous Coward · · Score: 0

      Doesn't pretty much everyone on Slashdot want a phone you can compile and run arbitrary open source code on?

  34. Leverage an existing market need... by Anonymous Coward · · Score: 0

    There is still no really viable small pocketable linux tablet available (for years now!) surely that would have generated support from a very interested group of hobbyists who would love such a thing and would then help develop it.
    It could be cheap and fast to develop, (as in, it's not a phone!) and it would not even matter if the system on it was not highly polished just so long as it works, as it's users would probably improve it quite quickly.
    4core 1.4ghz 2gb 4000mah otg usb $200 would be nice

  35. Openmoko by MichaelSmith · · Score: 1

    Reading the article it sounds like the openmoko all over again

  36. creating bad card games, bad comics and bad games by Anonymous Coward · · Score: 0

    > he says he doesn't regret the time he spent on the project -- though now he spends his free time "traveling the world, taking photographs and creating bad card games, bad comics and bad games."

    I understand self-deprecation and all that, but does he ever think he might also be responsible for the oh-so-many bugs he mentioned didn't get fixed? That's not the tone I'd use if I was talking, in hindsight, about a failed project.

  37. Poor execution, poorly thought out by Anonymous Coward · · Score: 0

    That's it, really.

    I tried it. It was horrible. The idea we were sold on was an Ubuntu desktop OS on the phone.

    Then it became a JS-app enabled smartphone-light experience

    Then when the preview builds and RTMs came out I tried those. They were... unusable. I don't know what they were thinking.

    Ubuntu on a phone wasn't an inherently bad idea. If they stuck with native apps, or did the app model better, got some big players like FB/Twitter/etc onboard in the beginning, which wouldn't have been hard to do, they'd be in a much better position.

    They would still have had an uphill battle, but when those stunningly bad early builds came out they weren't even good enough for a daily driver. I couldn't leave them on my phone. They left me cut off from EVERYTHING I do on my phone. No good!

  38. My daughter dropped her Ubuntu tablet by fonske · · Score: 1

    ...and it's still working thanks to convergence. She even started to appreciate the desktop experience ;-)

  39. Re:Probably the same reason why Windows phone fail by david_thornley · · Score: 1

    It could have easily attracted a market of more professional users if it wouldn't have tried to copy iOS and Android.

    Which was basically RIM's idea to stay relevant with the Blackberry. Provide professional-level services (whatever they are) and sell to businesses. Microsoft couldn't have won that way either.

    --
    "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  40. Re:Free market at work by BarbaraHudson · · Score: 1

    The resource that is scare in this case is CASH.

    A shortage of cash for shit projects? I wish that were true, but SillyValley proves otherwise. This won't attract any more funding only because it's way shittier than most. At some point, sanity begins to push back.

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  41. He's not really the problem by dbIII · · Score: 1

    If it was only him it would be just one of a few choices of sound system and init systems with nobody bitching about having his ideas on what linux should be forced upon them.
    We can't blame him especially for his early stuff - RedHat management have plenty of options about who they can have running their projects - it appears he impressed them with his "vision" of not being content with just an init system like the upstart people were doing, but an entire takeover of linux and a change to an MS style environment (as you can read on his blog). Without RedHat he's just a guy with ambition who would have to "play well with others" - with RedHat he can act as he has acted. For example, the "if you want gnome you need to have systemd" deal could never have happened without RedHat behind him.
    It's one of the reasons I migrated a lot of stuff to FreeBSD (I haven't seen linux crash so much as it has with recent distros - not even in 1995 on the bleeding edge) including now a couple of desktop systems and a laptop.