Slashdot Mirror


Drawing the Line Between Android and Linux

jfruhlinger writes "The relationship between Linux and Android is on a technical level not hard to grasp — there's a shared kernel, but the application and interface layers are quite different. But, as Brian Proffitt points out, there are differences of philosophy and of community — which hasn't stopped Adobe from touting its Android dev tools as proof of its devotion to Linux."

168 of 258 comments (clear)

  1. Yupp by Anonymous Coward · · Score: 1

    KERNEL.DLL and MS-Windows are also the same thing!

    1. Re:Yupp by u17 · · Score: 1

      That's GNU/Kernel.dll, mister!

  2. don't know by justsomebody · · Score: 2, Insightful

    android didn't do anything good for linux, if anything it just made another incompatible implementation of the same platform. wake me up when i can run android app on my linux desktop without needing to run it in some virtual machine.

    adobe i don't even wanna comment about. i avoid them more carefully than entrance to hell.

    --
    Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    1. Re:don't know by h4rr4r · · Score: 4, Insightful

      You do realize that android apps run in dalvik right? So there is always a virtual machine. I fail to see how that is any different than running it on the virtual machine running on the phone.

    2. Re:don't know by Belial6 · · Score: 1

      Because there are Apps that would work in either environment just fine. Just because you can think of a case that won't work doesn't mean that all cases don't work.

    3. Re:don't know by luis_a_espinal · · Score: 1

      android didn't do anything good for linux, if anything it just made another incompatible implementation of the same platform. wake me up when i can run android app on my linux desktop without needing to run it in some virtual machine.

      adobe i don't even wanna comment about. i avoid them more carefully than entrance to hell.

      Oh really, so do you think you could have taken RHL or Ubuntu and popularize Linux as a mobile OS? Also, the statement is stupid. It is not a question of whether X has done anything good for Linux, but whether Linux has done anything good for X. And it has. Linux has allowed to create a good mobile platform (Android) which is far more open than the competition (the closed-source iOS).

      Asking or saying whether Android has done anything good for Linux is as stupid as saying that inkjets and laser printers (and any Linux-based embedded system for that matter) haven't done anything good for Linux. Plain retarded fanboyism.

    4. Re:don't know by GPLHost-Thomas · · Score: 1

      Oh really, so do you think you could have taken RHL or Ubuntu and popularize Linux as a mobile OS?

      That's what a bunch of Debian developers are trying to do, yes. They are doing so by backporting the open source Meego APPs into Debian so that your phone can eventually run them. It seems to work pretty well in fact (faster than Maemo which is damned slow).

    5. Re:don't know by w0mprat · · Score: 1

      Android Apps *can* be coded for the virtual machine (which uses JIT compiling anyway) but it doesn't have to be that way, you can have native code in your Android Apps, and many do. http://developer.android.com/sdk/ndk/

      --
      After logging in slashdot still does not take you back to the page you were on. It's been that way for 20 years.
    6. Re:don't know by KugelKurt · · Score: 1

      Why, exactly, would you want to run an app designed for a phone on your desktop anyway?

      Your assumption is wrong. Traditional "desktop" Linux isn't bound to desktops. See MeeGo or KDE's Plasma Active: Both develop touch-friendly GUIs on top of traditional Linux systems.
      With convertible tablets/laptops one may indeed want to run a touch-friendly app on the same system as mouse-driven apps.

    7. Re:don't know by justsomebody · · Score: 1

      there already were meego and maemo. both mobile desktops are much more friendly with other linux implementations and both can run on any distro (i know for meego 100%). so yes, you can use RHL or Ubuntu. both are also much more open than android. couldn't care less about iOS, wouldn't touch it with a ten foot pole.

      as it is currently, android, while running on linux... how the fuck linux as desktop os is the least compatible with that platform of all closed ones if it is such holly grail for it like you say? face it, android just fragment linux once again for no reason.

      proclaiming one as stupid, while you actually have no clue about other options just bounces your statement back to you.

      p.s. while saying all this i still have android phone, at least until i can find some decent phone on which i can put custom brew meego os

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    8. Re:don't know by HappyPsycho · · Score: 1

      Given that google is trying to integrate the android kernel back into the vanilla kernel, it has the potential to do allot.

      Google got caught between a rock and a hard place in terms of needing to show a working product and having to maintain a separate kernel vs having nothing to show for a while and keeping their patches within the linux kernel itself.

  3. Share the love by Citizen+of+Earth · · Score: 2

    When will I be able to run Android on my desktop?

    1. Re:Share the love by Anonymous Coward · · Score: 3, Interesting

      Now?
      http://www.android-x86.org/

    2. Re:Share the love by fortyonejb · · Score: 1

      When you are running an ARM desktop for one.

      How do people still not get this?

    3. Re:Share the love by jonbryce · · Score: 1

      About 7 months ago
      http://www.reghardware.com/2010/11/03/review_netbook_toshiba_ac100/
      But after reading that review, or any other review elsewhere on the same product, you probably won't want to.

    4. Re:Share the love by Fred+Or+Alive · · Score: 1

      OK then, when will I be able to run Android on my Acorn A4000. :-)

      --
      10 PRINT "LOOK AROUND YOU ";
      20 GOTO 10
    5. Re:Share the love by Pope · · Score: 1

      I am writing that in my copybook, now.

      --
      It doesn't mean much now, it's built for the future.
    6. Re:Share the love by Sunshinerat · · Score: 1

      I am pretty sure your ARM250 from yesteryear isn't completely compatible with the ARM9 cores that appeared 15 years later.
      Some critical things missing are graphics acceleration and FPU.

      --
      Load New Commander (Y/N)?
    7. Re:Share the love by Svartalf · · Score: 1

      Now. Especially if you're using one of the Honeycomb tablets. You can run it with X86 Android now on any desktop with the proviso that you just simply can't run NDK derived stuff without having someone provide you with the X86 native code variants for that Android image/distribution.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  4. Adobe - it's a disfunctional relationship by cultiv8 · · Score: 1

    Adobe isn't moving away from the Linux community. Rather, the company is refocusing its efforts into the emerging Linux-based space found in mobile products.

    So you're going to market Dreamweaver and Illustrator/Photoshop as the latest greatest dev tool for building apps? Why do I get the feeling academia would really embrace that...

    --
    sysadmins and parents of newborns get the same amount of sleep.
    1. Re:Adobe - it's a disfunctional relationship by luis_a_espinal · · Score: 1

      Adobe isn't moving away from the Linux community. Rather, the company is refocusing its efforts into the emerging Linux-based space found in mobile products.

      So you're going to market Dreamweaver and Illustrator/Photoshop as the latest greatest dev tool for building apps? Why do I get the feeling academia would really embrace that...

      How did you get to that conclusion from what he wrote? Strawman much?

    2. Re:Adobe - it's a disfunctional relationship by Narnie · · Score: 1

      Nah.... since 2.2 can run flash, we're supposed to be developing our apps in flash now. With flash's portability and its security, it is the best tool....

      ah, who the fuck am I kidding. Adobe sees android as cake and they want a slice too.

      --
      greed@All_Evils:~#
  5. Whoa! Hold on a moment. by Anonymous Coward · · Score: 5, Informative

    "The relationship between Linux and Android is on a technical level not hard to grasp — there's a shared kernel...

    Most Linux Distros -> GNU/Linux.

    Linux is the kernel. Shared kernel means it's Linux.

    Period. end of story.

    , but the application and interface layers are quite different.

    That could be said for any Linux distro.

    Android is a Linux distro.

    1. Re:Whoa! Hold on a moment. by sexconker · · Score: 1

      I love how it takes an AC to point out the blatantly obvious.

    2. Re:Whoa! Hold on a moment. by TheRaven64 · · Score: 1

      Mod parent right up. The confusion comes from people who keep talking about Linux when they mean all of the extra stuff on top of the kernel. You can take a typical 'Linux' system and replace the kernel with FreeBSD and neither users nor developers will notice. The closest most of them get to it is libc, which is GNU code. Your applications on Ubuntu care about X11, glibc, GTK, Cairo, and so on. Your apps on Android care about Dalvik, Skia, and so on.

      --
      I am TheRaven on Soylent News
    3. Re:Whoa! Hold on a moment. by node+3 · · Score: 2

      You make a good point, but come to the wrong conclusion.

      The word "Linux" can be used to describe just the kernel alone, or the GNU/Linux (to use Stallman's nomenclature, which Linus Torvalds rejects) system in general. When someone says "Linux distro", they mean a "GNU/Linux distro". And, isn't Android GNU/Linux anyway? Doesn't it include the GNU tools? What it's not is a traditional GNU/X11/GNOME|KDE|other-X11-based UI/Linux Intel-compatible PC distro. I think it's not unreasonable that people don't go around being so specific, and just say "Linux".

      So, Android is an OS based on a heavily modified Linux kernel, it's not a Linux distro in the way people use the term. And even if you want to play the semantics card and call it one, you still fail to answer the question posed in the article. If it makes you feel linguistically better, use the term "traditional" or "common" or something similar.

      Rewrite the headline in your mind to read: Drawing the Line Between Android and the Common, Traditional Form of GNU/Linux Distro

      That's what the author meant, and most people (who even know what Linux is in the first place) take as understood.

    4. Re:Whoa! Hold on a moment. by node+3 · · Score: 1, Insightful

      The confusion comes from people who keep talking about Linux when they mean all of the extra stuff on top of the kernel.

      No, the confusion is with people who think that Linux can only refer to the kernel. Even Linus doesn't play the "GNU/Linux" game.

      Certainly, it would have save a lot of hassle had Linus decided to give his kernel and the GNU OS using his kernel completely different names, like Darwin and xnu. Instead, he called the kernel "Linux", named the file "vmlinux" or "vmlinuz" (depending on whether it's compressed or not).

      The language may be imprecise, but you can't blame people for using the language as it exists. Just because a bunch of nerds with an aversion to ambiguity have come up with a way to be more precise doesn't make it right. It just makes a set of more specific terminology, that almost nobody uses. Not even most of the people who make a fuss about it.

      After all, are you saying that you aren't also one of the "people who keep talking about Linux when they mean all of the extra stuff on top of the kernel"?

    5. Re:Whoa! Hold on a moment. by Anonymous Coward · · Score: 1

      Android is a Linux fork, not a distro. Not because they use a 100% incompatible userland, but because the Android kernel is kept in a separate repository with no access to outside developers, and they release a huge patch with their improvements with no comments or documentation to respect the letter of the GPL. This is why Android isn't Linux.

      Also, the userland isn't only different, but completely incompatible. On any Linux distro, you can expect (for a GUI application) glibc, X, and one of glib/gtk, Qt, or other toolkits. You can't find that stack on Android.

    6. Re:Whoa! Hold on a moment. by GameboyRMH · · Score: 2

      Android doesn't include the GNU tools. The Android kernel is based on the Linux kernel (but is incompatible with the mainline kernel), and that's where the similarities end. Because the kernel is incompatible you could argue it shouldn't be called Linux at all.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    7. Re:Whoa! Hold on a moment. by betterunixthanunix · · Score: 1

      The word "Linux" can be used to describe just the kernel alone, or the GNU/Linux (to use Stallman's nomenclature, which Linus Torvalds rejects) system in general

      Android and TiVo demonstrate why Stallman is right on this issue. Nobody can deny that Android and TiVo are using Linux as a kernel, but the userland is completely different and certainly isn't GNU. Gone are the days when you could assume that any computer running Linux would also be running GNU.

      That's what the author meant, and most people (who even know what Linux is in the first place) take as understood.

      Most people on /. -- not most people in general. People may have heard of "Linux," not know exactly what it is, then hear "ANDROID IS LINUX" and immediately think that it must be the same as Fedora or Ubuntu. That kind of confusion is not a good thing for anyone.

      --
      Palm trees and 8
    8. Re:Whoa! Hold on a moment. by luis_a_espinal · · Score: 1

      The word "Linux" can be used to describe just the kernel alone, or the GNU/Linux (to use Stallman's nomenclature, which Linus Torvalds rejects) system in general

      Android and TiVo demonstrate why Stallman is right on this issue. Nobody can deny that Android and TiVo are using Linux as a kernel, but the userland is completely different and certainly isn't GNU. Gone are the days when you could assume that any computer running Linux would also be running GNU.

      A distinction that is mostly irrelevant for most people, even most developers (if you count them as people:P)

      That's what the author meant, and most people (who even know what Linux is in the first place) take as understood.

      Most people on /. -- not most people in general. People may have heard of "Linux," not know exactly what it is, then hear "ANDROID IS LINUX" and immediately think that it must be the same as Fedora or Ubuntu. That kind of confusion is not a good thing for anyone.

      See my response above.

    9. Re:Whoa! Hold on a moment. by goarilla · · Score: 1

      You can take a typical 'Linux' system and replace the kernel with FreeBSD and neither users nor developers will notice.

      Yeah right ! In theory maybe but in practice hell NO!
      I do long for the day for it to be possible without me noticing.
      But i guess we'll have to wait some more for that.

    10. Re:Whoa! Hold on a moment. by GPLHost-Thomas · · Score: 1

      Most Linux Distros -> GNU/Linux. Linux is the kernel. Shared kernel means it's Linux. Period. end of story.

      Where would you classify Debian k-FreeBSD, which is Debian running over the FreeBSD kernel? And Debian GNU/Hurd? Are they "less" a linux distro than other flavor of Debian?

      Android is a Linux distro.

      Hell no. Android is not a distribution. From wikipedia: "The operating system will consist of the Linux kernel and, usually, a set of libraries and utilities from the GNU project, with graphics support from the X Window System. Distributions optimized for size may not contain X and tend to use more compact alternatives to the GNU utilities, such as Busybox, uClibc, or dietlibc. There are currently over six hundred Linux distributions. Over three hundred of those are in active development, constantly being revised and improved."

      Where are my GNU tools in Android? It's definitely NOT a Unix distribution. It barely has a fork of the Linux kernel, which in many cases, we don't have the patches for and all the drivers.

    11. Re:Whoa! Hold on a moment. by tlhIngan · · Score: 1

      Android and TiVo demonstrate why Stallman is right on this issue. Nobody can deny that Android and TiVo are using Linux as a kernel, but the userland is completely different and certainly isn't GNU. Gone are the days when you could assume that any computer running Linux would also be running GNU.

      Actually, TiVo uses the GNU userland - it's all standard GNU with proprietary addons. Of course, it's *old* GNU (pre-GPLv3), but it's still GNU.
      http://www.tivo.com/linux/

      Heck, they use glibc. Granted though, they do have DRM and other stuff, and the vast majority of stuff they use is proprietary and written by TiVo, but everything in it works the same way any regular GNU/Linux system works.

      It's Android that's the odd one, being a completely new userland - the only thing GPL is the kernel itself. The rest of it is Apache, including the C library (Bionic). Heck, it has a completely rewritten version of BusyBox as well. Though, other than the kernel running init, that's where the similarities end - the startup system is different as is everything else. I'm sure Bionic isn't a full C library either - just enough to kickstart the Android environment and support the tools Android uses.

      If someone was daring enough, they could implement the necessary services and such on BSD and make a completely compatible, but closed, version of Android.

    12. Re:Whoa! Hold on a moment. by node+3 · · Score: 1

      I don't know about "should", but that's exactly what ended up happening. The individual OS's have their own names (Slackware, Debian, Red Hat, etc.), but they are all called "Linux" (well, one of those goes by GNU/Linux).

    13. Re:Whoa! Hold on a moment. by batkiwi · · Score: 1

      Where would you classify Debian k-FreeBSD, which is Debian running over the FreeBSD kernel? And Debian GNU/Hurd? Are they "less" a linux distro than other flavor of Debian?

      Are you serious? Neither of those are Linux distributions!

      If you install cygwin does that make windows a "linux" distribution?

    14. Re:Whoa! Hold on a moment. by GPLHost-Thomas · · Score: 1

      No, windows itself wouldn't, but cygwin for sure IS a GNU distro. Windows is simply capable of running it. Here, you are simply pretending that Linux == kernel and that's it, like many others in this /. entry. If you want to think it this way, then go on. But never ever, the Android platform can be called a "distribution" (Linux or not).

    15. Re:Whoa! Hold on a moment. by KugelKurt · · Score: 1

      Most Linux Distros -> GNU/Linux.

      It may be nitpicking but even that is not necessarily true. GNU/Linux means a GNU userland on top of the Linux kernel. These days it's at least not unlikely that the userland is not primarily GNU powered. KDE is not a GNU project. Neither is eglibc (used by at least Debian and Ubuntu).

    16. Re:Whoa! Hold on a moment. by wrook · · Score: 1

      Before you could get Linux to run as a kernel, the GNU code was making the rounds. It ran on all the popular Un*x hardware and was pre-compiled for a variety of kernels. You could even buy tapes which contained distributions of it. The GNU code was so much better than anything shipping with the hardware that it was practically the first thing you would install after you got your box. There *were* people (and still are) that preferred the original BSD code, mostly because they were used to it, I think. You have to understand that at the time that Linux was being developed, GNU had very little competition.

      When the Linux kernel became available people started to put together small distributions of GNU code that included the Linux kernel. Especially at the beginning, there were still a lot of legal hurdles that BSD had to jump through. For me, personally, I didn't really have confidence that BSD was going to continue to be in existence. And besides, I wanted GNU. I might as well get a Linux kernel along with GNU pre-compiled, rather than get BSD (whose future was uncertain) and compile GNU on top of it.

      What people fail to realise is that nobody was distributing Linux with a whole bunch of stuff along with it. They were distributing a whole bunch of stuff (originally just GNU, but later X and many, many apps) and including the Linux kernel with it. *That's* why the distribution was called "Linux". It was the same distribution of software that people already wanted, but coupled with a kernel and pre-compiled for that kernel. I don't think anyone even considered calling it GNU with Linux at first, because everyone knew it was GNU. There wasn't anything else you could distribute.

      But somewhere along the way, as users became less and less technical, they got confused about what was Linux and what was other stuff. Now there are a lot more options. It *is* confusing to say "Android is Linux". It certainly isn't anything like the Linux distribution on my desktop. The TFA is ranting about about this situation. To me it's bloody obvious. My desktop is GNU and X with a Linux kernel. My phone is Android with a Linux kernel. It's perfectly clear. But somehow the TFA can't understand the point and the confusion is due to unclear naming.

      Even in this thread there is confusion. Do you *really* care if you have a Linux kernel? Granted it has a lot of hardware support and there are some other advantages. But if you had GNU and X sitting on top of a BSD kernel, you would barely notice a difference. If you had Android sitting on top of Linux on your desktop, that would be a massive change from your normal desktop. And yet we talk about our system being "Linux with a bunch of other stuff", even though Linux is not what we generally care about.

      The FSF really goofed the situation when they pressed for the whole GNU/Linux thing. It came out as some big ego thing (which it might have been, I don't have the slightest notion). But they foresaw the situation where someone was going to take a Linux kernel and build an OS around something other than GNU. At this point the distinction is important (GNU/Linux vs Android) and now, when it is important, we can't do a damn thing about it because people are pissed off about something that is barely relevant (whether the whole GNU/Linux thing was just an ego play).

    17. Re:Whoa! Hold on a moment. by peppepz · · Score: 1

      Android is a Linux distro.

      Yeah. My Samsung TV set is a Linux distro, too, because it runs the Linux kernel.

  6. Adobe Air by devjoe · · Score: 1

    The main point of the article is about Adobe's development tools for Adobe Air. Is anybody actually using Adobe Air? The only thing I can recall having seen done using Adobe Air is help for recent versions of Adobe products, and this makes it so slow compared with any other help system that it makes a hugely negative ad for Air.

    1. Re:Adobe Air by cultiv8 · · Score: 1

      The Amazon Cloud Player MP3 upload uses Adobe Air...

      --
      sysadmins and parents of newborns get the same amount of sleep.
    2. Re:Adobe Air by hitmark · · Score: 1

      There are some twitter clients done in Air, with the biggest being Tweetdeck.

      --
      comment first, facts later. http://chem.tufts.edu/AnswersInScience/RelativityofWrong.htm
    3. Re:Adobe Air by umberleigh · · Score: 1

      in the UK, the BBC's iPlayer app which is used for video on demand is built in Adobe Air

    4. Re:Adobe Air by DavidinAla · · Score: 2

      Air is great for people who care only about developing cross-platform apps cheaply and not about whether those apps fit with the rest of the platform they're running on. As a user, I won't use Air apps unless there's absolutely no other choice. For me, that's happened ... never.

    5. Re:Adobe Air by Sheik+Yerbouti · · Score: 1

      Actually I am really liking Gwizard Gcode calculator and Gcode editor which is air also the ebay desktop app is air and National Geographic Complete is also air. Adobe flex is a good dev tool and air is one of the better VMs out there for desktop GUI apps better than Java in my opinion. Silverlight might give it a run for it's money on Windows but air is truly cross platform for example I can use all of those air apps on Linux, Windows, or Mac. That's pretty cool. In fact I do use those apps on Linux. Also I like actionscript 3 it's a pleasure to write code in much better than actionscript 2 IMO

  7. Re:Android and Linux by h4rr4r · · Score: 1

    Ok, so I copied the update.zip to the SD card, and ran it from clockwork.

    What was supposed to be hard about that?

  8. Linux market by future+assassin · · Score: 2

    I don't understand why so many companies refuse to support linux. Yes the market is small comapred to Windows BUT its not that small and its a big niche market which lets you charge more for the software/hardware as most Linux users will undderstand that a company might have to sell at higher margings since the user base numbers are smaller. Mabe its the short term profit mantality that is causing this but wouldn't you as a company want to make customers for life?

    I'm just an average Linux user who has all computers in the house running Mint but I don't get into the software and hardware setup anymore yet I'm willing to pay a little more to have the software hardware compatabiliy in Linux even at 20% of whats available on windows.

    --
    by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
    1. Re:Linux market by tepples · · Score: 1, Insightful

      Yes the market is small comapred to Windows BUT its not that small and its a big niche market which lets you charge more for the software/hardware

      It's also a niche market filled with skinflints who won't pay anything for software and filled with users who demand the right and ability to hire anyone to fix defects in the software.

    2. Re:Linux market by h4rr4r · · Score: 1

      That depends on the software we are talking about. For a desktop environment I totally agree, I would not pay for one and it must be FREE software. For video games, not at all. I buy games on steam and play them in Wine all the time.

      The reality is software for the most part is not worth much of anything, it has no scarcity and most commercial devs deadend it all the time to boost their profits. No wonder at least some people oppose that sort of thing.

    3. Re:Linux market by Anonymous Coward · · Score: 3, Insightful

      It's also a niche market filled with skinflints who won't pay anything for software

      Yes, that's why Linux users have consistently paid more for the Humble Indie Bundle games than Mac or Windows users. We're all so cheap.
        Hell, I punched in what I thought was a fair price and was downright shocked to see what Windows users were paying. There's a bunch of cheapskate bastards if I ever saw one.

    4. Re:Linux market by phantomfive · · Score: 1

      As I see it there are two main problems with Linux (and I really like Linux).

      The first is a lack of good APIs (beyond the Posix level, which is fine). If Linux had something like Quartz, porting Photoshop to Linux would be simple for Adobe. It would make a lot of things easier. Instead you have to hack around with SDL (which is a great library that reaches it's goals, it just doesn't do all that much).

      Second is the difficulty of installing/distributing binary software. Linux was built for distributing applications by source, and has a lot of good tools for doing so, and as an open-source advocate I like that, but a lot of companies don't want to distribute source, and there isn't really a good way to distribute binaries.

      Fix those two problems, and the effort of porting to Linux will be a lot cheaper, and more companies will do it (because the cost/benefit analysis will say it is worth it to hire one guy to port if that's all it takes).

      --
      "First they came for the slanderers and i said nothing."
    5. Re:Linux market by Nursie · · Score: 1

      Yup.

      Linus server software is a different game entirely, but on the desktop you're right - us linux users will look for the free, open source way every time.

      This is because FOSS products end up being more capable, over time. Maybe not in terms of bells and whistles, but in terms of moving data between formats, supporting every possible device, data format etc etc. We've come to like the way things work on the FOSS desktop - every new capability is just an apt-get away.

    6. Re:Linux market by Microlith · · Score: 2

      Good to see anti-FOSS trolls are all over Slashdot these days too.

    7. Re:Linux market by h4rr4r · · Score: 1

      Second is the difficulty of installing/distributing binary software. Linux was built for distributing applications by source, and has a lot of good tools for doing so, and as an open-source advocate I like that, but a lot of companies don't want to distribute source, and there isn't really a good way to distribute binaries.

      Deb and rpm handle this problem completely. Package your app and be done with it. If you can't even be bothered to do that you never would have ported you app to begin with.

    8. Re:Linux market by Junta · · Score: 1

      So at the low level, there is SDL, at the high layer, QT or GTK. In terms of the middle ground, how does Cairo compare with Quartz? We are talking capability, not compatibility. If you want to recompile existing OSX or Windows projects, that's different (with GNUstep and libwine respectively coming the closest, but very very far from production ready, though at least EVE online thought libwine was sufficient).

      To second, binaries are quite workable, but claiming support for 'Linux' may be more complicated than supporting, say 'Ubuntu and/or Fedora'. Some people may bemoan the multi-distro situation, but covering RHEL and Ubuntu largely covers your bases. I occasionally do have reason to execute ancient Linux binaries still, and they generally are passable still. Do you ruffle the feathers of Slackware and/or OpenSuSE and/or Gentoo? Perhaps, but the share is small and they can reasonably take care of themselves if the work has been done to assure RHEL and Ubuntu functionality.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    9. Re:Linux market by brainzach · · Score: 1

      Linux market share is less than 2% of desktop computing.

      If you have a product that targets the geek demographic like a graphics card, then supporting Linux is in a company's best interest, but its not surprising to see why many companies refuse to support Linux.

    10. Re:Linux market by phantomfive · · Score: 1

      See, this is the kind of problem we in the open-source community run into. We have a thing that works well enough for us, and we don't understand why it won't work for everyone.

      In general, commercial software doesn't want something that will fit easily into a package manager. What they want is an installer that is click-click-click "accept license agreement" and then on top makes you type in some kind of serial number, and maybe has some other kind of DRM. Deb was definitely not designed to do that, and rpm? Well, it is better than tar -xvf anyway.

      --
      "First they came for the slanderers and i said nothing."
    11. Re:Linux market by h4rr4r · · Score: 1

      I don't want that. I am the buyer. If you want me to click on stuff put the deb on a website with such a click through. Have the key entered into the program on first launch, not during installation. That breaks automated installation.

    12. Re:Linux market by phantomfive · · Score: 1

      how does Cairo compare with Quartz

      That's a good question, I'll have to look at it after work.

      A lot of times the problem is dealing with stuff in an API that just doesn't work. It should, but (usually it is because of a driver issue) you call the function and something messed up happens. This happens a lot even on Android, for example, if you leave the Dalvik runtime environment. Drivers are hastily written and cause APIs to be broken.

      --
      "First they came for the slanderers and i said nothing."
    13. Re:Linux market by phantomfive · · Score: 1

      If it were up to the buyer, DRM stuff would never exist. Not everything is up to the buyer.

      --
      "First they came for the slanderers and i said nothing."
    14. Re:Linux market by The+Moof · · Score: 1

      the geek demographic like a graphics card

      I'd say they target pc gamers, and Linux is pretty far behind Windows in that regard. So graphics card manufacturers aren't very interested in marketing to Linux since their primary consumer is using Windows.

    15. Re:Linux market by h4rr4r · · Score: 1

      Yes it is, why do you think I don't own any games that don't play on wine? What games I buy is 100% up to me.
      I will own Portal 2 as soon as it is supported by Wine or the Codeweavers commercial product without any cracks.

      Everything is up to the buyer. If buyers did not buy games with DRM, they would not exist.

    16. Re:Linux market by Kjella · · Score: 1

      I think you're making a flawed assumption about Linux, once you start charging more for a Linux version the sales drops drastically. After all the software is already written and the Windows sales covered the development cost, then surely the Linux sales can cover the small porting cost. Not saying that's necessarily a correct assumption, but many think that way. And as some of the Linux porting companies have found out, often people feel they've paid for this software and is then entitled to use it on any platform it's available.

      The other thing is support and binary compatibility. You can say you only support Linux distro X, but rest assured that you'll have a million requests/demands/complaints that you support every little distro out there, as well as people clogging up the forums with hacks and workarounds to do it anyway. Every sort of library/upgrade/version issue will land on your table, which may be once every six months. In short, Windows and OS X is built to ship binaries, there's long lasting binary interfaces to everything and old interfaces are kept around for many years until they're slowly deprecated and phased out. Linux is constantly changing and backwards compatibility is spotty at best.

      Oh yes and you might not realize it, but Microsoft does a whole lot both on the hardware and software side to make life easier for developers. Driver models like WDDM, NDIS etc and software toolkits like DirectX. There's a reason Windows has one video acceleration standard (DXVA) and Linux has three (XvBA, VA API and VDPAU). It's Microsoft saying here's the standard, build your driver to comply with this and the DirectX code will do the rest. Nobody really takes the same responsibility to write the code above the vendor specific layer, very often it falls to AMD and nVidia and Intel to write what Microsoft would have done on Windows. That puts even more of the cost of supporting Linux on them.

      --
      Live today, because you never know what tomorrow brings
    17. Re:Linux market by Nursie · · Score: 1

      "The incentive for using Linux is at first the fact that it is free"

      False.
      Other platforms are effectively free. I use linux because it is capable, useful and (to me) easy.

      It also doesn't pick up infections like a $5 hooker, which windows does.

      OTOH free allows it to do amazing things like have app stores. I just wouldn't do half so much with the computer if they weren't there. In that case free is the enabling mechanism, not really the reason itself.

    18. Re:Linux market by Nursie · · Score: 1

      I don't know why I said data formats twice... tired...

    19. Re:Linux market by jedidiah · · Score: 1

      > It's also a niche market filled with skinflints

      It's no different than Windows in this regard.

      Linux from a developers perspective isn't really all that difference. Most of it is just rhetoric from a few noisy people on either side.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    20. Re:Linux market by jedidiah · · Score: 1

      ...except the more hardcore part of the market is less slanted towards Windows.

      Get into the demographic that's actually likely to know what a video card even is and you will see much more Linux and MacOS users.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    21. Re:Linux market by node+3 · · Score: 1

      How many people do you think there are that will gladly buy software with their own money who won't also run either Windows or OS X? And I say "gladly", because there are some Linux users who would reluctantly buy proprietary, binary-only software, but they don't like it. It runs counter to some of the motivation behind running Linux in the first place.

      There aren't as many of you as you seem to think.

      Most people who want proprietary software will run Windows or OS X. If you use Linux because it's UNIX-like, OS X is a fantastic UNIX which enjoys great third-party software support.

      Otherwise, you'll have to make a choice. Stay with Linux and get almost no proprietary software (something which most Linux users won't see as a bad thing), run Windows (at least in dual-boot mode or in a VM), or buy a Mac.

    22. Re:Linux market by node+3 · · Score: 1

      The reality is software for the most part is not worth much of anything

      That sentiment right there sums up the average Linux user almost perfectly.

    23. Re:Linux market by node+3 · · Score: 1

      It's also a niche market filled with skinflints who won't pay anything for software

      Yes, that's why Linux users have consistently paid more for the Humble Indie Bundle games than Mac or Windows users. We're all so cheap.

        Hell, I punched in what I thought was a fair price and was downright shocked to see what Windows users were paying. There's a bunch of cheapskate bastards if I ever saw one.

      A few exceptions don't disprove the rule.

    24. Re:Linux market by brainzach · · Score: 1

      I bet the average Linux user cares about a video card more than the average Windows user. Although companies will promote Windows usage the most, offering Linux support can be profitable for the companies because of increase sales and positive PR with the open source community.

    25. Re:Linux market by node+3 · · Score: 1

      Deb and rpm handle this problem completely. Package your app and be done with it.

      Do you know how selling software works? If you just throw together a .deb or .rpm, and "be done with it", you'll find an inbox full of angry customers demanding support. Oh, you packaged your .deb based on Debian Squeeze? Well, package foo upon which you software was tested doesn't work the same in Ubuntu Natty Narwhal. And never mind all the requests from Gentoo users who want to know which flags they need to set to recompile their software to fix some obscure bug that pops up when trying to run the software as installed by your .rpm.

      Oh, and where does your package install to? Is it /usr/local/? Or maybe /opt/? Wherever you pick, you will piss off someone who wants it somewhere else.

      And for systems that aren't based on .rpm or .deb packages, so they don't have proper dependancies? *You* might say they are ignorable, they *they* sure won't see it that way.

      There is no "package your app and be done with it" in Linux.

      If you can't even be bothered to do that you never would have ported you app to begin with.

      And that's exactly what most software makers choose, simply not even porting it in the first place.

    26. Re:Linux market by h4rr4r · · Score: 1

      Do you disagree?
      How is something that is not rare worth much?
      I would be happy to pay for its development cost, but beyond that there is no point. I can make copies as easily as the folks that wrote it.

      Games I make an exception for as those are entertainment not tools I need.

    27. Re:Linux market by h4rr4r · · Score: 2

      Then just give me a tar.gz.
      The humblie indie bundle folks managed that.
      The reality most linux users will be so happy to be able to buy your game they won't bother you with emails but will fix their problems themselves.

      There is no package your app and be done with it on any desktop OS. Windows has no package management at all, and OSX only has it if you want to pay Steve Jobs 30%.

      And that's exactly what most software makers choose, simply not even porting it in the first place.

      Fine by me, most software like most of everything sucks.

    28. Re:Linux market by GPLHost-Thomas · · Score: 1

      Do you know how selling software works? If you just throw together a .deb or .rpm, and "be done with it", you'll find an inbox full of angry customers demanding support. Oh, you packaged your .deb based on Debian Squeeze? Well, package foo upon which you software was tested doesn't work the same in Ubuntu Natty Narwhal. And never mind all the requests from Gentoo users who want to know which flags they need to set to recompile their software to fix some obscure bug that pops up when trying to run the software as installed by your .rpm.

      Has someone every said you should ship ONE type of package? It isn't that hard to build binaries for both Debian and Ubuntu, it's just a dpkg-buildpackage away, and virtualization (like virtualbox) makes it *very* easy to have many build platforms. Now, let's say you want to cover 90% of the cases, then you'd be doing packages for Debian, Ubuntu and CentOS, with both 32 and 64 bits. In fact, that's down to doing one deb and one rpm, and then build. Yet, you might find some funny distro like Gentoo, you are right, and "they" wont like it, but you can still live with it... Also, most of the time, there's no ABI breakage, so it will work even without recompiling (see the horrible work that Skype did: even if it's horrible job, it does work).

      Oh, and where does your package install to? Is it /usr/local/? Or maybe /opt/? Wherever you pick, you will piss off someone who wants it somewhere else.

      There's a standard filesystem hierarchy here, it's not about pissing somebody off, it's about respecting standards, like having your configuration files in /etc, your read only files in /usr, and so on. There's no reason to put anything in /opt unless you are on the non-brainer Maemo platform, or things in /usr/local unless you are writing a FreeBSD port.

      And for systems that aren't based on .rpm or .deb packages, so they don't have proper dependancies? *You* might say they are ignorable, they *they* sure won't see it that way.

      But *you* might don't care about 5% of the users if you've covered most of the others with deb/rpm. So let them say...

    29. Re:Linux market by marnues · · Score: 1

      You must understand that it's not up to the buyer or else you would be able to buy the software for your Linux distro. I'm not sure how you created such a disconnect.

    30. Re:Linux market by h4rr4r · · Score: 1

      If I paid a few million dollars I am sure I could get any game I want ported. Failing that if I could get enough buyers together we could do that same thing.

    31. Re:Linux market by shutdown+-p+now · · Score: 1

      its not that small

      Actually, yes, it is for the most part. Sorry.

    32. Re:Linux market by VortexCortex · · Score: 2

      Data
      Paid for
      Choose one.

      I'll Pay for someone to do work: process my data for me, or to manipulate the data (write/fix code). However, in a world where data duplication is so cheap these words were copied over 20 times (more if you consider video ram, or have many router hops), you shouldn't expect people to pay for the data... (Supply = infinite, regardless of dev cost or demand, price = 0;)

      Let's say you contract me to write a program for you for $2,000. I'm done with the program and I've sent you screenshots of it in action. What's that? You want a copy of the program? Oh, we didn't discuss that in your contract... You want me to copy the data for you across the Internet or on in the mail via Disk? Well, let's see... I'll have to charge you an extra $100 for that. Additionally, each time YOU copy the program, I want you to pay me another $100.

      Oh? You don't agree with that? You say that the program is yours since you paid me to create it, eh? I already did the work, and it costs nothing, surely not $100, to duplicate the 1's and 0's...

      -- OK, say we never met --

      And, how about we say you just happen to work in an industry that has lots of common problems that have software solutions. Now, let's say I went off and wrote a program that provides solutions to many of these problems. Now, You can download the program from my website but first you must purchase a product registration key for $100 -- Each workstation or server you install it on will need a unique code, so you pay me for each copy. Oh, WTF?! This is somehow acceptable? Hypocrite much?

      You see -- I like to get paid for actually doing work. Reproducing bits is not work, we all have teams of machines that do this hundreds of times a minute for us constantly.

      So, The problem isn't that Linux users don't want to pay for software -- I'll gladly pay you to make an improvement, or to create a new bit of software, or to be on call for when I need support for the software... However, paying for each copy? No. We won't pay any more than it costs to duplicate it. Who do you think we are? Naive proprietary software users? I'm not paying you to do ABSOLUTELY ZERO WORK.

      Artificial Scarcity is Considered Harmful. Stop doing it.
      Oh noes! How will you fund the massive software project without imposing artificial scarcity? How about you tie your "sale price" to your actually costs of doing business? Instead of: "each copy costs $X", say, "to fund the development of that software we need $X"

      Being honest sucks, eh? Can't be nearly as greedy, right? Guess what? I work and make an honest living too!

      (please excuse any silliness or mistakes, I'm doped-up -- just had wisdom teeth out, but I'm not crazy)

    33. Re:Linux market by Anonymous Coward · · Score: 1

      No. It's all demographcs. I work in visual-fx where linux has a strong market share. All the major player in this space sell linux versions (tools from Autodesk, SideEffects, Foundary). There has sufficient APIs and have no trouble selling (installing/distributing) closed source software.

      I'm sure there are other small markets where linux is also strong, and I'll be app developers in those markets support linux.

    34. Re:Linux market by phantomfive · · Score: 1

      lol man, a million dollars? You have a serious disconnect with this conversation. Keep it real, dude.

      --
      "First they came for the slanderers and i said nothing."
    35. Re:Linux market by benhattman · · Score: 1

      Games I make an exception for as those are entertainment not tools I need.

      I'm all for FOSS, but your comments actually make negative sense.

      If you should be willing to pay for anything, it's the things you need and not the games. Based on your logic, you should pay to play basketball at your local park, but your home should be free because it's something you need.

      It's definitely rational to choose LibreOffice for free if it does everything you need rather than pay MSFT for a comparable tool. And it's certainly a valid argument than copyright laws, which were always designed to create artificial scarcity, seem even more out of place in the digital world we've adopted over the last 20 years. But, at the same token we will need to figure out a way to compensate creators for their labor.

      It was one thing when the main product being stolen was music (not that musicians don't deserve to be compensated), because at least there was an obvious way to continue paying them (through live performances) and musicians want to make music even when they won't be well paid. In other words, it really doesn't take much to compensate someone for the effort to write a song. When it spread to movies, and software, it got a little dicier just because the production costs of those products are generally so much higher. But things are really going to come to a head when CNC/makerbots reach a maturity level where if you can get your hands on the iphoneX specs you can make one at material cost.

      Not sure what will happen, because a world where the specs are free for all could be wonderful, but I think society will need to find some alternative financial policy aside from capitalism/socialism to make it work.

    36. Re:Linux market by h4rr4r · · Score: 1

      Software I need must be free because I need to be able to update it and improve it. Entertainment does not need that.

    37. Re:Linux market by peppepz · · Score: 1

      The first is a lack of good APIs (beyond the Posix level, which is fine).

      We have excellent APIs well above the POSIX level. Try QT for example. Or the huge standard libraries made automatically available by high level languages such as Java.

      If Linux had something like Quartz, porting Photoshop to Linux would be simple for Adobe.

      Qt has nothing to envy from Quartz. Adobe ported Photoshop to UNIX, back when it had to be done using Motif and X11, which were a pain in the ass to code for. Nowadays even Adobe products for Windows use Qt (Photoshop Elements). If Adobe wanted to port Photoshop to Linux, they could do it in a couple of months. They don't, only because there's no demand for it.

      It would make a lot of things easier. Instead you have to hack around with SDL (which is a great library that reaches it's goals, it just doesn't do all that much).

      You can't in any way see SDL as the equivalent of Quartz for Linux. That would be XRender, Cairo, Arthur or Java2D. At least 3 of them are pretty powerful and easy to use.

      Second is the difficulty of installing/distributing binary software. Linux was built for distributing applications by source, and has a lot of good tools for doing so, and as an open-source advocate I like that, but a lot of companies don't want to distribute source, and there isn't really a good way to distribute binaries.

      Linux has all the mechanisms in place to install, distribute and maintain binary-only software. Even more so than Windows. It was modeled after the traditional UNIX OSes which weren't open source. The good way to distribute binaries is well defined by both common sense and written standards that all Linux distributions try to follow (Android doesn't, hence it is not a "Linux distro").

      Packaging systems are nice to maintain an operating system, but IMHO they're highly overrated as a third party application distribution system. Try cracking open some RPM or DEB and manually run the software inside them - it will probably work fine with no modifications. Applications for Linux could be distributed in .tar format just like most applications for Windows are distributed in .zip format.

    38. Re:Linux market by ToasterMonkey · · Score: 1

      Good to see anti-FOSS trolls are all over Slashdot these days too.

      Don't confuse pro-professionalism, entrepreneurism, maturity types with anti-FOSS types.

      They may completely overlap, but there's an important difference.

      I mean there are people who just hate FOSS people, but then there are people who think anything goes, no risk, no commitment software development is _stupid_ and people who assert all software should be like that are _insane_.

    39. Re:Linux market by soccerisgod · · Score: 1

      Aren't we confusing free-as-in-beer and free-as-in-freedom?

      --
      If a train station is a place where a train stops, what's a workstation?
    40. Re:Linux market by h4rr4r · · Score: 1

      No, when I say FREE I mean FREE as in freedom. As I prefer GPL or BSD odds are it will also be free-as-in-beer but that is a secondary concern.

  9. Re:Android and Linux by royallthefourth · · Score: 3, Informative

    No problem! The Android SDK is in the repository for every major distro. Just push out the ROM, and reboot into recovery and flash it.

  10. Flash Builder by tepples · · Score: 2

    As I understand it, AIR is pretty much the same environment as Flash, except run outside of a browser.

    1. Re:Flash Builder by krazytekn0 · · Score: 2

      If that's true it scares me out of my mind. I always think of flash like a 12 year old boy driving a bulldozer around a giant sandbox with holes in all the walls. I like to think of the browser it's running in as another giant sandbox with slightly less holes in all the walls. Every once in a while (all the time) that damn kid finds his way out of BOTH sandboxes and starts driving around the streets of some highly populated town wreaking destruction. And if what parent is saying is true are we taking one of the perimeter walls totally down? OH GOD!

      --
      Not all life is cyber. Extra Income
    2. Re:Flash Builder by GameboyRMH · · Score: 1

      Yep, isn't Adobe a brilliant company?

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
  11. there's a shared kernel? by bfree · · Score: 2

    The kernel is not shared, it is derived and has never _really_ attempted to minimise it's changes from it's upstream so really it is an incompatible fork. So not only is Android not GNU/Linux (or X/Linux or posix/Linux or BSD/Linux) it's not even Linux.

    --

    Never underestimate the dark side of the Source

    1. Re:there's a shared kernel? by Microlith · · Score: 1

      the fact that all their changes are not merged back to the mainline doesn't mean it's a fork

      Actually that explicitly makes it a fork. Every distro has its own fork of the kernel. The problem is that Google has made little effort to get their changes into the kernel, and when drivers for hardware are built against their kernel they are almost completely unsalvageable and a pain in the ass to bring into the mainline.

    2. Re:there's a shared kernel? by airfoobar · · Score: 1

      What's the point of making Linux GPL if people aren't meant to fork it and make something new out of it? This is Linux and the GPL working exactly as they should, I think.

    3. Re:there's a shared kernel? by bgat · · Score: 1

      The kernel is not shared, it is derived and has never _really_ attempted to minimise it's changes from it's upstream so really it is an incompatible fork. So not only is Android not GNU/Linux (or X/Linux or posix/Linux or BSD/Linux) it's not even Linux.

      Not quite.

      It's true that the Android kernel is derived from the mainline kernel. It's also true that some of what is in the Android kernel will never be merged into the mainline kernel, although some Android kernel features, like timed-GPIO, are now part of the mainline. The differences that have remained between the two kernels over the years are likely to remain that way, for various reasons.

      It is NOT true, however, that the Android kernel is an "incompatible fork" from the mainline kernel. Assuming you get the runtime library situation right, ordinary "Linux" programs will run under an Android kernel just fine. So Android is most definitely "Linux" as you define the term.

      The purists will correctly argue, however, that Android is an Operating System and not a kernel at all. It's just an operating system that requires a few features not found in the mainline Linux kernels. Hence the need for an Android-associated Linux kernel.

      --
      b.g.
    4. Re:there's a shared kernel? by Microlith · · Score: 2

      No one has a problem with forks. Redhat maintains a huge fork.

      The problem is that Android uses a heavily customized kernel that results in virtually nothing (certainly nothing that I am aware of) going back upstream. Unsurprisingly, vendors are loathe to port their drivers forward to the next version of the kernel (which would be easier if they were upstream.)

    5. Re:there's a shared kernel? by bgat · · Score: 2

      The problem is that Google has made little effort to get their changes into the kernel, and when drivers for hardware are built against their kernel they are almost completely unsalvageable and a pain in the ass to bring into the mainline.

      And that's different from most other contributed drivers how, exactly? :)

      --
      b.g.
    6. Re:there's a shared kernel? by Spykk · · Score: 1

      So I guess Redhat and Ubuntu aren't really Linux either because they use custom kernel patches?

    7. Re:there's a shared kernel? by Confusador · · Score: 1

      There's nothing wrong with forking it, the question is whether it's still the same thing after you do. Nobody is claiming that X.Org is the same as Xfree86, even though they are clearly related. Likewise OpenOffice.org and LibreOffice. Has the Android kernel deviated enough that it should no longer be called Linux? I think probably.

  12. GNU/Linux by vagabond_gr · · Score: 3, Interesting

    So the GNU/Linux arguments start making a lot more sense now, aren't they? Cause if you just call it Linux, Android seems perfectly "Linux" to me.

    1. Re:GNU/Linux by Pausanias · · Score: 1

      Mod parent up. "Linux" as synonymous for "Linux on the Desktop" is a disservice to both Linux and GNU/KDE. Aren't most Linux kernel users now Android users? Whereas they still wouldn't touch Ubuntu with 10 foot pole.

    2. Re:GNU/Linux by jimicus · · Score: 1

      Most Linux kernel users today are probably modern television or set-top box users.

    3. Re:GNU/Linux by krgallagher · · Score: 1
      "So the GNU/Linux arguments start making a lot more sense now, aren't they? Cause if you just call it Linux, Android seems perfectly "Linux" to me."

      I just don't get this. The gas pump you use probably runs Linux. The cash register at the store probably runs Linux (OK I've seen a lot that run windows.) Tivo runs Linux. Linux is a very popular embedded operating system. Most embedded systems run little if any GNU software. That does not make them less Linux.

      --

      Insert Generic Sig Here:

  13. Linux is a kernel by the_humeister · · Score: 4, Insightful

    All the other programs running on top comprise the OS. Why can't people get this straight? There isn't just a "Linux" community, there's a GNU community, an X community, a Debian community, a GCC community, an Android community, etc. Some parts overlap and some parts don't. But to say that all of these communities is Linux is a little misleading.

    1. Re:Linux is a kernel by Microlith · · Score: 1

      there's a GNU community, an X community, a Debian community, a GCC community, an Android community

      The interesting part is that if you look at how code flows between those communities, the first four benefit each other in various ways. In contrast, the Android community is entirely insular, neither aiding nor being aided by the others.

    2. Re:Linux is a kernel by bgat · · Score: 1

      there's a GNU community, an X community, a Debian community, a GCC community, an Android community

      The interesting part is that if you look at how code flows between those communities, the first four benefit each other in various ways. In contrast, the Android community is entirely insular, neither aiding nor being aided by the others.

      I don't think you can generally say that--- or prove it.

      Part of the reason that the first four communities are so visibly benefiting each other is that those communities themselves are relatively transparent. They are also mutually-dependent on each other. Android hasn't see major uptake in the FOSS community (yet!), however, so there aren't any obvious benefits to those other communities from Android at least because the communities currently contributing the most to Android aren't themselves transparent.

      Given the complexity of Android's source code, I'd say it's pretty likely that Android has provided the opportunity to identify and fix issues in GCC and GNU Make, at least. Android doesn't use X, so lack of mutual benefit shouldn't be too surprising there. And I do know of at least one Android OEM that is using Debian very, very heavily so it's reasonable to conclude that there have been Android-to-Debian improvements there too.

      --
      b.g.
    3. Re:Linux is a kernel by owlstead · · Score: 1

      Personally I would love it if apps are not only distributed as "free", but also as "free, open source". That could make a bit of a difference regarding the uptake of certain apps. And an URL to the website (preferably sourcesafe or similar) would give extra trust, especially if somebody (Google itself) would check the correctness somehow. Maybe that would give Android some O/S love.

      Free is one thing, but on my Linux desktop, I try and run open source only.

    4. Re:Linux is a kernel by andydread · · Score: 1

      You are probably correct It is misleading. The communities you mentioned though are typically centered around Linux. I guess like you said some parts overlap I guess Linux is the main overlapping piece.

  14. Re:Linux is a kernel not an OS by Frankie70 · · Score: 1

    Why are you posting anonymously, Richard?

  15. MVC by tepples · · Score: 1

    You do realize that android apps run in dalvik right?

    One common pattern is a Java front-end made especially for Android that runs in Dalvik, combined with a C++ back-end shared with other platforms that runs in the NDK. In MVC terms, this corresponds to a C++ model and a Java view.

    1. Re:MVC by Lunix+Nutcase · · Score: 2

      One common pattern is a Java front-end made especially for Android that runs in Dalvik, combined with a C++ back-end shared with other platforms that runs in the NDK.

      Except that your C++ code is still executed from within the Dalvik VM.

      The Android NDK is a companion tool to the Android SDK that lets you build performance-critical portions of your apps in native code. It provides headers and libraries that allow you to build activities, handle user input, use hardware sensors, access application resources, and more, when programming in C or C++. If you write native code, your applications are still packaged into an .apk file and they still run inside of a virtual machine on the device. The fundamental Android application model does not change.

      So no it doesn't run in the "NDK" considering that statement makes absolutely no sense.

    2. Re:MVC by tepples · · Score: 1

      Does "and they still run inside of a virtual machine on the device" mean that the NDK compiles C++ to Dalvik bytecode?

    3. Re:MVC by bgat · · Score: 2

      Except that your C++ code is still executed from within the Dalvik VM.

      Depends on how you define "within". True, the VM allows control to pass to the C++ code. And true, that code is running in the process context of the VM. HOWEVER, the C++ code is running directly on the CPU, just like ordinary C++ code.

      The situation is not unlike a shell invoking a native program. Although the native program is running as a child process to the shell, the native program is only minimally influenced by that.

      --
      b.g.
    4. Re:MVC by Anonymous Coward · · Score: 2

      That's not how that works at all. It works similarly to JNI. The method call is a proxy made available to your Java (or Dalvik) application, then by executing that code, the VM will, rather than executing Java (or Dalvik) byte-code, know based on the declaration:

      public native void Blah() {
      }

      That it has to execute a native method, and it will check the library in LD_LIBRARY_PATH for a shared object that contains a method with a matching name and signature.

    5. Re:MVC by ommerson · · Score: 1

      Having implemented just such an application (it has a large model layer shared with the iPad version of the same app), this is not a trivial bit of engineering.
      JNI provides lots of ways to screw up and debugging across the interface is challenging to say the least.

      By FAR the best way to do the development is to get the model and JNI portions working and thoroughly unit tested with a test-harness before going anywhere near any of Google's tools or a device. Since lots of your problems are going to be in C/C++ land, invoking a JVM from native code makes life a lot easier at this stage.

      An easy port it was not.

      With the possible scenario of Windows Phone 7 being the 3rd successful mobile platform, building the bottom layers of these apps in C#/.Net is looking quite attractive as you can run it on all of the platforms. I assume MonoDroid deals with the consequential .NET VM Native Java boundary crossing.

    6. Re:MVC by tepples · · Score: 1

      I assume MonoDroid deals with the consequential .NET VM Native Java boundary crossing.

      MonoTouch/MonoDroid is also cost prohibitive for individual hobbyists trying to develop a hobby into a business.

  16. Re:Both by Elbereth · · Score: 2, Interesting

    There's a difference between being cheap (trying to minimize costs), having an entitlement complex (believing that you deserve everything for free), and wanting the source code available (software freedom). I'm not saying that they don't intersect, but there are differences. It's easy to confuse people who call for software freedom with the people who pirate software, because they're both using the word "free", but in different contexts, and they both have an aversion to paying for commercial software, whereas the cheap user might be virtually immune to spending their money on luxury brands, like Apple or Sony, that offer little real return for the extra money spent.

    But, in the end, you're just trolling, and I'm simply bored; so I'm responding to your troll. I'm sure someone else will mention the Humble Indie Bundle, because it's turning into an annoyingly cliched (though true) counter-example to this common troll.

  17. don't know... how OS's work? by Kamiza+Ikioi · · Score: 4, Insightful

    First, it's called Java and it runs android apps on linux (amoung others), just like Linux runs any other app. Android doesn't make kernel bound, machine compiled apps for the very good reason that they need as many apps to run on as many phones without separate compilers. Phones are still running completely different chipsets than PCs, or are you not aware that you can't run amd64.deb on a 32bit PC, etc. etc. If so, you aren't very educated about the issue at all.

    If you want to take some code, make some native applications compile to it, I'm sure you could get some command line tools that work on both platforms, compiling separately on each. Mainstream users don't CARE if they can run it on their computers. Frankly, not many geeks care either. That's a pretty minority of a minority view. At best, people would like to run Linux desktop apps on Android, not the other way around.

    And the problem isn't Android, it's XWindows. When you get XWindows and Gnome/KDE to run efficiently on ARM, you let me know and THEN we'll talk about portability. Until then, NON ISSUE QED.

    And even then, you'd still need a type of virtual machine, regardless of whether the code ran or not. Apps are built for.. wait for it... phones and tablets! It's pointy-multi-touchy, not lefty-righty-clicky.

    The fact is that Android is the first, and only, real main stream Linux OS that rivals every single one of its competitors. What did Android do for Linux? That's like asking what Apache has done for Linux. Without Apache, Linux wouldn't have the server market cornered. Android did for linux on phones what Apache did for linux on servers. And if you don't get that analogy, you just don't get it the topic at all.

    --
    I8-D
    1. Re:don't know... how OS's work? by Johnny+O · · Score: 1

      I didnt think there was a more idiotic post. Gratz!

      I have a GP2x and just bought a Caanoo..
      I couldnt believe what I just read.

      http://www.google.com/search?q=gp2x

      I also help with ArmedSlack. I found this post very bizarre.

    2. Re:don't know... how OS's work? by Anonymous Coward · · Score: 3, Insightful

      And the problem isn't Android, it's XWindows. When you get XWindows and Gnome/KDE to run efficiently on ARM, you let me know and THEN we'll talk about portability. Until then, NON ISSUE QED.

      GNOME/KDE are overrated, but the N900 runs X11 on ARM just dandy. Of course it's not the huge Xorg nee Xfree86 monstrosity, it's a kdrive variant (which, perhaps confusingly, is also an X.org project), but it's still X11R6 and it lets all your X apps run, including letting PC apps display on your phone or phone apps* display on your PC's X server. And Hildon (the desktop environment of Maemo) is pretty much a mobile-centric version of GNOME, so it could be said without much exaggeration that we do have "XWindows and Gnome" running efficiently on ARM.

      *But some phone apps are stupidly written to ignore the DISPLAY environment variable, and hard-coded to :0 -- obviously they won't display remotely without massive futzing around.

      The trouble isn't that a real UNIX-like phone OS can't be done -- it has been done! The trouble's that Maemo, and the similarly UNIX-like WebOS, each belong to a single phone maker, so they'll never make the market impact of a commoditized OS like Android, and never get the same ecosystem of developers. Nokia's involvement with Meego was supposed to rectify that, but we all know where that went *coughELOPcough*, and without a big phone name behind it, it looks like Meego will be primarily a tablet/in-vehicle/etc. OS, with at best niche presence in the phone market.

    3. Re:don't know... how OS's work? by Kamiza+Ikioi · · Score: 1

      Exactly. People don't understand that you have to build to the device, not just the platform. PCs are so very similar that people rarely notice the difference. Of course, anyone with a 32bit PC trying to run a 64bit only app immediately learn that there is a difference when the chipset changes. That's why devices like the GP2X runs emulators. It's also why VMWare and HyperV have such a great market. Not just for segregation of services, but also because many people still rely on 32 bit systems but need the power and ram of a 64bit system, which can be dynamically allocated among many 32bit systems. I have a server here running 32GB of ram and running nearly a dozen copies of Windows 2003.

      People just don't realize that it's not just kernel, but the device, that matters. I can't even imagine the driver nightmare someone would run into ala Linux from years ago when nobody made open source drivers... actually, I can. Running CyanogenMod7, it becomes clear that drivers for different cameras and wireless chipsets are hard to optimize and get working properly.

      Emulators solve that problem, especially if you can get everyone to agree on a common emulator or virtual machine.

      --
      I8-D
    4. Re:don't know... how OS's work? by Kamiza+Ikioi · · Score: 1

      Great information (definitely Insightful), thanks!

      --
      I8-D
    5. Re:don't know... how OS's work? by xenocide2 · · Score: 2

      Maemo Linux, the OS that runs my n900, runs Xorg just fine. I don't think GNOME would be a good fit, but Hildon does use GTK, dbus, hald, pulseaudio, NetworkManager, and the evolution DB backend. And while you can't run amd64.deb, it does have a repository of ARM arch .debs. I think the best way to define what Slashdot would call linux is "capable of running wireshark". And the N900 meets that task, but does hilight your point that desktop apps are not in and of themselves, ready for mobile. I think the opposite might be true though; things that work on phones should be able to work natively on desktops without much fuss.

      Maemo goes back to the n770 in 2005, so Android is hardly the first ARM phone attempt. Frankly, the reasons for success and failure here don't involve Linux technicals. It's about market position and strategies. Nokia has so many base patents on cellphones that they feel entitled to dictate the pace of phone growth. Their Maemo smartphone strategy assumed a leisurely 5 years and a patent portfolio to stop competition from racing ahead. Well that didn't stop Apple, or Google, and Nokia is happy to collect their profits in the form of patent settlements instead, while the board of directors approves a backdoor sale of Nokia to Microsoft.

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

    6. Re:don't know... how OS's work? by Anonymous Coward · · Score: 1

      When you get XWindows and Gnome/KDE to run efficiently on ARM, you let me know and THEN we'll talk about portability

      Heh... You mean, with this?

      Maemo.

      Or, perhaps, you mean with this:

      Meego

      Or even further...

      OpenPandora

      The only thing that Android has over those is that the mobile companies got behind it FIRST. Nothing else. XWindows isn't the problem. Hell, even GNOME/KDE isn't really the problem, especially with the class of resources you'll find with most of the ARM devices you're finding in the handhelds or tablets. It's only a sort-of problem with something that has 128MiB of RAM and then only sort-of.

      Putting it simply, you haven't a clue about what you're talking about if you're basing this all on what you just tried to run up the flagpole here.

    7. Re:don't know... how OS's work? by gnapster · · Score: 1

      It is unfortunate that some moderators hold back on anonymous cowards because their is no karma imparted. I would definitely mod GP up.

    8. Re:don't know... how OS's work? by Svartalf · · Score: 1

      Heh... Think of Hildon as GNOME Mobile, more or less. That was what Nokia was aiming for when they did it originally.

      As it stands, Android is a Linux distribution with a specific and unique App framework that runs under the Dalvik VM.

      That's why Canonical was able to make an execution environment that the dev threw his hands up in disgust over- he'd arrived at the conclusion that it was "open" in one sense and not another. For example, you can't get the market app and a few other things except by jiggery-pokery or permission from Google themselves. There's a few other gotchas to doing what Canonical tried for- NDK work won't work directly (This doesn't preclude trickery to call into Qemu or similar, though...) on an X86 system, for example.

      In the end...the only thing that makes Android "special" is that the mobile device players went with it instead of Maemo/Meego because it was more "ready" first, combined with more of a closed (which I allude to...) world than the other provided- and it was a bit more restricted than the other answers at the time it came out. The main reason that tablets are using it instead of some other bespoke Linux variant right at the moment is more inertia and app availability than anything else.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    9. Re:don't know... how OS's work? by GPLHost-Thomas · · Score: 1

      As it stands, Android is a Linux distribution

      No, it is NOT.

      I could write arguments about why it's not, but the simple fact that you wrote it means you don't understand what a Linux distribution is.

      Next, your speculations about Maemo vs Android are quite silly and misses the hole point. Nokia didn't care promoting its own product, or sharing some vital drivers that were shipped as binary blobs, didn't have a clear path on the development, and even made very bad announcements right after the n900 was out. How do you want other companies to follow such a dangerous path, or even use the OS of a competitor which aggressively uses patents when pretending to do open source stuff?

    10. Re:don't know... how OS's work? by Microlith · · Score: 1

      WebOS, at last glance, used a proprietary system and not Xorg. If they move to Wayland... well then. All they'd need to do is eliminate the proprietary IPC system and they'd have a fully open system (minus the webOS specific bits.)

    11. Re:don't know... how OS's work? by Anonymous Coward · · Score: 1

      Hm. I take it you haven't seen the N900, N9 from Nokia? No? Full X11 stack (whatever that's worth). Also what's wrong with the chipsets? ARM isn't exactly from out of this world, I can run apps compiled for debian armel just fine on my n900 when I also install the libraries debian needs. Heck you can make those things run full desktop distros....not that you'd want to....

      I think the mental model you have of phones is pretty screwed. At this point their are nothing more than a bunch of ARM computers with fancy extensions. Nothing that can't and hasn't been abstracted away with libraries before.

      As long as the platforms architecture doesn't change and I don't directly use the extensions in my app (you usually don't) it doesn't really matter if I use a library to get at the system dependent features or if I use them through a "vm". Even if x86/64 _would_ take a footing in the smartphone phone market (anyone but intel trying to do that?) all it would need is a recompile.

      Anyway. Don't get me wrong: I'm not advocating running desktop apps on our phones (it's funny in the odd cases, wireshark anyone? ;-) the UI sucks ofc) but saying you need a VM to cover different phones is just wrong.

      (oh and what android uses isn't Java, if it turned out to be google would be in deep trouble. You write java code alright, but it isn't compiled to jvm bytecode and hence isn't java. Dalvik is what google calls its VM)

    12. Re:don't know... how OS's work? by jonwil · · Score: 1

      X is running just FINE on my Nokia N900 thankyou very much.

    13. Re:don't know... how OS's work? by exomondo · · Score: 1

      First, it's called Java and it runs android apps on linux (amoung others), just like Linux runs any other app.

      Oh come on, the suggestion you linked to - if you even bothered to read it or have any understanding of what it does - is an emulator that emulates the entire device including the hardware and then runs android on top of that and then your applications on top of that. Whether or not it's java makes no difference which is why you can make native calls from java to compiled ARM libraries using the NDK and it still works in the emulator, it's also why the emulator is so incredibly slow.

  18. Linux is only the kernel. by CountBrass · · Score: 1

    As Linux is only the kernel and not the applications, GUI, C libraries nor any of the other things that make a complete OS then Adobe's claim is completely valid.

    There is no line to draw Android uses the Linux kernel the same as Ubuntu and every other GNU/Linux distro.

    --
    Bad analogies are like waxing a monkey with a rainbow.
    1. Re:Linux is only the kernel. by Billly+Gates · · Score: 1

      Why is it called GNU/Linux? Because some guy said so?

      He didn't write Linux? Nor did he write KDE and all the other non GNU products. X.org is certainly not nor is Firefox which is included.

      Give it up already. All this is doing is confusing non technical users based on some ideology from RMS. I do not care what he says. He can call it pink puppies for all I care. Does that mean you have to call it pink puppies too? According to Wikipedia Linux is an OS which uses the Linux kernel and that includes distro's which are simply called Linux. If you argue with me you have no data to back you up other than what some guy with a beard said. He is an individual and nothing more.

      I only care when people are knocked down for not supporting RMS's ideology. After using FreeBSD for awhile I realize there is more. I do agree that I do not consider an Andriod a Linux distro as I like to refer to it as Linux based.

    2. Re:Linux is only the kernel. by Eric+Sharkey · · Score: 1

      There is no line to draw Android uses the Linux kernel the same as Ubuntu and every other GNU/Linux distro.

      It's a bit murkier than that. Debian can actually run without Linux. (See Debian GNU/kfreebsd.)

  19. Kinds of software that don't need service by tepples · · Score: 1

    With OSS you don't pay for the software, you pay for the service.

    I understand. But there are some kinds of software that don't need much service, such as video games that aren't massively multiplayer.

    filled with users who demand the right and ability to hire anyone to fix defects in the software

    I'm amazed and horrified you think that's a bad thing.

    I think it's a good thing. I'm just describing conditions in the market where a lot of major software publishers think it's a bad thing, or at least not enough of a good thing to offset the competition that would occur.

  20. Games by tepples · · Score: 1

    on the desktop you're right - us linux users will look for the free, open source way every time.

    This is because FOSS products end up being more capable, over time.

    A lot of prominent applications that run in the Adobe runtime are games such as FarmVille. Do games also "end up being more capable, over time" if distributed as free software?

    1. Re:Games by Nursie · · Score: 1

      In some ways yes - Quake, OpenTyrian and various others now run on many, many more platforms and architectures than the originals did.

      They're not very up to date, it's true.

  21. Technicalities... by Junta · · Score: 1

    So if you get pedantic, sure, 'Linux' means/meant the kernel and only the kernel.

    In *practice*, Linux has come to describe the distributions that all use glibc, xorg, kernel, gtk, qt, etc. As far as application developers go, the kernel underneath it all is interacted with rarely if at all. Adobe in *particular* has no reason to be making Linux *kernel* specific calls, so it *is* disingenuous to hold up Android work as their 'Linux' support. Adobe hasn't done anything to support the specific kernel of any other platform, so trying to say 'Linux means kernel, so Adobe is fine to say that' is just not right.

    In truth, the *closest* to a mainstream 'Linux' has been WebOS, but it's fringe and skips the Xorg/GTK/QT part of the equation (though they do use SDL).

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re:Technicalities... by bgat · · Score: 1

      So if you get pedantic, sure, 'Linux' means/meant the kernel and only the kernel.

      In *practice*, Linux has come to describe the distributions that all use glibc, xorg, kernel, gtk, qt, etc.

      To you, maybe. :) Those of use not using Linux "on the desktop" are in many cases not using glibc, xorg, etc. etc. either. I'm thinking about embedded systems that use Linux as their kernel, and a home-grown root filesystem. The overwhelming majority of consumer and SOHO routers are constructed this way, to pick but one example.

      In terms of the number of physical devices running the Linux kernel, desktop machines are a distant second to all those other devices. Even if you don't count Android platforms--- which, by definition, count as Linux kernel installations.

      For me, I only care about "desktop Linux" to the extent that it helps me construct those other Linux-based systems. As such, I've been running Linux as the kernel and Debian as the OS on my production workstations for nearly a decade.

      --
      b.g.
    2. Re:Technicalities... by Junta · · Score: 1

      So I've made uclibc based installs and suffer from 'glibc'-isms, so I do take the point that in some crowds 'Linux' does still specifically refer to kernel.

      However, I still fail to see the relevance of any of Adobe's Android specific work being credibly associated with 'Linux'. If they had some noise around libva and friends, ok, but I don't see Adobe-level work on Android as being relevant at all to non-Android use of Linux.

      --
      XML is like violence. If it doesn't solve the problem, use more.
  22. Re:"A kernel alone doth not an OS make" by biodata · · Score: 1
    Sorry for my ignorance but where is the pravda quote from? It seems funny associating *NIX with the ruskies.

    I wonder if think the main thing the stats prove is that the vulns in Linux server platforms are better understood and publicly documented than those in other platforms because most people use Linux.

    --
    Korma: Good
  23. Re:Both by tuppe666 · · Score: 1

    How Offensive WTF is "entitlement complex" lets be fair you made that up. I do not have an unlimited supply of money, and that which I do I work hard for. What I am an "informed consumer with limited income", and that means I choose "best value" . I suspect that is why many Linux users paid more the "Humble Bundle Deal". It could be why many linux users (although I see no evidence of this) do not need the reassurance of large brand names to assess quality as they can read a specification sheet, often a supermarket brand or an unknown developing world country branded device will do more for less. Its not an Item of clothing. The only similarity between pirating and open source is the price of software. I believe more and more more that the model of maximising profits by changing large amounts for artificial scarcity is simply a bad model made worse by DRM etc, fortunately the digital age is killing of the old middlemen, and hopefully will bring affordable good content for everyone. Untill then I buy games from second hand stores. I'm not cheap thats what I can afford, and I'm better off than most.

    Whats most worrying about your post is its frighteningly misinformed, you are insulting people who don't buy products from companies (Apple/Sony) that not only cost more, are behind the curve technically/artificially restricted/proprietary technology incompatible with standards.In fact all they have going for them is the BRAND. At least use Samsung/Google/LG/Red Hat software/hardware etc. companies that are cutting edge/open standards....well more so anyway ;)

  24. Re:Seriously? by jedidiah · · Score: 2, Insightful

    Linux users respect the developer and their choices. This is inherent in the whole GPL thing.

    I see a product and I am willing to pay a fair price for it. I won't make excuses meant to make things cheaper for me.

    No. In truth it's Windows users that are the real "freetards". Their numbers just help diffuse this problem somewhat In truth, Windows users are a den of theives that have no problem pirating anything they might want or need. This is the reality that the results of the Humble bundles reflects.

    --
    A Pirate and a Puritan look the same on a balance sheet.
  25. Becoming more capable more slowly by tepples · · Score: 1

    They're not very up to date, it's true.

    So I guess we agree that non-free games rereleased as free software "end up being more capable, over time" in the sense that they end up more capable than they were when first published, but they don't end up more capable than the latest non-free games at any given moment. For example, I haven't seen a game based on ioquake3 or any other Free engine that would compete in production values with my cousin's favorite video game (Call of Duty: Black Ops).

    1. Re:Becoming more capable more slowly by Nursie · · Score: 1

      Sure, we can agree that, if we can also agree that games are generally the one area that linux folk, recognising that there are very few FOSS games, are willing to pay out.

      I'd never dream of paying for an operating system, but I buy stuff off steam.

  26. Potato, Potato by ArmchairGeneral · · Score: 1

    After reading the various comments from some who know more about this than I do, I think I can safely say there is not much agreement. Most arguments have valid points, but perhaps that is where we are with the GNU community, a bunch of ideas that share a similar philosophy, but no one particular direction. Much like the rest of the human race.

    1. Re:Potato, Potato by peppepz · · Score: 1

      But in the end it worked overall, both for the human race and for Linux. We did progress.

  27. Re:Both by obergfellja · · Score: 1

    Though the physical price (via currency aka Dollar Bill, Euro, Yen, etc) may not be used as much, but the concept of physical and mental cost is still there.

    Just because you don't pay in one way, you will still pay in another way. It is called equivalent exchange. you pay one way or another, but you will still pay.

  28. Re:UNTRUTHFUL PROPOGANDA comes 2 an end by biodata · · Score: 1

    Sorry I still don't understand what any of this has to do with pravda. It seems like you just repeated that the vulnerabilities in open source software are better known and more publicly documented than the MS stack.

    --
    Korma: Good
  29. Re:don't know - it shows by luis_a_espinal · · Score: 1

    Because there are Apps that would work in either environment just fine. Just because you can think of a case that won't work doesn't mean that all cases don't work.

    And that doesn't mean that *your* case is the general case either. Besides, why would people want to develop apps that run on both Android and Linux on a desktop? The majority of the linux user base is either in the mobile arena (via Android) or in the server arena. The desktop arena is irrelevant and provides no business case to develop for it.

    The android platform, not your PC, is the Linux desktop. Period.

  30. Re:X Windows should die by goarilla · · Score: 1

    I don't think you have have any idea of what you're talking about and buying into the
    X Windows is what makes linux sucks crap !

  31. Re:don't know - it shows by Belial6 · · Score: 1

    That statement makes no sense. If 20% of the people want to use Android Apps on the desktop, that isn't the general case, but it would be ridiculous to say that it shouldn't be done because the other 80% don't care. Using that logic, virtually no software should be written.

    Using the "Desktop Linux is too small of a market" is equally silly. There are tons of Linux desktop apps. Your argument is that none of those should exist either. It isn't even on the radar for a statement that can be taken seriously.

    Finally, Android is not the Linux desktop. It may be one day, but it isn't today, and it may never be. By claiming that Android is the Linux desktop, you are acknowledging that there are Android applications that people want to run on the desktop. Thus contradicting your first statement, and showing that integrating an Android VM into the Linux desktop makes sense.

  32. Re:Android and Linux by Eggbloke · · Score: 1

    I think he must mean reflashing it over USB. I'm not brilliant with terminology but I mean the first time you do it to enable recovery. I do not know of a way to do it with Linux. Of course you can transfer an update.zip to your SD card then run it in recovery but you can do that with any OS that supports file transfers and USB.

    --
    I care not for your karma and your mod points.
  33. Re:Seriously? by Kjella · · Score: 2

    The Humble Bundle proves that people that are fans of open source will pay more for open source games than people that don't give a fuck if it's proprietary or not. It's like using the sales of a Metallica album to prove that Metallica fans are more willing to pay for music than other fans. Fans that were told "please show how much you support us" while the rest were told "please check out our games". Big surprise that a lot of Windows users did download it for nothing or next to nothing to check it our, almost like a free demo while many Linux users took it as a donation run. You can look at Steam and see lots of people spending lots of money on games every day, a single sale there often being more than any OS' users gave for the Humble Bundle. That this somehow proves this is all wrong and that it's the Linux users that are willing to pay and the Windows users that are not, well let's just say it takes a certain kind of zealotry to reach that conclusion.

    --
    Live today, because you never know what tomorrow brings
  34. That's honestly laughable... by Kamiza+Ikioi · · Score: 1

    I could write arguments about why it's not, but...

    But, you don't, because you can't. Because every argument you have against it being Linux would either be plain wrong, or could be used to say that distro x, y, or z isn't Linux. Is Gnome linux or KDE? Is .deb linux or is .rpm? Once you hit the application layer, the argument turns to dust, and that's the only argument one could really have. You mention patents. I hate to tell you this, but Linux is still Linux even if on top of it, it is running proprietary, patented, closed source, copyrighted binaries.

    The fact is, Android is Linux. You can claim that it is a fork, or a massive fork, or whatever you want. If you could make the argument, you would. If you want to argue that it's not GNU, or it's not fully GPL, or something like that then you have some ground. But no argument takes away from the fact that Android is Linux anymore than arguing that LAMP isn't Linux because Apache uses it's own Apache License, and that's not "real" GPL, or some other RMS rubbish like that.

    I thought this junk went away with the arguments over the LGPL.

    --
    I8-D
    1. Re:That's honestly laughable... by GPLHost-Thomas · · Score: 1

      See how much a waste of time it would have been to state arguments that you know already! Yourself, you know already that running Linux is all about the GNU tools and all the libraries we have, and the ease of "porting" one app to another arch/platform. In Maemo, I just typed "dpkg-buildpackage" and I had both joe and mtr available for my phone, and I use them both very often. Until I can do that in Android, you can't call it a Unix distribution (and yet, even less a Linux distro.).

    2. Re:That's honestly laughable... by Cid+Highwind · · Score: 1

      So where's the line between "A Linux distro" and a platform that runs on top of a Linux kernel but is not a distro? Are you saying the requirements are having a package repo with joe and mtr, and the Debian package tools?

      --
      0 1 - just my two bits
    3. Re:That's honestly laughable... by GPLHost-Thomas · · Score: 1

      Not specifically joe and mtr, but being able to rebuild basic ncurses tools that needs the autotools layer, libc6, and other non-fancy very common libs (zlib, libstdc++, and other stuff like that) is for sure one of the requirements. I'm on purpose avoiding any graphical (X, GTK, Qt, etc.) depends to my definition, but some might not agree. There's about 30k packages in Debian, about 10k in CentOS 5.x, being able to rebuild (or even at least, cross-compile) a vast majority of the non-graphical ones seems a reasonable requirement to be able to be called a distribution. That is for being a *Unix* distro, not even Linux (eg: you aren't bound to a particular kernel here, which I don't think is the important bit). dpkg and rpm aren't even involved, you could well use other types of packages if you like it (see the variety of choice we have in this world: tar.gz with Slackware, deb, rpm, gentoo and FreeBSD ports, and there's all sorts of other less common types of packages (.ipk of openwrt anyone?)). Being bound to a particular language in a device (java, in the case of Android) isn't really helping.

  35. Re:don't know - it shows by improfane · · Score: 1

    I agree with you.

    I can imagine an Android application being the standard format for small 'widget' like applications that run on GNOME and KDE or any other desktop environment.

    They would replace the proprietary plasmoids and applets of DE and become standardized. I figure it makes sense because Android supports 'fragments' which are designed to scale up to larger interface.

    It also comes with a permission system for free. Many Android APIs could be mapped to a Linux compatibility layer, a daemon called. androidd. Phone call Apps would be using standard Android APIs but integrate with the VOIP software configured by the layer, your contacts with your address book, Wifi with your LAN and so on.

    --
    Slashdot needs Geekcode | Can anyone recommend any good SCIFI? My tastes: Foundation, Startide Rising, CITY, Ringworld,
  36. Re:Android and Linux by lordandmaker · · Score: 1

    Is there an advantage to the non-adb methods?

  37. Re:Linux market MIcrosoft Extortion Racket by andydread · · Score: 2
    Microsoft is running and extortion program to extract a tax from anyone that produces a successful Linux device.

    They are doing everything in their power to damage Linux in the marketplace.
    They are threating manufacturers actively using litigation to increase the cost of deploying Linux on a device/computer above that of Windows. This is a sleazy tactic but Microsoft is proving itself to be one of the sleaziest companies in tech right now.

    The racket goes like this. Microsoft enters your store/shop/company
    Microsoft: "You know, Its a dangerous neighborhood around here. You need some protection."
    You: "Protection? From who?"
    Microsoft: "Well.. from us mainly... IF you fail to get protection from us then you will feel the full wrath of our boys in our legal department."
    Microsoft: "Oh and by the way. The specifics of our protection deal is under NDA. You cannot talk about it got it?
    You: :-O

  38. Re:Android and Linux by MichaelSmith · · Score: 1

    Linux on openmoko phones can be reflashed over USB using dfu-util.

  39. Re:X Windows should die by MichaelSmith · · Score: 2

    Did X kick your dog or something? If you don't like it feel free to not use it.

  40. No single buyer who can front the entire cost by tepples · · Score: 2

    Instead of: "each copy costs $X", say, "to fund the development of that software we need $X"

    The trouble is that for some kinds of software, especially software intended for home use, there's no single buyer who can front the entire $X. Say someone has posted the first complete draft of a design document for a video game and asked you to help fund the implementation of that design document. Would you donate? Or would you wait for the finished game to see if the game is worth your while first? How should the developer make the deal more attractive to potential donors?

  41. Re:Both by Spugglefink · · Score: 1

    Have cheap ass users who don't want to pay for anything.

    In fairness, if I had an iPhone or a Blackberry or something, I'd still be a cheap ass user who didn't want to pay for anything.

    When I want/need an app for my Android phone, I start with the free stuff first. It seems like it's not the best software out there, but it's free, and there's plenty of it. So far I haven't actually paid for anything at all. I really am too cheap to spend $2 for something; especially when you can't just charge it to your phone account, but have to set up some kind of payment account thing at the app store; or at least it looks that way at a glance. Meh. Too much trouble. I'm cheap and lazy.

  42. Re:don't know - it shows by PoopCat · · Score: 1

    The android platform, not your PC, is the Linux desktop. Period.

    Guess I need to erase the last 10 or so years of my life then.