Slashdot Mirror


Ask Slashdot: Attracting Developers To Abandonware?

phlawed writes "I've been a Linux user since the previous millennium. I came from OS/2, which I really liked. I quickly felt at home with icewm, using a suitably tweaked config to give me something resembling Presentation Manager. I may have commented on that before. Today, I find myself in a position where my preferred 'environment' is eroding. The only force keeping icewm rolling these days is the distribution package maintainers. I can't code in any meaningful way, nor do I aspire to. I could easily pay for a supported version of icewm, but I can't personally pay someone enough to keep it alive. I'd love it if someone took a personal interest in the code, to ensure that it remains up to date, or to make it run on Wayland or whatever. I want someone to own the code, be proud of it. Is there a general solution for this situation? How do I go about drumming up interest for an old project?"

226 of 321 comments (clear)

  1. Relax the License by Anonymous Coward · · Score: 1

    Turn the license into a BSD license, maybe? If it's good code, it might attract some interest. If the software is dead, why not?

    1. Re:Relax the License by HiThere · · Score: 3, Informative

      Well, BSD generally attracks fewer developes than GPL, and you need to own the copyright to change the license, but outside of that it's a reasonable idea.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    2. Re:Relax the License by Anonymous Coward · · Score: 1

      I think the poster is talking from the point of view of someone who does not have the power to do that.

  2. There is a way by Rinisari · · Score: 3, Interesting

    I could easily pay for a supported version of icewm, but I can't personally pay someone enough to keep it alive.

    Sure you can. Find someone to work on it and get them to sign up for Gittip, while you do the same. You can "tip" them a few cents to several bucks per week for their efforts and they can get paid by you and other supporters.

    1. Re:There is a way by 93+Escort+Wagon · · Score: 4, Insightful

      Yes, I'm sure a few dollars a week is going to attract a coder to a project be isn't otherwise interested in.

      The submitter needs to just face reality - if there were enough people interested in keeping icewm going, it would already be happening.

      --
      #DeleteChrome
    2. Re:There is a way by ShanghaiBill · · Score: 1

      In some places a few dollars a week is a good living for something you can do as a hobby.

      Anyone that is able to write good code can make a decent living anywhere in the world. I have hired contract programmers from China, Pakistan, India, etc. If they are any good, they can easily make a few hundred USD a week. You aren't hiring rice farmers.

    3. Re:There is a way by Arker · · Score: 2

      The hardest thing would be getting a coder that's mature enough to do the job properly. It would take very little time to simply maintain the mature code and occasionally stomp a bug. Unfortunately if you give this job to a younger coder, regardless of what country he's from, you stand a very high chance of seeing him go crazy wanting to add new features and just screw it all up.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    4. Re:There is a way by InfiniteLoopCounter · · Score: 1

      Unfortunately if you give this job to a younger coder, regardless of what country he's from, you stand a very high chance of seeing him go crazy wanting to add new features and just screw it all up.

      As a young coder you don't have to tell me twice to learn the lesson -- this is the kind of thinking to promote to get high paying jobs maintining spaghettified cobol code that no one else understands in a bank later in life. Problem is that you old folks are already doing this and they might wake up to it by the time I get there.

    5. Re:There is a way by Billly+Gates · · Score: 1

      Sorry I wont click your link as it ends in .cx. Old timer slashdotters know what happens you go clicking around in those links. Something that can not ever be forgotten appears

    6. Re:There is a way by n7ytd · · Score: 1

      The hardest thing would be getting a coder that's mature enough to do the job properly. It would take very little time to simply maintain the mature code and occasionally stomp a bug. Unfortunately if you give this job to a younger coder, regardless of what country he's from, you stand a very high chance of seeing him go crazy wanting to add new features and just screw it all up.

      The way I read the OP's question was: "I really like program X, but I can't afford programmers to work on it. How can I convince programmers to work on program X for free or convince other people to pay them so that I can continue to enjoy it for free?"

      If someone is offering a reasonable wage, they will attract talent. Weeding out the non-talented is actual work, but not impossible. If they don't have wages to offer, then the only option I see is to spend more of what they do have (time) to build a following of program X, convincing others that it's the cat's meow and must be experienced to be appreciated.

      There are people out there working for free to maintain Commodore 64, Atari 2600, Apple ][, or PDP-11 emulators; all platforms which were obsolete 25 years ago. You don't find the same type of cult following for CP/M machines or building WordStar clones. Figure out why that is, and more importantly, which camp your
      favorite program X falls into: was it abandoned because it was no longer made, or because clearly better, evolved products of the same technology became available?

    7. Re:There is a way by Arker · · Score: 1

      I am not a huge fan of ICEWM personally but the same thing seems to have happened as with WindowMaker. The thing is pretty much done. There's nothing exciting left to be done, maybe a little updating of compatibility features (but that is never fun, when you just have to take what the other project gives you as-is and cant do anything cool with it yourself) and an occasional small bugfix is needed to keep it going though. But most everyone DOES have orders of magnitude more computing resources than they need these days, so it's easy to go with the herd mentality and move to one of the other projects, particularly if you are an employed programmer with plenty of cash and free time - exactly the people who normally volunteer to do this sort of work on projects that are still useful.

      The thing is, these projects obviously ARE still useful to some of us. And I didnt read his question as implying he didnt want to pay at all - but that he didnt feel he could pay it all alone. If we pooled our resources it really doesnt seem like it would take too many people pitching in $50/year or something for needed maintenance work on a program of this size and scope.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
  3. Re:Welcome to Linux by pipatron · · Score: 4, Informative

    While on the topic about fragmentation... Android is another type of linux.

    --
    c++; /* this makes c bigger but returns the old value */
  4. In "old vs new", usually "new" wins by ClassicASP · · Score: 2

    Sorry but thats just how it is, even in the Linux world. You can't relive the past. You gotta move on to newer things. Just look at my screen handle; I've learned this lesson myself. Don't waste time hoping it will make a comeback because it won't; not as long as there's a surplus of people willing to complain about how old and obsolete it is, and not as long as there's no significant payoff to be made.

    1. Re:In "old vs new", usually "new" wins by hedwards · · Score: 1

      Right. Vi remains viable because it's still an incredibly useful text editor that has a fairly large user base. When a project gets to the point where it's just a small number of non-coders that want to see it continue, it's finished. The likelihood of attracting developers is slim, unless they're either using the software or being paid for it.

      And being paid for it usually means a substantial number of users as I doubt that the software is worth hundreds of dollars to the submitter. And hundreds on a periodic basis.

    2. Re:In "old vs new", usually "new" wins by Tyler+Eaves · · Score: 1

      I suspect you just proved GP's point by mistake.

      The old, original vi is quite stagant, the most recent release is from 2005. On the other hand, "the new hotness" like Vim is seeing regular releases.

      --
      TODO: Something witty here...
    3. Re:In "old vs new", usually "new" wins by Bing+Tsher+E · · Score: 1

      The original vi is 'stagnant' because it's complete. Similarly, there are few new claw hammer designs since 2005 that anybody really cares about.

    4. Re:In "old vs new", usually "new" wins by hedwards · · Score: 1

      Like the other poster said, vi is feature complete, they implemented all the features that it needed ages ago. The only patches going into it now are compatibility ones and the occasional bug fix. But even that is fairly rare because it's mature code. It also remains the default text editor in some *NIX variants because it's historically what's been used and works very effectively once you've gotten over the suicidal learning curve.

      Vim has some nice features, but you're best not counting on them if you want to be able to log into any *NIX system out there without having functionality missing.

  5. Does maintaining mean reinventing the wheel? by atari2600a · · Score: 2

    What's keeping this layout from being re-implemented on any other window manager?

    1. Re:Does maintaining mean reinventing the wheel? by Anonymous Coward · · Score: 2, Insightful

      What's keeping this layout from being re-implemented on any other window manager?

      I. Do. Not. Get. It. Either.

      Here's his linked comment:

      I. Do. Not. Get. It.
      It is beyond me why people want to emulate the clutter they have on their physical desk, on their computer.
      One does not need a "Desktop Environment".

      What I want is a window manager that allows me to set the only sane focus policy (focus follows mouse, click to raise), maintains the user experience and config-file compatibility from release to release and otherwise stays out of the way. Not having to choose between 42 different plugins/extensions/addons and whatnot is also a good thing.

      A couple of years ago (*cough*) when IBM killed OS/2, I made the transition to Linux. I soon landed on icewm as my preferred window manager, as it had a "OS/2 Warp" theme. I believe I at one time played with a Presentation Manager-like desktop, but I soon realized it was more hassle than benefit.
      icewm has a fully configurable "context-menu" on the entire desktop background (right-click mouse for *your* selection of files, programs, folders, etc), ditto menu for windows (left click), configurable hotkeys (I hit F12 for a terminal), a toolbar with the regular stuff, workspaces and so on.

      And for any newbie out there: not running gnome or kde or whatever does not prevent you from launching gnome or kde programs.

      Now, please tell me again about the added benefits of having a zillion garish icons on your desktop background?
      Or, by the way... don't bother,...

      Seriously, let me paraphrase the parent:

      What the fuck is keeping the elements of this layout that you like from being re-implemented on any other window manager?

      Have you even tried? Hint: You don't need to know how to write code to customize a window manager...

    2. Re:Does maintaining mean reinventing the wheel? by Anonymous Coward · · Score: 2

      Totally agree.

      I used IceWM for a long damn time. I even wrote some patches (never released) to handle multi-monitor better.

      Now I use a combination of openbox/xfce and have it set up with all the behaviours I liked in IceWM (and many that wern't available in IceWM). It's not really that hard.

      When a project gets to a point where no-one wants to work on it any more, or even fork their own version off from it, it's time to let it rest.

    3. Re:Does maintaining mean reinventing the wheel? by fast+turtle · · Score: 1

      Guess he's looking for fluxbox - what I use. It's still under active development, has mouse focus, clk to raise, hotkeys/key bindings, a task pane (clock/dropbox) along with a taskbar. As to KDE or Gnome apps, yea I've got KDE 4.10 installed and use several apps (kate, dolphin, ark & konsole) plus several gtk based such as Filezilla, firefox, qmmp along with Qt4 apps such as qpdf, vlc and others. I guess he's simply pissing in the wind and bitching about getting wet because I've got everything he wants already.

      --
      Mod me up/Mod me down: I wont frown as I've no crown
    4. Re: Does maintaining mean reinventing the wheel? by Bing+Tsher+E · · Score: 1

      I've been maintaining the same .fvwmrc for over a decade now. It seldom needs anything but an occasional tweak.

  6. Become a Free Software Manager by reluctantjoiner · · Score: 2

    Determine if there's sufficient demand for your preferred environment to grow and be maintained, sufficient to pay the salaries for a small dedicated team. If you can't code, perhaps you can manage the project or handle the marketing. If the demand isn't there, you may have to deal with the situation as is, or transition to another platform.

  7. Re:Welcome to Linux by Blaskowicz · · Score: 2, Informative

    By that metric Playstation 4 is another type of BSD, so I guess it's the same as using linux, right?

  8. A 12-pack of Mountain Dew Code Red... by KrazyDave · · Score: 2

    ...and a family-sized bag of Cheetos ought to do the trick.

    --
    www.chihuahuarescue.com- Help to end dog abuse, abandonment and cruelty
  9. Workplace Shell by bmo · · Score: 4, Insightful

    I'm an OS/2 refugee.

    There are parts of KDE that seem much closer to WPS than the other environments. For example, right clicking in Dolphin and "Create New" to make a new blank object is similar to Workplace Shell's templates.

    The only parts of icewm that are similar to WPS is the coloring and button layout.

    None of the environments on Linux, Windows, or OSX are like the WPS "object oriented user interface." To understand what this is like you have to actually have used OS/2. Everyone else has no idea.

    --
    BMO

    1. Re:Workplace Shell by The_Revelation · · Score: 1

      Whats wrong with eComStation? http://en.wikipedia.org/wiki/EComStation

    2. Re:Workplace Shell by bmo · · Score: 2

      >Not even the windows version of Object Desktop from the folks at Stardock?

      Just because you call something "object" doesn't mean it's object oriented.

      I'll give you an example: Say you have an icon. The icon is a representation of an object that does something. You take another object, drop it on the icon, and an output object is created. But it's not just that, this "an object that does something" is available throughout the entire environment. That's the view from the user side.

      From the developer end, to quote Wikipedia:

      A part of the WPS design allows for the developer of a class Y which extends or modifies a class X to execute an additional API on installation which will let the WPS 'replace' class X by class Y. This will make even all existing instances of class X behave as instances of the modified class Y; i.e., almost a retroactive inheritance. This allows for many useful third-party desktop utilities that add or modify functionality to or of existing objects without access to IBM's source code. Where the IDL and class headers also of derived classes are published, these classes can as well be extended in turn in the same way.

      You can find out what this is really like by downloading EcomStation.

      --
      BMO

    3. Re:Workplace Shell by bmo · · Score: 1

      Nothing's wrong with EcomStation, except the unavailability of modern software. People who buy EcomStation have legacy applications that need to be run on OS/2.

      I've used it in VirtualBox for nostalgia reasons.

      --
      BMO

    4. Re:Workplace Shell by TheGoodNamesWereGone · · Score: 2

      The WPS was elegant and very well designed & was light years ahead of anything else. I still miss it. It'll never happen, but I wish the old code could be open sourced and developed for again. Like I said, it'll never happen though.

    5. Re:Workplace Shell by Anonymous Coward · · Score: 1

      Thanks to Adventure Time, I read your comments in a high pitched female voice with a light Korean accent.

    6. Re:Workplace Shell by dryeo · · Score: 1

      You can find out what this is really like by downloading EcomStation.

      There is a demo of the coming 2.2 release available at http://www.ecomstation.com/democd/ it's a beta so...

      --
      https://en.wikipedia.org/wiki/Inverted_totalitarianism
    7. Re:Workplace Shell by phlawed · · Score: 1

      I didn't mention WPS. :-)
      And I agree there isn't much like WPS. While I though it was a neat idea at the time, I never got accustomed to using the template system. It may have been my usage pattern.

      --
      Dag B
    8. Re:Workplace Shell by Billly+Gates · · Score: 1

      It is still updated?!

      Who the hell uses it? I know legacy apps but it makes more sense to me to keep old OS/2 in VMWare workstation or ESXi server and virtualize it to have it run older programs. No one cares what features it will include because it is obsolete and users would leave if they could.

    9. Re:Workplace Shell by jones_supa · · Score: 1

      Hmm, what is Adventure Time?

    10. Re:Workplace Shell by Yaztromo · · Score: 1

      It is still updated?!

      Who the hell uses it? I know legacy apps but it makes more sense to me to keep old OS/2 in VMWare workstation or ESXi server and virtualize it to have it run older programs. No one cares what features it will include because it is obsolete and users would leave if they could.

      The last time I tested it, VMware has a really hard time virtualizing the latest OS/2 releases. I was able to get it to work with some degree of stability only if I ensured I never went past OS/2 WARP v4 FixPak 11. Anything beyond that and the VM simply wouldn't boot.

      My understanding is the problem is that OS/2 was pretty much the only OS out there to make use of the full range of the Intel IA-32 architecture, in particular Ring 2 access, which isn't used in Windows or most *NIX derivatives.

      Wikipedia has some background on this issue.

      Yaz

    11. Re:Workplace Shell by bmo · · Score: 1

      Hmm, what is Adventure Time?

      Google is over there---->

      A note, my 5 digit UID here predates Adventure Time.

      I actually took my name from Firesign Theatre.

      --
      BMO - Not the Bank of Montreal.

  10. Re:How to attract developers? by nurb432 · · Score: 1

    He did say he was willing to pay for the software, just not pay a guys salary.

    --
    ---- Booth was a patriot ----
  11. Time to switch by bugnuts · · Score: 1

    That reminds me of when uwm went away in pref of twm. Window managers have all sorts of abilities and usu have widgets and event traps, and may have to be rewritten from the ground up to incorporate new ideas. But all is not lost, because you can usually tweak the new ones to behave like the predecessor.

    As far as window managers, old is often a subset of new, so my suggestion is to spend a day to adapt some new, maintained software using its config and dotfiles to behave the way you want.

  12. Kickstart? by Anonymous Coward · · Score: 1

    I suppose you could start a Kickstarter campaign to raise money for a developer's salary. It wouldn't have to be a full year's salary, just enough to encourage a developer to take on the work. Heck, I'd probably do it for a couple of grand. Anyway, if the Kickstarter campaign is a success you can hire a part-time developer to work on the project. On the other hand, if the campaign fails then maybe it is time to move on to a new window manager. There are plenty of free ones out there that work just fine.

  13. Re:How to attract developers? by bmo · · Score: 5, Funny

    I have a mod stalker who is modding down my past comments and is too much of a cowardly pussy to admit it or face me.

    No, you get modded down because you say idiotic things like this:

    Now you know why 90% of FLOSS projects are crap.

    Implying that this is different in closed source software. This is false. 90 percent of closed-source software is crap too. Sturgeon's Law applies everywhere.

    --
    BMO

  14. Android is not Linux ... by perpenso · · Score: 3, Interesting

    While on the topic about fragmentation... Android is another type of linux.

    No, its not. End users and nearly all **developers** don't see it. The Linux kernel could probably be swapped out with a BSD kernel and few would notice. Even for those using the NDK and writing some C code they are probably making POSIX calls not calls to anything Linux specific.

    1. Re:Android is not Linux ... by dindi · · Score: 3, Interesting

      Funny you mention this. When I got my first (and last) Android phone, I was honestly expecting a somewhat functional/scriptable Linux environment with Perl, some web server, and a sane package manager. I imagined that I would be able to script behaviour and set up a cron job to make a call or connect to the net......
      I did not even consider, that what I was getting was nothing like that. Besides this little surprise I hated the phone, the experience, everything about it.. including the uselessly slow emulator and the whole eclipse-based dev environment.

    2. Re:Android is not Linux ... by Fishchip · · Score: 4, Insightful

      Why did you even consider this? What did you expect from a consumer-grade cellular phone? Honestly?

    3. Re:Android is not Linux ... by PCM2 · · Score: 1

      Funny you mention this. When I got my first (and last) Android phone, I was honestly expecting a somewhat functional/scriptable Linux environment with Perl, some web server, and a sane package manager I imagined that I would be able to script behaviour and set up a cron job to make a call or connect to the net......

      What a strange thing to say. Do you expect that of your consumer Wi-Fi router, too? I mean, sure, there are third-party firmwares that will let you do some of that stuff, but that's true of Android, too.

      --
      Breakfast served all day!
    4. Re:Android is not Linux ... by H0p313ss · · Score: 2

      While on the topic about fragmentation... Android is another type of linux.

      No, its not.

      Yes it bloody well is.

      End users and nearly all **developers** don't see it. The Linux kernel could probably be swapped out with a BSD kernel and few would notice.

      That's true of desktop linux as well. If you used gnome on FreeBSD you would not notice.

      --
      XML is a known as a key material required to create SMD: Software of Mass Destruction
    5. Re:Android is not Linux ... by Microlith · · Score: 2

      Amusingly, the 3rd party firmware on my router has more in common with desktop Linux than any 3rd party Android firmware.

    6. Re:Android is not Linux ... by Arker · · Score: 2

      Not that I agree with his original point, but...

      "Linux and BSD are a bit different when you get to the console."

      Actually they arent. Dont let the default shells fool you. You can get bash on BSD and Zsh on linux. Or you could install ksh on either one for that matter.

      If you install and use bash and other gnu tools in preference to the BSD tools, you would wind up with GNU/BSD.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    7. Re:Android is not Linux ... by morgauxo · · Score: 1

      So? Most of the time you could say the same thing about a Desktop Linux distro.

    8. Re:Android is not Linux ... by FPhlyer · · Score: 2

      Android is very much Linux. It's just not GNU/Linux. All the GNU utilities that give Linux the functionality and feel of Unix have been stripped out and replaced by running Dalvik on top of the Kernal.

      --
      Brought to you by Frobozz Magic Penguin Fodder.
    9. Re:Android is not Linux ... by Samantha+Wright · · Score: 5, Informative

      While I generally agree that it's a huge WTF to think a consumer phone would be like that, when Android first appeared one of the most popular phones was the Maemo-based N900, a Linux smartphone that did indeed ship with a terminal client. Many Slashdotters seemed to consider it the pinnacle of phone design at the time, so it's perhaps not too surprising they were caught off guard by the notion that a Linux-based iPhone killer would have completely different priorities than preceding Linux-based phones. (Or, to paraphrase: "No terminal. Fewer buttons than a Nomad. Lame.")

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    10. Re:Android is not Linux ... by JWSmythe · · Score: 5, Informative

          You're expecting too much.

          Android is just another embedded *nix. I'm happy that it's Linux. You shouldn't expect it to have a whole bunch of scripting languages, and unnecessary servers.

          With all that said, it is a functional embedded system, where you *do* have the ability. to extend it do to all kinds of neat things.

          They provided hooks to just about everything in Java. I'm not terribly delighted with that decision, but it's what they went with.

          For most purposes, play is their package manager. For the majority of users, they'll never open a terminal. I do 99% of my phone stuff through the happy little touchscreen. That's the nice interface provided.

          If you really want the CLI package manager, you'll find pm, which does just about everything you'd expect from a package manager.

          You can get Apache, Perl, and pretty much whatever else you want on there. Is it going to be like developing for an x86 server or desktop? Not really. It's a different platform.

          If you're going to be developing for distribution, and not just for yourself, I'd recommend about the Android way to do it.. If you're doing it yourself, grab a copy of Perl for Android, and enjoy.

          If you're going to complain, well, that's up to you. At least research it a little.

         

      --
      Serious? Seriousness is well above my pay grade.
    11. Re:Android is not Linux ... by VortexCortex · · Score: 2

      While on the topic about fragmentation... Android is another type of linux.

      No, its not. End users and nearly all **developers** don't see it. The Linux kernel could probably be swapped out with a BSD kernel and few would notice. Even for those using the NDK and writing some C code they are probably making POSIX calls not calls to anything Linux specific.

      So, what you're saying is: RMS was right. It's the userland that makes the Operating System... In that case it should be called GNU/Linux... or just GNU for short...not Linux.

    12. Re:Android is not Linux ... by dtdmrr · · Score: 4, Insightful

      Still think the N900 is the most useful phone I've used/seen.

    13. Re:Android is not Linux ... by Windwraith · · Score: 2

      Well, I don't do perl, but it's trivial to cross-compile a Lua interpreter and get it to do stuff inside android. You can populate your scripting enviroment pretty well if you compile your own binaries (it's a bit tricky, not everything works, but you can indeed get stuff working).
      I also build bash (git version no less) for my cheap android phone, and you can build most coreutils, sed, awk and stuff. I got a very complete shell working, with all the advantages.

      You can also get a debian chroot to work pretty well, as a last resort. With some bash it can be made seamless, requiring only one command to get all working (mostly for ADB, it can be automated if using in the phone itself, but the input sucks...). I run stuff like bitlbee on my even cheaper chinese tablet, my 3g is more stable than my wifi, and connecting to the tablet I can keep stable communications. I have seen people running webservers like that too, and even forcing X to work (overriding the entire android display, though!).

      Considering I use more of my custom linux tools (same as desktop with minimal display changes) than android apps, that must mean stuff can get done. Give it another try, you can find cheap chinese hardware to experiment with for a pittance, and some samsung phones can be gotten cheap in second-hand markets or brand new as special offers.

      Oh, there's also a small hack of Connectbot that allows mouse input for terminals, so if you can code, you can make semi-visual apps using ncurses and that Connectbot. I lost the link, but it's somewhere in the google code site for Connectbot.

    14. Re:Android is not Linux ... by perpenso · · Score: 1

      So? Most of the time you could say the same thing about a Desktop Linux distro.

      Note that I was referring to both the user and the **developer** perspective. Android is a Java based environment, not a Linux based environment, not even a posix based environment.

    15. Re:Android is not Linux ... by GNious · · Score: 1

      You'll want to take a good, hard look at Jolla.

      Disclaimer: besides having preordered a Jolla phone, I'm not in any way affiliated with them.

    16. Re:Android is not Linux ... by GNious · · Score: 1

      here's to hoping Jolla somehow manages to combine the two worlds.

    17. Re:Android is not Linux ... by jones_supa · · Score: 1

      Guards! A Jolla shill!

    18. Re:Android is not Linux ... by gl4ss · · Score: 2

      ... but you could have done all that. if you're really salivating about the idea of doing cron jobs for making calls, you COULD HAVE MADE IT HAPPEN if you cared enough. heck, you could have distributed the solution you made for robo calling. sure, it might not be "simple" but it is doable. of course, chances are that if you needed trigger car functionality you could have found an app for it already...

      and you can't do that shit on iOS(non-jb) or WP.

      you could have used something else than eclipse for development(the new official sdk is idea based), you could have used ant for building or whatever the fuck you like.

      if you want speedy emulation run android-x86 in a virtualbox...

      if you just want a "linux phone" then get some used up N9.. it's the closest you'll get if you don't want to linuxify your android phone by installing stuff nobody ever actually seems to want on their android phones.

      --
      world was created 5 seconds before this post as it is.
    19. Re:Android is not Linux ... by Anonymous Coward · · Score: 1

      You got that wrong. YOU can't change the fact that Android runs on a Linux kernel and that's pissing you off so hard that you wanna deny that Linux is there at all. Seriously who the fuck are you to define Linux as Linux+Bash+X? Will it still be Linux when we switch to Wayland? Or does that make it something else too? What if I just use a frame buffer to run a SDL app without X? Does that disqualify it as Linux? At what point exactly does it become Linux?

      For fuck sake if the kernel doesn't make it Linux and Linux is only defined by its user space then fucking BSD IS LINUX. And while we're at it (since kernels don't matter) Wine is Windows and /. is Firefox OS.

      They went with a Linux kernel because it exists on more architectures than BSD ever had a wet dream about. I'm laughing at the "superior" design.

      Linux Linux Linux Linux Linux Linux Linux Linux Linux Linux Linux Linux Linux Linux get over it. And while you're getting over it try running those android drivers on BSD. ZMG ANDROID NEEDS LINUX DRIVERS???!!!! Yeah it does derp! Hey you know those fuck heads at Canonical that are doing that Mir thing? Yeah that Mir thing to run their Linux on? Yeah that Fucking thing? They use the same fucking drivers that Android uses... ON LINUX. Now you can call them "android drivers" if you really want but I guess that makes Ubuntu Android too.

      You're a fucking idiot.

    20. Re:Android is not Linux ... by Pokey.Clyde · · Score: 1

      Damn, do you need a Mydol?

    21. Re:Android is not Linux ... by gagol · · Score: 1

      Same is true for Debian: Linux kernel, FreeBSD kernel, same userland. Hence GNU/Linux GNU/hurd GNU/whatever...

      --
      Tomorrow is another day...
    22. Re:Android is not Linux ... by dindi · · Score: 2, Interesting

      I could have done a lot of things, you are totally right.

      Or I could have just set a cron job up or a shell script to do them .

      Don't get me wrong, if I cared for phones I would be programming for them probably (I am actually mostly working with Java console apps these days that process/monitor data) ...

      The big difference is that when you have the power of command line, you don't have to "write a program" for every little stupid task you want to achieve.

      Compare the effort of setting up a cron job (to stay with the example) to send you the location of the phone every 5 minutes.
      In cron (given that you have a theoretical program called GPSutil and SMSutil) would be
      crontab -e; put time, path GPSutil --currentlocation| SMSutil 12345667 ....
      in an other 10 minutes of tinkering, if there is no net, you could log it to a file, then send the batch when there is net again.

      You can also install the dev tools, start reading the API, the docs, figure out how to compile .. set up an app, see how you can run that in the background, use a crapload of unnecessary resources to keep an app running, automate its startup, check (if possible) how to restart if it fails ... write the app, deploy.. blablabla...

      And solution 2 is perfect ... will take you from cold start .. at least 2 weeks.. more if you are not a Java dev.

      Solution 1 for someone using linux for almost 20 years : 15-30 minutes, if you really polish it.

      It is like the thing I always tell to the windows admins/programmers:
      solve this problem: open a file, and replace every instance of "blabla" but only if it is the first word on the line with a tab before.....

      You can write an app and regex, you can install VI or SED.... the difference, is that my preferred OS (osx or linux) comes with that installed, I just need to chain them together to get what I want .. and I am done before you found it on google what to install

    23. Re:Android is not Linux ... by PurpleAlien · · Score: 3, Insightful

      Which is why I still have an N900 new in the box to replace my current N900 should it die.

      --
      My blog, if you're interested: http://www.purp
    24. Re:Android is not Linux ... by Billly+Gates · · Score: 1

      Funny you mention this. When I got my first (and last) Android phone, I was honestly expecting a somewhat functional/scriptable Linux environment with Perl, some web server, and a sane package manager. I imagined that I would be able to script behaviour and set up a cron job to make a call or connect to the net......
      I did not even consider, that what I was getting was nothing like that. Besides this little surprise I hated the phone, the experience, everything about it.. including the uselessly slow emulator and the whole eclipse-based dev environment.

      I am curious as to what you replaced your droid with?

    25. Re:Android is not Linux ... by Billly+Gates · · Score: 1

      OR download Java and the free Android SDK that comes with preconfigured Eclipse.

      FYI DISABLE THE JAVA IN YOUR ADD-ONS in IE/FIREFOX WHEN YOU ARE DONE.

    26. Re: Android is not Linux ... by JWSmythe · · Score: 2

      Ya, I've seen this kind of troll before..

      Most of his argument is that the UI is different. It's like saying that if you don't have a Gnome/KDE/Unity UI, you're not running Linux..

      As a sysadmin, when I'm in a shell on Android, I see Linux. When I'm in a shell on a Mac, I see a Unix. When I open a cmd.exe window on Windows, I see Windows.

      I was having some fun with some of my older Android phones a couple weeks ago. I put Dropbear Server II on. I had 4 shells open to 4 phones. I was remounting filesystems, moving files, using wget to collect stuff from my server, installpkg packages (with pm), chmod'ing files, and rebooting as I saw fit. It's just another *nix, and by his own admission a barely modified Linux kernel...

      If it looks like a bear, and acts like a bear, and everything else says it's a bear, it must be a spherical chicken in a vacuum.

      --
      Serious? Seriousness is well above my pay grade.
    27. Re:Android is not Linux ... by mrchaotica · · Score: 1

      What did you expect from a consumer-grade cellular phone?

      Maybe the same thing he'd expect from a consumer-grade laptop (but with a smaller screen and less power)? Is that so unreasonable?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    28. Re:Android is not Linux ... by gmueckl · · Score: 2

      You are wrong. Android has a C interface that is very POSIX conformant. It is there for applications to use. Google offers all the tools you need to make use of that.

      --
      http://www.moonlight3d.eu/
    29. Re:Android is not Linux ... by phlawed · · Score: 1

      Speaking of which, please check out the Neo900 project.

      --
      Dag B
    30. Re:Android is not Linux ... by gmueckl · · Score: 1

      Very few apps use it? Everything that is ported from other platforms is using the NDK, Or do you think that apps like Firefox, Chrome or Opera have been rewritten in Java? And then there's all the cross-platform games.

      --
      http://www.moonlight3d.eu/
    31. Re:Android is not Linux ... by gmueckl · · Score: 1

      Well, and how does it change the nature of Android that you can write apps entirely in C without a single line of Java anywhere? Google even ships demos that do just that.

      --
      http://www.moonlight3d.eu/
    32. Re:Android is not Linux ... by hairyfeet · · Score: 1

      Which is why I never understood why the FOSS advocates cheered android...what is the difference, really? It doesn't support the four freedoms, the drivers are pretty much all proprietary, and it takes an act of God and skills beyond the majority to unlock many of the phones. I looked into unlocking my LG and it was over a page long with half a dozen points where it said "If you get this wrong or it fails YOU BRICK YOUR PHONE" which was enough to make even an old techie like me reconsider, a regular user would have turned back at the page and a half of insanely complex moves. Hell most folks can't even re-partition their PCs, and they are supposed to re-partition their phone by CLI? Not likely.

      So I honestly don't get it, and this is coming from somebody that loves his Android phone but frankly Android has more in common with TiVo than it does with Linux. I may have my arguments with the FOSSie faction but I give credit where credit is due and the big difference between Linux and the other 2 is how trivial it is to change anything from the kernel on up. Don't like the DE? Change it to one of a half dozen or even go headless if you want, don't like the video subsystem? Rip out X11 and replace it with wayland or Mir, same goes for Pulse with ALSA and even the OS can be swapped out while keeping your data and settings. With Android honestly you have to jump through just as many hoops to unlock it as you do your average iPhone and it involves the same risks in a lot of cases, and even if you do there is a good chance that the community won't have drivers for your model, so what is the diff?

      --
      ACs don't waste your time replying, your posts are never seen by me.
    33. Re:Android is not Linux ... by perpenso · · Score: 1

      Well, and how does it change the nature of Android that you can write apps entirely in C without a single line of Java anywhere? Google even ships demos that do just that.

      Stock Android does not expose the kernel. The developer has to **customize** the Android run-time to get to the kernel. Google merely provides a mechanism for an app to do so, the Java Native Interface (JNI). The developer puts all the C/C++ code in a library with a JNI wrapper. Starting from a Google example that has all the necessary Java, JNI, makefiles, etc pre-made is not the same as having no Java anywhere. Having a C library that implements nearly all of your app does not change the Java nature of Android nor the fact that stock non-customized Android provides not access to the Linux kernel.

      That said, even if your app is basically written in C/C++ you are probably accessing and making calls to Java via the JNI. Its the only way to access the Android API and its resources.

    34. Re:Android is not Linux ... by gmueckl · · Score: 1

      I'm sorry to say it that way but you are wrong. Google has documentation and sample on writing Android activities without any Java code involved. Take a look at samples/native-activity in the NDK. That's a single C file plus the XML file you need to describe your app. No Java code to go inbetween and make JNI calls.

      --
      http://www.moonlight3d.eu/
    35. Re:Android is not Linux ... by perpenso · · Score: 1

      I'm sorry to say it that way but you are wrong. Google has documentation and sample on writing Android activities without any Java code involved. Take a look at samples/native-activity in the NDK.

      Note how Google's sample native code begins with "#include "

      You seem to be confusing you having to write additional Java or glue with there not being any. It is there, Google has merely provided it. The main process for your app is Java running in the Dalvik VM. Your native code is a C library effectively extending the Android run-time, it is running at the JNI stubbed library level of the Android Software Hierarchy.

    36. Re:Android is not Linux ... by bingoUV · · Score: 1

      So you missed where Samsung and HTC have vowed to keep their bootloaders open and have been true to it ever since, and Sony has an unlock bootloader on their own website, that works for a majority of their Android phones?

      Don't like the DE? Change it to one of a half dozen or even go headless if you want, don't like the video subsystem?

      Don't like the application launcher? Change it to one of 2 dozen. Even access your phone solely through VNC. Don't like your default video player? Change it to one of 10 available. All this even without rooting or unlocking bootloader.

      Rip out X11 and replace it with wayland or Mir, same goes for Pulse with ALSA and even the OS can be swapped out while keeping your data and settings

      Within 5 years of GNU/Linux, this couldn't be done for GNU/Linux either. So wait 10 more years, and I don't see any reason this can't be done for Android too.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    37. Re:Android is not Linux ... by dindi · · Score: 1

      but..

      Can that achieve hearing god through your speaker cat /boot/vmlinuz >> /dev/speaker (or audio, or sound or .. .whatever your device creates)

  15. Re:How to attract developers? by DaveV1.0 · · Score: 1

    In other words, he is not willing to pay the going rate to get the work done. Same difference.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  16. Plan 9, too, is dying. by rolfwind · · Score: 1

    I feel the same way about Plan 9 / Inferno.

    1. Re:Plan 9, too, is dying. by gagol · · Score: 1

      Yes, just search plan 9 and read the wikipedia page. Effortless information tends to be forgotten rather quickly.

      --
      Tomorrow is another day...
    2. Re:Plan 9, too, is dying. by Cassini2 · · Score: 1

      Plan 9 was Bell Labs successor to Unix. It was used to test many new concepts like Unicode and UTF-8, and has some pioneering features for clusters/networks of computers. I think most current operating systems including Windows and Linux have implemented concepts that were tested on Plan 9. For more information try plan 9 google search.

  17. Crowdfunding specific compatibility features by Statecraftsman · · Score: 5, Informative

    You might want to check into a class of crowdfunding sites that exist to fund features in free and open source software. The two main ones I could find are:

    https://www.bountysource.com/
    https://bountyoss.com/

    1. Re:Crowdfunding specific compatibility features by Jonah+Hex · · Score: 1

      Thanks this might be just what I need, I've been looking for a bounty/escrow for an I Can Haz Chat to IRC Bridge using their API.

  18. Like Linux, thank Corporations ... by Anonymous Coward · · Score: 3, Insightful

    "Hey guys, I really love your software... I'd be totally unwilling to pay for it, but I'd really love it if you did all of this work for me, thanks." The problem with the Linux software ecosystem is that it does not run on gratitude alone, as much as some of the users would love to think that it does.

    In truth, Linux is largely subsidized by various commercial corporation. If it had remained a hobbyist effort it would be far far behind where it is today.

  19. Re:Welcome to Linux by Windwraith · · Score: 4, Insightful

    No, it's the same as running BSD :P

  20. Is there something similar that can tip a project? by ron_ivi · · Score: 3, Interesting
    Or perhaps better - tips attached to specific bugs and feature requests in projects - and held in escrow - so they go to people who commit specific fixes to the project?

    I'm not too interested in an escrow service, but personally I liked tvtwm enough I might join a bounty program to bring it back into the mainstream.

    I'd gladly toss a few bucks to fund a bounty to get it back into a major distro.

  21. Innovate, explore, move forward. by thecorrectline · · Score: 1

    I get that you don't like change in this area of your life, but without active development and few users the writing is on the wall here...

    Fluxbox? Enlightenment? Awesome? All three can be customized and skinned/themed without "coding in a meaningful way".

  22. Progress by WillKemp · · Score: 1

    The days when desktop environments improved as time went by seem to have gone. Now they just get more and more annoying with every iteration. Unfortunately that's the way of the world and there's nothing to be done but to grit your teeth and put up with it. Hopefully things will change again before too long.

    1. Re:Progress by vtcodger · · Score: 1

      The days when desktop environments improved as time went by seem to have gone. Now they just get more and more annoying with every iteration.

      I have no mod points (I rarely post here anymore). But I think this nails a very real and quite annoying problem. Software of all sorts tends to start off simple, easy to use, but buggy and limited. As time goes by, problems get fixed, disconnects are resolved, obvious missing capabilities are provided. Then crap creeps in. And eventually the product becomes mostly crap. Bloated, slow, clunky, and -- too often -- virtually or actually unusable. Doesn't always happen. Windows (and Unix) hardware detection and driver installation seems finally to have reached the levels we were promised in 1995 ... and 1996 ... and 1997 ... and .... But it does happen often.

      I've never used Icewm except for maybe 15 minutes to see if it looked usable. As I recall, it did. But does is really need much fixing? Would fixing it make it better? Would "fixing" it risk ending up with an incoherent, increasingly incomprehensible, shambles as has happened with Internet user interfaces, the Microsoft Windows UI, and a multitude of other software? If all Icewm needs is a few modest fixes, maybe it really doesn't need anything more than finding a student or enthusiast looking for a project.

      If it needs extensive serous work, that's a different issue and probably does involve money.

      And is Icewm really better/more useful than Fluxbox or Openbox or other more or less OK windows managers that may already provide all the capabilities the OP needs?

      --
      You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
    2. Re:Progress by gagol · · Score: 1

      complete nonsense.

      --
      Tomorrow is another day...
  23. Re:How to attract developers? by HiThere · · Score: 2

    Not precisely. He doesn't think of himself as the only user. Micropayments is a perfectly reasonable model, that has just never taken off. Pertially because there's usually so much overhead to managing them. And THAT is partially because of legal constraints.

    OTOH, please note that I did say "partially". There are other reasons that it hasn't taken off, and the "free rider" problem is one of them. There's no obvious way around that. But someone *might* find a way if the legal obstacles were removed, and the overhead were lower.

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  24. Start a corporation by retchdog · · Score: 1

    Not an eeeevil corporation, not even necessarily a formal one. Post on forums (like you've already done here) with a solid proposal about chipping in (unlike you've done here); start a webpage; whatever. I guess you can even do a Kickstarter, unless it's required for the host to actually do the work. Start negotiating with developers, say that the $ is on its way or in hand.

    Seems like a lot of work? It is, and you probably won't do it. But unlike waiting for someone to be inspired to passionately solve the problem you care about, it has at least a snowball's chance in hell of actually happening.

    It's almost like those evil corporations are actually providing a service which random developers, with no motivation but fun and ego, can't or won't provide.

    --
    "They were pure niggers." – Noam Chomsky
  25. It's called marketing. by Qbertino · · Score: 5, Insightful

    It's called marketing. RubyOnRails wasn't the first web framework and it certainly wasn't the best. In fact, it was pretty shitty. But it was the first that had a professionally designed website that advertised its benefits and a screencast that explained and demonstraded them. The pratically invented screencasts. Weeks later slashdot was filled with Rails fanatics.

    The first version of the Zope Webapp Server came out roughly a decade before rails and still was notabliy superiour to any other WebFW, Rails included, in all aspects. Yet nobody cared. Why? That's why. Bland website? Nothing flashy? Can't find what I'm looking for? Backend UI without good looking buttons? Won't adhere to the loudmouths and hippsters and won't get attention, won't get critical mass, will lose eventually. It's that simple, even in the FOSS world nowadays (Rails actually sought to that, btw.)

    If you really want to bring ICEwm (back) into the limelight, join the team, update their 12 year old website, bundle a new version with good looking modern themes and your tweaked setup, give it a new version number and do a little rattling on related online forums. Once everything is in place, tested, up and running that is. If you've done your job well, userbase will rise again and IceWM 2.0 will the the Hip WM of 2014. Fluxbox, a Blackbox fork, gained hippness status some years back the exact same way. Neat website, one or two nice little extras, screenshots, a well kempt miniblog and everybody went "Oh, look, new and shiny."

    That's just about all there is to it. But don't you dare think good marketing isn't work and isn't worth giving as much thought as your projects software architecture. It's more work and - most of the time - even more important than that for the success of a project. Even in FOSS.

    Good luck.

    --
    We suffer more in our imagination than in reality. - Seneca
    1. Re:It's called marketing. by nigels · · Score: 3, Interesting

      I second this. What IceWM needs most is a project manager and an evangelist.

      Do a refresh of the website, reach out to all the known historical developers, start a blog about IceWM - little tutorials about what is good about IceWM, triage the bugs the best you can without diving into the code. If the debian and/or Fedora packages are missing, create some or work with the packaging folks to make them better. Convert the revision history to git and put it up on github, if possible.

      I think there is a decent backlash going on against Unity and Gnome 3. I'm currently using Cinnamon, but I'm fairly willing to give something old-school a try. I was happy with KDE3, then went to Gnome2, and really feeling that Unity is both unstable and inappropriate for work. (I do want to search for things locally without that going to Amazon for advertising purposes) Cinnamon is workable for me, but I'm not rusted onto it.

      Get the pitch right - it's probably not for Grandma, but it might appeal to seasoned developers who don't like instability and don't like any "surprises". One thing that's valuable to me is having something agreeable without much customization. I tend to have various machines with various distros installed, something solid and consistent across all those is a valuable feature to me.

      - Nigel

    2. Re:It's called marketing. by marcovje · · Score: 1

      Marketing is indeed not just about dolling up old hat. It is primarily about finding an audience, and give feedback to implementers about what the customer might want.

      (and btw

      1) I think the RoR and Zope examples are totally irrelevant, since they were in a "hot" area at the time. Minimalistic WMs are not, unless you get default on the next Raspberry Pi)
      2) I think the "I can't code for sh*t" argument of the original can only be invoked if you have at least 2 years of experience in a documenting team. Just to make sure you know what your talking about when calling people to invest their free time.

    3. Re:It's called marketing. by cerberusss · · Score: 1

      reach out to all the known historical developers

      I dunno about this. Suppose I'm playing D&D. And my wizard finds heaps of treasure in a dungeon. Do you think I should call upon the ancient lords of the Undermountain to contact all the liches who once owned part of this treasure?

      --
      8 of 13 people found this answer helpful. Did you?
  26. Try KDE4 by Windwraith · · Score: 1

    You can configure KDE4 pretty well, and even if you can't, you can always get someone to write a plasmoid in QML or python or something. Probably for a bounty you can afford, or even asking nicely, who knows.
    Alternatively, there's Gnome 3, but I haven't tested that one much.
    Even more alternatively, there's FVWM...you can do pretty much anything on it, if you can afford the time.

    I got my KDE using an Unity-like look and using some Unity apis for menus and displays. Didn't need to code at all (and any code I did for custom displays is pretty much bash and a python helper, about 10 minutes of coding).
    Of course, this only looks like Unity (I always used sidebars anyway, even in windows), but behaves more like I want it to behave.

    1. Re:Try KDE4 by Arker · · Score: 1

      What's the KDE base system? 500 megs or more these days? I havent looked at it in years. But tell me, why would I download and install all that for a window manager when I can get one that works better in less than a meg? Really?

      Dont get me wrong, KDE is ok. A lot better than GNOME. But I think it's absolutely ludicrous to talk about installing KDE just to get a WM. Which is what we are talking about. ICEWM, it's even in the name.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    2. Re:Try KDE4 by Billly+Gates · · Score: 1

      That is like saying Windows 1.0 is soo much better than Windows 8.Or being hung is soo much better than being stabbed.

      I prefer neither when you compare gnome-shell and KDE 4. KDE 3.5.x may it rest in peace. I kept obsolete versions of FreeBSD 4.x for years to keep running KDE 3.x but it was time to move on many years ago.

      What a shame since Linux had such great promise in its day. It is time to move on now for me.

    3. Re:Try KDE4 by Windwraith · · Score: 1

      Dude, it's disk space, not RAM. If you got space for a single movie you got space for KDE. That's like the lamest "hater" argument ever. I am not going to believe you can't afford the network and space for a single movie in 2013. Specially with your ID. Hell, you probably got better network than my flimsy and capped 3g.
      Also with my setup (and being 64-bit, which makes binaries a bit heftier), it's like 250-300mb or less with all the -dev packages I need, so your measurement seems pretty arbitrary. Did you even bother checking? You realize you can customize your install and it's not a monolithic package in any distro, do you?

      Also I used IceWM before KDE, precisely. And yeah I don't miss it a bit nowadays. Kwin's automation is a killer feature nobody ever talks about, it's fast, it's customizable. I boot with less than 90mb of RAM used until I open firefox.

      And, yes, the guy is asking for something that can be configured. I also suggested FVWM if you recall.

      But hey, it was your choice to be an ass on the internets. Unless you happen to live in a rural place with no available internet connection (how are you posting here then? cibercafé?) and the disk space of an early 90s computer, your argument is pretty much arguing for the sake of argument.

    4. Re:Try KDE4 by Windwraith · · Score: 1

      You gotta move on, then? And so what? Why should we care? Hurry up and move to OSX or Windows, and bring the negavitity to them instead. Or were you expecting us to go NO! WE NEED YOUR MARKET SHARE!. We don't need crybabies, they are dime a dozen.
      I use Linux because as a developer it's easy to set up, it's easy to automate and I don't dislike the apps, specially nowadays where I can even play steam games on it. Not for you? Then why are you complaining about it? Just move on to what you like instead of using your departure as some form of blackmail! You even save time complaining about it on the internet.

    5. Re:Try KDE4 by Arker · · Score: 1

      "Dude, it's disk space, not RAM."

      It increases RAM requirements significantly as well.

      "If you got space for a single movie you got space for KDE."

      And what if I have devices that dont have space for a movie? Particularly free and un-needed?

      Or what if I have more disk and ram than I know what to do with, I am still supposed to go through the equivalent of downloading a movie just to manage my windows? Whether I have the space/ram/time/bandwidth or not does not settle the question of whether or not I really want to use it on this in particular.

      "That's like the lamest "hater" argument ever."

      Wait a moment, let me get this straight, preferring a window manager to your DE makes me a 'hater?'

      FFS grow up.

      "You realize you can customize your install and it's not a monolithic package in any distro, do you?"

      It's still hundreds of megabytes for the absolute minimum install just to get kwin (the window manager in KDE) up and running. Why would I do that when I can get a WM I like better, and do it with a tiny fraction of the resources?

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    6. Re:Try KDE4 by Windwraith · · Score: 1

      Grow up? How funny, you were the one doing the reply in the first place, ignoring other things I recommended.
      Perhaps you grew up too much. You are judging a completely useful piece of software because it doesn't work in your fossil device? That's like blaming Windows XP for not running on your Commodore 64.

      But, how mature are you when you can't let a friendly recommendation pass without bashing it for being too heavy? Don't try to sound like the better man, your childish reaction to my recommendation came first, and you are unhappy because I challenge your opinion? Like a child does?
      And, yes, you seem to be a hater because your commentary was pretty uncalled for when I also recommended other things. Do you think people can't read the parent post and see the mention of FVWM there?

      But, like this reply you just produced, your replying is selective to support your argument better. More kiddie tactics.
      And sorry, if your devices can't run new software, just stay away from it, and don't bash people when it's recommended because it's too much for your obsolete machines. Progress is not going to cater to you only, you self-centered bigot.

      Grow up, will you?

  27. Re:Welcome to Linux by Anonymous Coward · · Score: 1

    Nah.

    'Linux' is a shortening of GNU/Linux, an open source OS built on the Linux kernel and available in many rather different distributions.
    Android is a different OS, also build on the Linux Kernel, available from Google.

  28. what's there to be done? by stenvar · · Score: 3, Insightful

    I use icewm pretty regularly on some machines. It hasn't changed in years, and I like it that way.

    Is there actually anything that needs doing?

    1. Re:what's there to be done? by gomadtroll · · Score: 1

      As long as some distro still packages it, I don't like/need change in my workstation either.

      WindowMaker is similar, used it for years, seemed to go unsupported for a while, lo & behold, it is active now.

    2. Re:what's there to be done? by phlawed · · Score: 3, Informative

      I agree it has been fairly resistant to breakage/bitrot. That may say something about the code quality.
      But do you actually compile from the original tarball? The last tarball is pushing 3 years by now.
      Building it gives an indication it needs an oilchange and a new filter.

      The bugtracker has a fair number of patches which appear to make sense. As do various distributions.

      So the short answer is: maintenance

      The longer answer is really up to whoever takes ownership of the code.

      --
      Dag B
    3. Re:what's there to be done? by sslayer · · Score: 2
      I did some changes a few years ago to icewm that mattered to me. One of them was included in captnmark's official release. You can see the rest at my github.

      It's not much, but they solved everything I needed. If you need something in particular, maybe we could get an arrangement though I don't have now the time I used to have and just have a basic comprehension of the code.

      As stenvar says, what is there to do? It's been good enough for years.

  29. Re:There is a 2nd alternative ... by DaveV1.0 · · Score: 1

    That assumes you can convince a major corporation that it is in their best interest to fund development. Linux is a major server operating system. IceWM is a minor and little used window manager. There is a big difference.

    There are reasons for corporations to support Linux, Apache, Mozilla, and some other projects. But, there is no reason for corporations to support the majority of projects because the corporations don't get anything out of it.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  30. Get the government involved by RogueWarrior65 · · Score: 2

    Lotus died a long time ago. Everyone on the planet uses Acrobat for electronic forms. Yet the US Government requires you to use crappy Lotus-based forms. Not only that, you have to submit them with Internet Explorer on Windows due to a crappy digital signature implementation that only works on IE and Windows. So, if you want keep an obsolete technology around, hire a lobbyist.

  31. Re:Welcome to Linux by petteyg359 · · Score: 3, Interesting

    That's utterly inane attention-grubbing bullshit that needs to stop because it makes all of us look bad. Linux is not GNU/Linux any more than Windows is "GNU/Windows" after you install Cygwin. Do you use the Cerf/Internet every day, and sometimes drive a Lenoir/Car? What did you have for Albertson's/Lunch?

  32. Re:How to attract developers? by bmo · · Score: 2

    If you want evidence, just look at the high profile projects that have had annoying little bugs that lasted for months or even years because hunting down the bug and fixing it would be boring.

    You mean like Windows itself?

    Your argument is nonsense.

    --
    BMO

  33. Like 16-bit DOS applications by msobkow · · Score: 1

    Like 16-bit DOS applications and Windows XP, all things eventually reach end of life.

    Get over it and move on to something else.

    --
    I do not fail; I succeed at finding out what does not work.
    1. Re:Like 16-bit DOS applications by vtcodger · · Score: 1

      Like 16-bit DOS applications and Windows XP, all things eventually reach end of life.

      Get over it and move on to something else.

      T'aint broke so it's time to discard it?

      Might want to consider the remote possibility that progress and motion are not always synonymous

      --
      You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
    2. Re:Like 16-bit DOS applications by Billly+Gates · · Score: 1

      Like 16-bit DOS applications and Windows XP, all things eventually reach end of life.

      Get over it and move on to something else.

      PDP-11 support is still a big business as many businesses wont leave them to run their mission critical factories and expect endless support. They run XP too and will do so for many years to come right up there with IE 6.

      Software does not die if it works.

    3. Re:Like 16-bit DOS applications by msobkow · · Score: 1

      But they pay to have it done.

      That, in a nutshell, is the article poster's problem. They want support for ancient technology, but can't pay for it.

      That means it's dead. It's defunct. It's passed on. It's kicked the bucket. It's pushing up daisies.

      So, yes, time to move on.

      And if it works, what maintenance is he asking for? If that's the case, then the package maintainer's "maintenance" is sufficient to keep it in a coma.

      --
      I do not fail; I succeed at finding out what does not work.
  34. The closed source story is the same, except worse. by robbak · · Score: 4, Insightful

    You make this point yourself. If the developer of a closed source package gets bored of it, or it is not profitable (which itself is a high bar for a most producers!), or both, they will drop it. Anyone who came to rely on it is completely stuck, as they cannot fix the most trivial or sexy bugs. They have to live with it until advancing technology and other changes make the program fail completely, and they will have to retrain.

    If it is open source, then at least you can recompile and/or port to a new OS. You have the option of paying someone to fix a problem. You have none of those options if the closed-source producer of a package arbitrarily decides to drop it.

    --
    Prediction for end of Universe #42: Fencepost error in Quantum_bogosort.cpp
  35. Zawinski's Law of Software Envelopment by Anonymous Coward · · Score: 2, Funny

    I still doesn't have a builtin mail client :)
    On the plus side jwm has seen quite a bit of development recently.

    1. Re:Zawinski's Law of Software Envelopment by H0p313ss · · Score: 1

      Please explain to me in short simple terms why a WINDOW MANAGER needs a "built in" mail tool.

      Do NONE of the dozens of existing mail tools work with icewm?

      --
      XML is a known as a key material required to create SMD: Software of Mass Destruction
  36. I wouldn't mind seeing icewm going again either. by aklinux · · Score: 1

    Never could figure out why it didn't catch on better than it did. I think it just lacked proper advertising.

  37. Re:Welcome to Linux by Jah-Wren+Ryel · · Score: 4, Insightful

    Linux is not GNU/Linux any more than Windows is "GNU/Windows" after you install Cygwin.

    That is an intellectually dishonest comparison. The more accurate comparison is "MS/Windows to GNU/Linux" - basically all of the userland on Windows depends on MS code. Similarly pretty much all of Linux userland depends on GNU code - gcc and glibc have practically 100% coverage for Linux userland's dependency on GNU software without having to get into the nitty-gritty details of exactly what other GNU software is in a typical distribution.

    I'm not particularly in favor of GNU/Linux as a term but I'm not particularly against it either. Right now, in this post, what I am against is bogus arguments either way.

    --
    When information is power, privacy is freedom.
  38. i3 tiling window manager by oliver.bestwalter · · Score: 1

    ... fits your requirements of being easy to configure and not getting in your way.

  39. Re:How to attract developers? by Anonymous Coward · · Score: 1

    No, he's right.

    I have nothing to do, so I spend all of my time finding his posts and down modding them with all my different accounts.
    It takes up so much time I even stopped contributing to a certain open source project.

  40. Re:Welcome to Linux by mellon · · Score: 3, Interesting

    Indeed. The problem is finding enough icewm users to fund a programmer to do maintenance on it. What the OP really ought to be doing is not looking for someone to work on icewm, but for fellow users.

  41. Icy Goodness by markdavis · · Score: 1

    We use Icewm for a Linux/X thin client environment (IceWM and apps runs on the host, not the desktop machine) and it works really well. It is simple, fast, reliable, low-resource, and controllable. I would hate to see it die or fade away. It does lack a few features that I had hoped would be added, but anything other than bug fixes stopped several years ago.

  42. Re:How to attract developers? by ChrisMaple · · Score: 1

    You want them to do boring, tedious work. Hmmm. What could you do to make people want to do boring tedious work? I know, pay them!

    1. Announce a course in window manager design.
    2. Collect tuition.
    3. Give your students the current source code for icewm.
    4. Tell them their assignment is to make icewm compatible with modern Linux.
    5. Profit!

    --
    Contribute to civilization: ari.aynrand.org/donate
  43. Look Around by enter+to+exit · · Score: 1

    I don't get this kind of mentality.

    The OP is using a WM because it's reminiscent to the WM of a dead OS he liked from the early 90s.

    If developers do anything more than maintenance work on the code, it's going to be less and less like his beloved, "Presentation Manager" and more like a modern WM, giving him less and less incentive to actually stay with IceWM. So what exactly does he want? He seems to be sticking to IceWM out of habit, perhaps he should look around at other WMs and not limit himself.

    When i was running Linux I used IceWM+PCmanFM for desktop icons, It's a fine for what it is, a loose imitation of the classic windows UIs. Like all cloneware, there comes a time when interest wanes, and the code is deemed "done".

    1. Re:Look Around by Arker · · Score: 1

      "So what exactly does he want?"

      What he wants, and your analysis practically fell across it without you ever noticing, is simply someone to do maintenance work so he can keep using the window manager he knows and loves. What's so wrong with that?

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
  44. Re:Welcome to Linux by bigdavex · · Score: 4, Funny

    It's properly referred to as Free Cell/Windows.
     

    --
    -Dave
  45. A DE by any other name by Osgeld · · Score: 1

    is really the same DE, really seriously, tell us what ICEWM does so much better than any other DE (not counting the recent crimes against useability from the big names) move along, which may be extremely difficult since your referencing OS/2 as a crowning glory in freakin 2013. Dont get me wrong I like presentation manager and ice wm as well, I have them both loaded up on a fat pentium MMX laptop as a dual boot.

    but its not cause its the best thing ever made, its more along the lines of its neat and not windows mentality

    1. Re:A DE by any other name by Arker · · Score: 1

      First off it's not a DE it's a WM. A Window Manager, not some Detestedesktop Environment.

      And while it's not my WM of choice, there is a lot to be said for a WM rather than a DE. It has a lot lower requirements in terms of memory or storage or dependencies, and it also has a lot less junk to get in the way of its core functionality. And since the codebase is smaller it's much less difficult to audit as well.

      There are several great old WMs out there that are mature, feature-complete, and nearly bug-free at this point. Companies arent interested (companies make profits selling latest and greatest and herding customers on the upgrade treadmill) and unfortunately in many cases neither are coders (maintaining a project that releases two updates to stomp minor bugs over 3 years does sound slightly boring, and isnt likely to help much in a job interview either I guess.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    2. Re:A DE by any other name by Osgeld · · Score: 1

      you forgot another feature

      they are all dead, move on to something modern instead of beating a dead horse, there are plenty of options

      (and leave it to a linux douche to get all bent out of shape over a DE vs WM, who gives a shit, its its not TWM then its a fucking DE)

  46. Re:How to attract developers? by tftp · · Score: 1

    Micropayments is a perfectly reasonable model, that has just never taken off.

    And why is that? You are answering:

    Partially because there's usually so much overhead to managing them. And THAT is partially because of legal constraints.

    Overhead? I can't think of much overhead in sending a fraction of a BTC, or in sending over PayPal. There might be a problem if you are an Amazonian native who lives in a rainforest and has no Internet. But then you aren't very likely to be a user either. Everyone else, who has access to the Net, can pay.

    OTOH, please note that I did say "partially". There are other reasons that it hasn't taken off, and the "free rider" problem is one of them.

    Somewhat yes, I agree. Very often optional payments are optimized away. Also, a small payment is seen as not influential, and therefore not necessary. People are conditioned to not spend their money left and right because they have needs in the real world, and those needs are not optional. For micropayments to work you need a new man. Good luck with that. People are, generally, opportunistic gatherers and freeloaders. They do contribute sometimes, but not too much and not too often. A modern society requires too much labor from an individual to just stay alive, pay for the house, and for the children, and for healthcare... very few people come home from a 12-hour hacking at work and immediately sit down for another 8 hours of hacking at home. Not everyone works as hard, but good coders usually do - and you want only those.

  47. Re:Welcome to Linux by Arker · · Score: 2

    "Right now, in this post, what I am against is bogus arguments either way."

    And you did that quite well.

    (And if there was a big meta-package I could install on Windows to add all the GNU tools, ported and compiled for Windows, THEN I might talk about GNU/Windows. I keep waiting for someone to package up ReactOS like that to support netbooks, but I digress.)

    And btw, I think a big part of why Stallman draws a red line on his terminology here is out of fear of exactly the sort of deliberate confusion that was used above us in this thread. 'Android is linux' is technically true, but since so many people hear 'linux' and think of a fully functioning GNU OS that happens to use linux as the kernel, it's very (deliberately) misleading. Android is really little if any more open than OSX. Both exploit a free kernel by hooking it into unfree userland and incorporating unfree drivers without which it is no longer functional.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  48. Re:How to attract developers? by Arker · · Score: 1

    It doesnt happen in exactly the same way with proprietary software. Instead of the developers going off to chase whatever they think is new and exciting, they get sent off every so often to chase what marketing thinks is new and exciting, but either way projects are never finished. Programs which become generally mature, in danger of reaching bug free and feature complete, are always phased out in favor of new and shiny one way or another.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  49. An answer (but didn't quite get your point). by Anonymous Coward · · Score: 2, Informative

    First, a short background: I played with OS/2 Warp for a really short time, but had a lot of things to do and then Linux came. So, no cigar here.

    I have a couple computers -- the most powerful run KDE4(Mageia); for the weaker/older I've been experimenting with Xfce and LXDE and since the latter will use Qt, I'll probably use it where KDE is not possible.

    Finally, for really weak machines I've been trying some simpler distros. Porteus is incredible nimble, but I'd rather have a Debian-based distro. Which led me to...

    antiX: a distro which can use a selection of window managers, iceWM included. I'd recommend that you try jwm, as others already said, 'cause I found it to be configurable to my taste (btw, I don't click a window to raise it; I click its title... that is because I may want to work with a certain window disposition and even paste things on a window I don't want to bring up and wreck my desktop layout).

    Now, what I don't get:

    If you got an older machine (or are helping lots of people in need like Ken from Reglue/Helios), ok, I recommend jwm by Joe Wing if you really need to stick to something akin to icewm.

    If you got a decent machine, depending on its age, I'd suggest waiting for LXDE-Qt and perhaps using Xfce in the mean time... it can be tweaked to look like iceWM (though I have no idea about OS/2's capabilities).

    Or, better yet, go for KDE4. It can be configured to work like mostly anything... from Windows (yuck!) to OS X... though the ride is not without emotions. Here the problem is the opposite: "how can I make those KDE developers stay put and don't change things so fast, or at least be better at marketing the new features?").

    I don't get why you don't want a desktop, since a desktop can be made to work just like a window manager (for the most cases, at least). I've seen your comment explaining it, but certainly you don't think icons are mandatory in KDE (or Gnome, btw)...

    And, btw, iceWM is nice. It's development slowed, maybe, because it already attained perfection. Why are you worried about it?

  50. Re:How to attract developers? by Livius · · Score: 2

    It's frightening how plausible that sounds.

  51. Re:How to attract developers? by Bite+The+Pillow · · Score: 1

    Not like Windows. With Windows, management can prioritize bugs with feedback from the triage team and their budget. And then assign those bugs to people, who get paid to find and fix the bug.

    Linux doesn't have this problem, because piles of companies employ people to fix what they want fixed. FireFox is funded, although I'm not sure how forcing people to work on specific things pans out - the "clownshoes" saga was the most ridiculous failure to diagnose a problem that I can remember, so not exactly a success story. Google funds/funded a lot of software develolpers on other projects such as Python, but doesn't seem to be in a position of forcing what to work on routinely. Dual licensing, like Qt and MySQL, means funding is available. The remainder of open source software projects are vulnerable to neglect, developer churn, and related problems due to not having a way to force attention.

    With FLOSS, sometimes the barrier is simply not having the hardware to be able to repro the bug, and thus being unable to fix it at all. Someone who has the hardware can fix it you say? Well, that person somehow decided that the software was worth using, wanted to fix it, had the right hardware, and was capable of debugging. All of which is missing in the case of "abandonware". And most of which is missing if the bug even exists at all.

    And, one good way to keep or build interest in a project is to introduce the new features. Fixing a bug that isn't critical or affecting most people just means that people who can't use your product, still won't use it. The lure for new is the obvious draw. As it is with Windows, or any software with resource constraints. Is Windows your only counter-example? Because "boring" is completely different from "not financially worth it", which is where your example completely breaks down.

    Now, I'm not sure what your point was here:

    90 percent of closed-source software is crap too.

    90 percent of open source software falls in the categories of: builds on a limited number of distros, won't build on current build environments, isn't finished, works for the case of the author only, or any number of other definitions of "crap". This is not dissing open source in any way, it is simple numerical data. Closed source, by the numbers, is impossible to enumerate. The stuff that doesn't work mostly doesn't ship. The stuff that does ship is mostly functional for the given use case. It's certainly not "better". But, and this I think was the original point, open source that *doesn't* work is statistically more prevalent.

    The complication of having an all-volunteer workforce just means you can't sit someone down and force them to work, so you have to appeal to their sense of accomplishment, pride, sometimes ego, or whatever happens to drive them. Unfortunately for "phlawed" I'm not sure that anyone here knows which personality attributes to appeal to for the people who might be interested in maintaining his/her toy.

    How about finding an IceWM user's group and drumming up interest there? Because they might have more helpful contributions than a bunch of nerds involved in a dick-waving contest about how their view of the world is the only correct one.

  52. Re:Welcome to Linux by devman · · Score: 1

    Also GNU/Linux isn't an OS, its a description of a software stack. RHEL, Debian, Arch Linux, Trisquel GNU/Linux, Android etc are all Operating Systems.

  53. Re:How to attract developers? by hedwards · · Score: 1

    Yes, but it's free market crap that we pay for.

  54. Re:How to attract developers? by Oligonicella · · Score: 1

    If one guy writes the software, his salary is the price of said software.

  55. Re:Welcome to Linux by binarylarry · · Score: 1

    Except that Android's userland is also open source and many of the drivers are open source.

    The exceptions are usually due to the hardware manufacturer, which is a problem on desktop linux as well (Nvidia driver, the assholes at broadcom, etc).

    --
    Mod me down, my New Earth Global Warmingist friends!
  56. rephrase: by noh8rz10 · · Score: 2

    rephrase: i really want hollywood to make "throw momma from the train 2: grandma!" I cannot afford to bankroll the whole movie but I will happily buy a ticket when this comes out in theaters. how can I make this happen?

    I was originally just going to say this to be a dick, but in rephrasing the question I think we see the answer. Look at the story behind Veronica Mars 2. It was fans who pushed for it and ultimately funded it through KS. The lesson here: even though Hollywood was apathetic, fans won out because of their collective ferver.

    solution for @phlawed: build a rabid fanbase. Don't worry about the coders, worry about the users. the coders will come.

    Of course, if you don't have the time / inclination to work towards this goal, and nobody else wants to do it either, then you're @phucked!

  57. Re:How to attract developers? by tftp · · Score: 1

    The end result will be more frightening. Do you want to use a WM that had been written by students? A WM crash may easily ruin your day.

  58. Re:Welcome to Linux by kermidge · · Score: 2

    I wonder if phlawed subscribed to https://lists.sourceforge.net/lists/listinfo/icewm-user whether he might then be able to send out a request for members willing to kick in towards paying a maintainer. With enough users they might also have fewer hops than six-degrees towards finding one.

  59. Re:uhh that's exactly the point I was making? by kermidge · · Score: 1

    Did you see the part in the submission where phlawed says he'd be willing to pay, that he can't realistically pay enough all by himself, and was asking for suggestions useful to his plaint?

  60. Re:FVWM has the same problem by retchdog · · Score: 1

    your testimony might be more compelling if you described why you need 45 workspaces.

    --
    "They were pure niggers." – Noam Chomsky
  61. He doesn't think of himself as the only user by tlambert · · Score: 1

    Not precisely. He doesn't think of himself as the only user.

    Well, he's (effectively) wrong on that count.

    SourceForge is indicating a total of 35 downloads, and I'd bet at least a couple of them were the result of this Slashdot article.

    1. Re:He doesn't think of himself as the only user by Kidbro · · Score: 1

      I've been using Linux exclusively for more than fifteen years, and I can't remember the last time I downloaded anything from Sourceforge. If five of those 35 are the package maintainers of the biggest distributions, the software could easily have a million users[0] and it wouldn't change that number one bit.

      [0] No, I don't think it has a million users. But your metrics is very flawed either way.

  62. Re: Welcome to Linux by Anonymous Coward · · Score: 1, Informative

    Android user land is NOT open source fully.

    The AOSP is.

    The Google proprietary code in an Android product IS NOT. (gmail, gmaps, sync plugins, ...)

  63. Re:How to attract developers? by kermidge · · Score: 1

    Congrats, Chris, that's fine turn-about.

    "How do we pay to get this done?

    "I know, we'll _charge_ for it!"

    Slick, man.

  64. Re:The closed source story is the same, except wor by MouseTheLuckyDog · · Score: 1

    It's more complex then that. Not only does it have to be profitable, it has to be more profitable then some other new project the guy is doing. And that other project is probably more fun so it has to be moore profitable enought to compensate for that.

  65. Re:FVWM has the same problem by skliarie · · Score: 1

    It is all about instantaneous switch. I manage about a hundred computers and serve as point of contact for all technical questions about them. It is very useful to be able to connect to any of the computer I wish using single keystroke. In these 10+ years I remember placement of every computer by heart and usually don't spend more than a second to switch to the virtual desktop. In rare cases when a terminal to a computer is closed (computer rebooted or network problems), my setup automatically starts new terminal according to the particular workspace setup. Besides connectivity to the computers, there are ongoing projects with many windows open. It saves lots of time to have all task-related windows in single workspace and be able to switch between tasks without having to set up work environment anew.

  66. Re:How to attract developers? by MouseTheLuckyDog · · Score: 2

    Actually i was going to suggest that if he can get the code modular enough and organized enough he ight search for universities that insist that students complete some sort of independent project before getting their degree, then seeing if he can get the students and faculty interested.

  67. Yes it is by dbIII · · Score: 1

    Linux is the kernel. Other stuff is other stuff.

    1. Re:Yes it is by Billly+Gates · · Score: 1

      Linux is the kernel. Other stuff is other stuff.

      Thanks RMS for that brilliant comment.

      I live in the real world where we call Linux Linux. Some of which is not GNU. Infact, I VMWare Workstation, ESXI, perl, Apache, postgresql, is what I see on my Unix VMs. I do not see gnu anywhere at all.

    2. Re:Yes it is by perpenso · · Score: 1

      Linux is the kernel. Other stuff is other stuff.

      The point is that in desktop/server/embedded Linux environment the developers sees the kernel API. Under Android they do not. Android is a Java environment not a *nix environment.

    3. Re:Yes it is by dbIII · · Score: 1

      A one line post that you quote no less and you manage to get the meaning completely reversed? Try reading it again. Note that gnu was not mentioned. Then please apologise for calling me RMS - I despise his two renaming attempts (LiGnuX and the other one that stuck), a thousand "linux - never HURD of it" cracks, the emacs fork and his juvenile hatred of passwords, name badges etc.

    4. Re:Yes it is by dbIII · · Score: 1

      So? With gnome or qt stuff that developers almost never get near the kernel either.

    5. Re:Yes it is by perpenso · · Score: 1

      So? With gnome or qt stuff that developers almost never get near the kernel either.

      I'm not commenting on gnome or qt, I'm commenting on Android. Android is a java based environment, java byte codes running on the Dalvik virtual machine. Its no more a Linux environment than Windows XP running in a virtual machine hosted on a Linux box.

    6. Re:Yes it is by H0p313ss · · Score: 1

      Linux is the kernel. Other stuff is other stuff.

      The point is that in desktop/server/embedded Linux environment the developers sees the kernel API. Under Android they do not. Android is a Java environment not a *nix environment.

      Bollocks, if I write a desktop app in Java (Eclipse for example...) all I see is Java API, but that doesn't mean Eclipse is not running on Linux.

      --
      XML is a known as a key material required to create SMD: Software of Mass Destruction
    7. Re:Yes it is by perpenso · · Score: 1

      Linux is the kernel. Other stuff is other stuff.

      The point is that in desktop/server/embedded Linux environment the developers sees the kernel API. Under Android they do not. Android is a Java environment not a *nix environment.

      Bollocks, if I write a desktop app in Java (Eclipse for example...) all I see is Java API, but that doesn't mean Eclipse is not running on Linux.

      The Java app is not running on Linux, it is running on a Java virtual machine. That is one of the benefits of Java, it isolates you from the host operating system so that your app is portable. What that Java virtual machine is running on is irrelevant to your app. Would you claim that a Windows app is Linux based because MS Windows is running on a virtual machine hosted on a Linux box?

    8. Re:Yes it is by H0p313ss · · Score: 1

      Linux is the kernel. Other stuff is other stuff.

      The point is that in desktop/server/embedded Linux environment the developers sees the kernel API. Under Android they do not. Android is a Java environment not a *nix environment.

      Bollocks, if I write a desktop app in Java (Eclipse for example...) all I see is Java API, but that doesn't mean Eclipse is not running on Linux.

      The Java app is not running on Linux, it is running on a Java virtual machine. That is one of the benefits of Java, it isolates you from the host operating system so that your app is portable. What that Java virtual machine is running on is irrelevant to your app. Would you claim that a Windows app is Linux based because MS Windows is running on a virtual machine hosted on a Linux box?

      I give up, you really are quite mad.

      --
      XML is a known as a key material required to create SMD: Software of Mass Destruction
    9. Re:Yes it is by perpenso · · Score: 1

      Linux is the kernel. Other stuff is other stuff.

      The point is that in desktop/server/embedded Linux environment the developers sees the kernel API. Under Android they do not. Android is a Java environment not a *nix environment.

      Bollocks, if I write a desktop app in Java (Eclipse for example...) all I see is Java API, but that doesn't mean Eclipse is not running on Linux.

      The Java app is not running on Linux, it is running on a Java virtual machine. That is one of the benefits of Java, it isolates you from the host operating system so that your app is portable. What that Java virtual machine is running on is irrelevant to your app. Would you claim that a Windows app is Linux based because MS Windows is running on a virtual machine hosted on a Linux box?

      I give up, you really are quite mad.

      Perhaps you are failing to see that you are arguing that Android "runs on Linux" and I am arguing that Android "is a Java environment". These are two different things. No one is claiming that the Dalvik VM is not being hosted on Linux in Android, my claim is merely that whatever OS is currently hosting the Dalvik VM is irrelevant to the app and its developer. Much as a MS Windows app and its developer don't care if it is running on native hardware or a VM, and in the later case doen't care what OS is hosting the VM.

      In other words. If you are virtualized the host OS is irrelevant.

    10. Re:Yes it is by dbIII · · Score: 1

      I've directly addressed your point about the desktop developers not being able to see the kernel anyway, so please answer honestly with that in mind instead of ignoring it and continuing with an irrelevant falsehood.

    11. Re:Yes it is by perpenso · · Score: 1

      I originally referred to developing desktop/server/embedded apps. C developers working on these apps have access to the kernel headers and APIs. I do not think we are referring to the same thing with respect to desktop development.

      Its a tangent anyway. The focus of my comment was Android, which is sort of its own operating system and environment where the underlying host OS is not available to the Java developers. If you want to discuss the NDK where an Android developer can extend the Android environment with a custom library implemented in C that has access to the kernel, well there is already a thread on that.

    12. Re:Yes it is by H0p313ss · · Score: 1

      feel free to show me a version of Android that does not require Linux though.

      I know right?

      Android is a thin layer on top of Linux that requires kernel driver support for phone hardware. This is one of the most bullshit conversations I've ever had.

      --
      XML is a known as a key material required to create SMD: Software of Mass Destruction
  68. Re:FVWM has the same problem by skliarie · · Score: 1

    Of course I wish to jump from FVWM to something more modern. Have been on constant search for past 4 years. So far I haven't seen anything close that might give me instantaneous switch to any of 45 desktops. The single feature raises my productivity as sysadmin by tenfold.

  69. $40,000 a year by Spugglefink · · Score: 1

    As long as you pay me $40,000 USD a year, I'll continue maintaining IceWM for you in perpetuity. That would be taking a big pay cut to do something boring that I have no interest in doing, but it would be worth it to get to work at home in my underwear.

    I don't know how many times I've been approached by someone who wanted to "pay" me to do work like this. Yeah, $60 isn't going to get you anywhere, Bunky. Sorry bud. You want me to do something that's going to eat all my time, then I'm quitting my day job, and guess who has to make my house payment and crap? Right!

    1. Re:$40,000 a year by iamacat · · Score: 2

      That's extreme, do you anticipate there really be enough work to maintain IceWM every single working day? I think asking for $4000/year and taking on 30 low-volume projects would be a better strategy. Next, expand and hire employees. Some of low use projects got to be commercially important for the one org that is using them.

    2. Re:$40,000 a year by Spugglefink · · Score: 1

      That's extreme, do you anticipate there really be enough work to maintain IceWM every single working day?

      No, I anticipate there being enough work that I can't get it done and work 70 hours at my day job too. Let's say it only takes me four months of highly concentrated effort to get everything up to date and humming along, after which future maintenance will be much easier to manage. All I have to do is take four months off from my day job, which means I give up my seniority, my vacation pay, my sick pay, my experience pay, my bonuses, my health insurance, and I start over from square one four months from now when they rehire me. If they rehire me.

      I'd like to do this badly enough to make some huge personal sacrifices, but one full year paid up front is the least I'll take in order to gamble everything and trade away all the benefits of staying with my nose to the corporate grindstone.

      Indeed, if I could pull together multiple projects, everybody could pay less. Too many projects, and I can't get the work done though. Financing for such things is extremely unpredictable too, and I might get paid this year and never get paid again, so I have to go off and hunt up some other project to work on.

      Hunting work takes time too. All in all, I'll just keep my day job until somebody meets my price. This means I will be keeping my day job in perpetuity, unfortunately for me, and unfortunately for all the FOSS I could have worked on, had I but time. Oh well.

      This is why it's impossible to pay somebody to work on your pet FOSS project, unless you have deep pockets, or a gigantic base of users with shallow pockets and the will to empty them. The best way to get FOSS done is to go do it yourself, and do it for free, out of love. If you can't code, and you can't pay, then you're just shit out of luck. Incidentally, while obviously somewhat over-valued, Ohloh.net lists IceWM as having an estimated commercial development cost of about $2,000,000 USD. $40,000 is jack shit. It's not even one real salary for a developer.

    3. Re:$40,000 a year by gottabeme · · Score: 1

      What's wrong with, "Hey, if you (fix this bug|add this feature), I'll pay you $x. No rush, do it in your spare time, and whenever you get it done you'll get paid"?

      --
      "Those who consume the bulk of goods are those who make them. We must never forget this secret of our prosperity."
    4. Re:$40,000 a year by Spugglefink · · Score: 1

      What's wrong with, "Hey, if you (fix this bug|add this feature), I'll pay you $x. No rush, do it in your spare time, and whenever you get it done you'll get paid"?

      In principle, nothing. In practice, $x is always a figure that's off by at least one order of magnitude relative to the amount of work involved in accomplishing the desired goal.

      It helps if you already know the code, the language, and the toolkit intimately. The more you know ahead of time, the easier it is to accomplish some goal for hire. In practice, the more intimately involved you are with a project, the less $x will be. I've had people offer to buy me a six-pack of beer in exchange for what amounts to 50 hours of work to someone familiar with the code and able to get off and running quickly. Another time, I got offered $50 for a similar amount of work, which is much better, but still laughable. Sure, I know the code, but it still takes time and work to implement and test something. I work on that particular code for free, but if I'm for hire, I'm going to get at least minimum wage. Otherwise, I'm simply not for hire.

    5. Re:$40,000 a year by gottabeme · · Score: 1

      So most non-programmers can't estimate how long the work really takes. Not surprising--the same is true for any field of endeavor.

      Curious, have you ever tried giving a realistic estimate to someone who's asked you to do something like that?

      Also, are you familiar with Joey Hess's work on git-annex, his Kickstarter-funded year of development, and his second year of privately-crowdfunded-not-through-Kickstarter development? Interesting food for thought.

      --
      "Those who consume the bulk of goods are those who make them. We must never forget this secret of our prosperity."
    6. Re:$40,000 a year by Spugglefink · · Score: 1

      Curious, have you ever tried giving a realistic estimate to someone who's asked you to do something like that?

      Yes. I've provided estimates I felt were very fair. I bill based on what a competent person ought to be able to do with something, and don't charge for the extra time I have to spend due to not being competent with some particular language or toolkit or what have you. If the project is in Python, I don't know Python, so I'm not going to charge for the time I have to spend reading up on the language.

      In this case, the $40,000 estimate is realistic for me, simply because that's what I would actually have to have in order to endeavor to complete this task. There is more work there than I can get done while working 80 hours at a day job and having a little bit left over for a life, so if I'm taking on a project of that magnitude, I have no choice but to interrupt my regular employment. There probably isn't enough work in IceWM or whatever we're talking about to justify paying one guy to work on it full time for a year, but my regular gig is an all or nothing proposition where I either eat all the food on my plate, or I get none at all. That's what it would take for me, but obviously anybody actually hiring me for this job under these circumstances is a moron, and to that extent my offer is not especially serious.

    7. Re:$40,000 a year by gottabeme · · Score: 1

      Haha, ok. Well, obviously it's not workable for everyone. But there are probably lots of people (e.g. teenagers, college students, people with part-time jobs, and retirees) who could spend some time on such projects and supplement their income without giving up the rest of their lives.

      --
      "Those who consume the bulk of goods are those who make them. We must never forget this secret of our prosperity."
  70. Re:Welcome to Linux by NotBorg · · Score: 1

    No.

    "MS" is not software like "GNU" is. So it doesn't work that way.

    MS owns Windows. GNU does not own Linux. So it doesn't work that way either.

    The relation that works is that Linux uses GNU therefore it gets GNU in it's name. (If you subscribe to the opinion that you should list accompanying software in its name.)

    --
    I want this account deleted.
  71. Re:I Tried by jones_supa · · Score: 1

    I started a website dedicated to this, but I eventually gave up on it.

    How informative. What kind of things were featured on the site, what made you give up on it, etc?

  72. Re:Welcome to Linux by NotBorg · · Score: 1

    LFS isn't an OS because it's not branded?

    --
    I want this account deleted.
  73. Re:Welcome to Linux by ls671 · · Score: 1

    It doesn't look like it:

    "Although not released until 1992 due to legal complications, development of 386BSD, from which NetBSD, OpenBSD and FreeBSD descended, predated that of Linux. Linus Torvalds has said that if 386BSD had been available at the time, he probably would not have created Linux."

    https://en.wikipedia.org/wiki/Linux#BSD

    --
    Everything I write is lies, read between the lines.
  74. Re:Welcome to Linux by ls671 · · Score: 1

    This picture makes it even clearer:

    https://en.wikipedia.org/wiki/File:Unix_history.svg

    --
    Everything I write is lies, read between the lines.
  75. Re:Welcome to Linux by couchslug · · Score: 1

    In Linux, fragmentation is robust diversity. You aren't compelled to use the fragments, which is why I ignore the whiners.

    Use what works for you and you can get by just fine ignoring the rest.

    Unlike abandoned proprietary "fragments", you can help revive those you like. Or not.

    --
    "This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
  76. Re:I Tried by webnut77 · · Score: 2

    Sorry, but "Anonymous Cowards" are not allowed to use the "I" pronoun. There is no "I" there.

    Unless you're an "Anonymous Coward" from Apple. You know, iAC? :-)

  77. Re:How to attract developers? by gagol · · Score: 1

    Have you seen the amount of closed-source freeware that is not worth half a cent? There is good and bad software in both ecosystem. In open-source you can at least have a say in its evolution path. Want ZFS in Windows? forget it. Want to support humonguous amount of CPUs? Windows will sell you a less-crippled version for a helty price, in open-source world artificial limitations dont exist. You can argue all you want, my actual experience of the open-source software made we want to stay, as opposed to closed eco-systems.

    --
    Tomorrow is another day...
  78. Re:How to attract developers? by bmo · · Score: 1

    > Is Windows your only counter-example?

    No, I could say Lotus Notes or any other kind of crapware. Do I have to list all the crapware out there? After I list, will you ask for more? Probably, because you are here to troll.

    >your message overall

    You keep using arguments that apply to both closed source software and open source software, and then saying it's only open source software that's crap.

    "open source that *doesn't* work is statistically more prevalent"

    And then you pull stuff like that straight out of your ass with no references.

    You're a troll.

    --
    BMO

  79. Re:The closed source story is the same, except wor by mytec · · Score: 1

    If it is open source, then at least you can recompile and/or port to a new OS.

    The OP says, "I can't code in any meaningful way, nor do I aspire to"

    You have the option of paying someone to fix a problem.

    The OP says, "I could easily pay for a supported version of icewm, but I can't personally pay someone enough to keep it alive."

    You have none of those options if the closed-source producer of a package arbitrarily decides to drop it.

    What you've written is true, there are more options for open source projects. However, exercising those options just may not be feasible, as the OP points out in this particular case. If resources for continued development cannot be found, the open source project is effectively just as dead.

  80. Re:I am a VMS user by Billly+Gates · · Score: 2

    I run Windows XP and Windows 7

    Same kernel right?

  81. Android is a Java environment, not a Linux env... by perpenso · · Score: 1

    Most of his argument is that the UI is different. It's like saying that if you don't have a Gnome/KDE/Unity UI, you're not running Linux.

    If you think this is a UI argument you are mistaken. Android is a Java environment not a Linux environment. Nearly all apps are pure byte code executing on a VM, they never see the Linux kernel. Unlike desktop Linux UI's where the apps may interact with the kernel.

  82. Motive? by ZipXap · · Score: 3, Informative

    I'm sorry I can't give any good advise on how to save icemw. What I can do is give you some reasons why an Open Source developer might be interested in developing a project... You can then try to find a marketing angle that appeals to one of these: 1. At the root of all open source development is the desire to do one of two things: (A) Build a tool of profound use to self and/or others. (B) Build one's skills and/or resume. Unfortunately, desktop management systems are an innovation that we've moved beyond. Today the "wild west" is in HTML5 cloud computing, wearable devices (mobile in general), etc. Sometimes an old technology will get lucky and be used as a building-block to something new and upcoming. What makes icewm so useful? How is it useful in the context of things on the "cutting-edge" today? If you can't answer that in a meaningful way then you may need to face the fact that change is a fundamental (and sometimes sad) part of the computer industry.

  83. Lisa Project? by Keith+Henson · · Score: 1

    The best project management tool I ever used was Lisa Project. NASA used it as long as they could and were lost when it could no longer be supported.

    Has anyone revived it?

    --
    End MGM. Get prospective parents of boys to Google: Men do complain
  84. Spherical Chicken? by khelms · · Score: 1

    Isn't that a Fedora release? That's DEFINITELY Linux!

    1. Re:Spherical Chicken? by JWSmythe · · Score: 1
      --
      Serious? Seriousness is well above my pay grade.
  85. Re:How to attract developers? by Bite+The+Pillow · · Score: 1

    and then saying it's only open source software that's crap.

    no, I said "open source that *doesn't* work is statistically more prevalent". Which you quoted. I specifically said It's certainly not "better". I in no way even implied that open source as a rule is crap. Your failure to comprehend makes it difficult for you to participate, so I'll spend some time explaining.

    You want a reference? Search for *anything* on GitHub or Sourceforge, and count the number of projects that actually do anything, vs. the incomplete, half-assed garbage. That is what I'm talking about - statistics and numbers. One stand-out project in a class doesn't erase the remainder of projects which just don't work.

    My perspective is on the Windows platform - I'm sure if you're a Linux user your experience is different. But that is much like a self-selected study sample, and you can't exclude parts of open source. So look for Windows only, and learn something from the experience.

    20 years of following open source tells me that when I have a particular use case, I will find endless half-finished projects that do nothing, one that builds on an outdated or specific platform, and if I'm lucky I'll find abandonware that doesn't completely suck. Meanwhile, I'll find both free and paid closed source software that just works.

    IrfanView is pretty much the go-to image viewer on Windows, with no real open source alternatives. Playing a DVD from the hard drive, Windows Media Player does a better job up-scaling to a 1080 display, so I use it instead of VLC.

    I have written my own software for 35 years for most use cases, because I can't download and run something that works. Why would I spend the time if options were available? Sure the experience is great, but I could write something that doesn't *exist* instead of re-writing something that doesn't *work*.

    Here's a stupid bug in Notepad that is still not fixed in Windows 7, meaning I can't just CTRL-S and continue typing It is not important enough to be fixed, which is completely different from the open-source experience of "can't fix" or "won't fix". And, since I know Windows programming and enjoy reverse engineering, I don't mind making a binary patch to an executable - it's generally simpler than finding the source, setting up a build environment, fixing inevitable errors like include paths, debugging, and patching. Most people couldn't do a binary patch. But, most people couldn't patch open source either, because like OP they don't program.

    Do I use Notepad++ instead? No, because it sucks. I paid for UltraEdit. For hex editing, UltraEdit sometimes does internal conversions on text, meaning I can't debug UTF-8 issues. So I use XVI32, which is free but closed source.

    I use FireFox and Audacity and VLC, and for the rare times I have to use it, Impress is actually better than Powerpoint for presenter view and rehearsing. But on Windows, those are exceptions and I generally can't find open source that beats closed-source freeware. I prefer Media Player, Excel, WinZip, PhotoShop, and countless other paid or free closed source software. Or I write my own, which I don't release because it works for my specific use case and I don't have any desire to fix issues for other people. Which would add to the number of half-assed, unsupported open source projects which is the whole problem.

    I have adopted several open source projects. My patches weren't accepted due to 1) "not invented here" syndrome 2) cannot contact the owner to submit patches 3) no idea - never got a response. 3 projects, with submitted patches available, which are still broken. I'm not forking and becoming a maintainer, so the projects remain broken for non-developers.

    Most FLOSS projects end up as "works for me, if you want to fix your problem yourself, you have the source". Which is great, if you have the knowledge. As OP demonstrates, once the developer decides to quit, if you don't have the knowledge you're stuck. This is my experience, *on Windows*.

  86. Re:How to attract developers? by bmo · · Score: 1

    >You want a reference? Search for *anything* on GitHub or Sourceforge, and count the number of projects that actually do anything, vs. the incomplete, half-assed garbage.

    And I can point at stacks and stacks of crapware out there on Download.com and Tucows.

    You continue to fail to grasp Sturgeon's Law.

    Take the beam out of your eye.

    --
    BMO

  87. Re:Welcome to Linux by petteyg359 · · Score: 1

    Let's extrapolate:

    I haven't manufactured any vehicles, so I don't deserve to have an opinion on how much fuel they should use or how safe they should be.
    I haven't invented any media codecs, so I don't deserve to have an opinion on which formats online distributors should provide.

    And for immature bullshit, let's extrapolate again:

    You're not my mom, so you don't deserve to have any opinions about me.

    See how stupid that was?

  88. Re:Welcome to Linux by mellon · · Score: 1

    It's much more likely that he or she will find more icewm users here. How many mailing lists do you subscribe to that have to do with the various bits of software you run? I'd guess it's not zero, but it's not huge.

  89. Re:Welcome to Linux by binarylarry · · Score: 1

    The google applications aren't really the "userland" in that they're not the basic system. They add value on top of the core userland (email browser, social site, video player, etc).

    Whoever modded the clueless fuck up above insightful should be spanked.

    --
    Mod me down, my New Earth Global Warmingist friends!
  90. Re: Welcome to Linux by binarylarry · · Score: 1

    Oh the Android Open Source Project, hosted by Google that is the base of the official release isn't open source?

    You mean this AOSP (Android Open Source Project): http://source.android.com/

    Can't believe some idiot of a mod actually modded your post up, lol. Only on slashdot.

    --
    Mod me down, my New Earth Global Warmingist friends!
  91. Re:Welcome to Linux by binarylarry · · Score: 1

    So just to make it clear, since I have Steam installed on my Linux desktop, the Linux desktop is no longer considered open source or free because proprietary applications can be installed?

    Even RMS would think you are on crack.

    --
    Mod me down, my New Earth Global Warmingist friends!
  92. That should be "#include <jni.h>" by perpenso · · Score: 1

    Oops, should have been: Note how Google's sample native code begins with "#include "

  93. Re: Welcome to Linux by Arker · · Score: 1

    As I read it he wasnt disputing that the AOSP is hosted by google, he was disputing that it is the entire userland.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  94. Find a Zealot by tmjva · · Score: 1

    Regarding my own site, that runs the Empire game hosted on the MPE/iX operating system. I have simply found a programmer who LIKES the game AND he like the platform it is hosted.

    Granted you can only get to it via simple telnet, but he likes it. The game has been running in various forms since 1973. My Zealot programmer has continued to make improvements to his very day.

    --
    Tracy Johnson
    Old fashioned text games hosted below:
    http://empire.openmpe.com/
    BT
  95. Re:Android is a Java environment, not a Linux env. by exomondo · · Score: 1

    Android is a Java environment not a Linux environment. Nearly all apps are pure byte code executing on a VM, they never see the Linux kernel.

    Android is a Linux distribution just like any other Linux distribution which can include different userland, desktop environment and application toolkits (which can be - but are not limited to - Java), applications can - but do not have to - use these provided toolkits and may or may not directly interact with the kernel.

    Unlike desktop Linux UI's where the apps may interact with the kernel.

    You just said If you think this is a UI argument you are mistaken and then compared applications running on Android to applications running on desktop Linux UI's. Are you quite sure you understand what you're trying to say? Because you are directly contradicting yourself, or perhaps just confusing terms.

  96. Re:Android is a Java environment, not a Linux env. by perpenso · · Score: 1

    Android is a Java environment not a Linux environment. Nearly all apps are pure byte code executing on a VM, they never see the Linux kernel.

    Android is a Linux distribution just like any other Linux distribution which can include different userland, desktop environment and application toolkits (which can be - but are not limited to - Java), applications can - but do not have to - use these provided toolkits and may or may not directly interact with the kernel.

    Java is not merely an application toolkit. For all practical purposes Java is its own operating system and environment. Its virtual machine (VM) can merely be hosted on Linux or various other platforms, Java apps don't know or care what is hosting the VM. Android is built upon Java and therefore shares this structure. Android apps run on the Dalvik VM, whether this VM is hosted by Linux or something else is irrelevant to Android.

    Android also comes with a set of support libraries implemented in C and wrapped with the Java Native Interface (JNI) letting an Android app call these libraries. When you use the NDK to wrap your own C code, which may interact with the kernel, in a JNI compatible library you are creating an application specific extension to Android. Its just a library next to libc, OpenGL, SQlite, etc. This does not somehow turn Android into a Linux distribution.

    Unlike desktop Linux UI's where the apps may interact with the kernel.

    You just said If you think this is a UI argument you are mistaken and then compared applications running on Android to applications running on desktop Linux UI's. Are you quite sure you understand what you're trying to say? Because you are directly contradicting yourself, or perhaps just confusing terms.

    Look at the post that I am responding to, that post made the claim that its just UI differences. I am responding to that claim.

  97. Re: Welcome to Linux by mdielmann · · Score: 1

    I'm not sure how applications have anything to do with the OS being open source. I have a linux install where I run closed source applications. Does this somehow negate everything that Linus (and Stallman) have done?

    --
    Sure I'm paranoid, but am I paranoid enough?
  98. Re:Android is a Java environment, not a Linux env. by exomondo · · Score: 1

    For all practical purposes Java is its own operating system and environment. Its virtual machine (VM) can merely be hosted on Linux or various other platforms, Java apps don't know or care what is hosting the VM.

    Except in the cases where the functionality is not provided by the VM but by native Android support libraries.

    Android is built upon Java

    Whilst much of Android is built on Java you even pointed out that "Android also comes with a set of support libraries implemented in C" and these libraries, while accessible by Dalvik applications through the JNI are not restricted only to Dalvik applications through the JNI and if you were to run Dalvik on another non-Linux host operating system you would be missing these native support libraries that are a part of Android and applications would not run. But it's more than that, Android includes its own window manager, it's own libc (Bionic), it's own Java VM (Dalvik), it's own native libraries and is not limited to just the bit that built on top of Java.

    Android also comes with a set of support libraries implemented in C and wrapped with the Java Native Interface (JNI) letting an Android app call these libraries.

    Yes and these are a part of Android and are not built upon Java even though they can be accessed by Java code through the JNI.

    This does not somehow turn Android into a Linux distribution.

    How exactly is it that you believe an installation of Android differs from say an installation of Ubuntu in terms of being a "linux distribution"? And what distribution of linux is Android?

  99. Re:Android is a Java environment, not a Linux env. by perpenso · · Score: 1

    The support libraries are Android's extension of the Java environment. The android app sees Java classes not the underlying C implementation. For example with respect to OpenGL: GLSurfaceView, android.opengl.GLES20. The environment is still Java language based and the underlying host OS still irrelevant.

  100. Re:Android is a Java environment, not a Linux env. by exomondo · · Score: 1

    The support libraries are Android's extension of the Java environment.

    Yes they are native Android libraries - that do not sit atop Java - that access the functionality of the underlying operating system.

    The android app sees Java classes not the underlying C implementation.

    But the C implementation is executed natively, not within the Java environment, because it does not sit atop Java, it executes at the native level.

    For example with respect to OpenGL: GLSurfaceView, android.opengl.GLES20. The environment is still Java language based and the underlying host OS still irrelevant.

    Wrong, when I call native code from Java that code is not executed in the Java environment even if you think there is some magic that makes it do so.

  101. Re:Android is a Java environment, not a Linux env. by perpenso · · Score: 1

    The support libraries are Android's extension of the Java environment.

    Yes they are native Android libraries - that do not sit atop Java - that access the functionality of the underlying operating system.

    And parts of Java are also implemented in native code. Its irrelevant. The host OS is abstracted away, the java app never sees it.

    The android app sees Java classes not the underlying C implementation.

    But the C implementation is executed natively, not within the Java environment, because it does not sit atop Java, it executes at the native level.

    Again, that is irrelevant. The java app does not know or care. Its a hidden implementation detail.

    Are you thinking that someone is claiming that Java is purely implemented in Java? No one is claiming that. What is being claimed is that the Android development environment is a java based environment where the underlying host OS is abstracted away and irrelevant to the java app. That Android is a java based environment, not a Linux based environment, that Linux is just a host OS that Android apps are unaware of. Most apps on the Google Play store are pure Java. For the minority that use the NDK to extend Android and access the host OS through a custom library, many of these are not even Linux based. They are generally accessing c runtime libraries and possibly posix functionality, rarely something Linux specific. Linux is just a host OS. Its not required by stock Android. Its not even required by most NDK based apps.

    For example with respect to OpenGL: GLSurfaceView, android.opengl.GLES20. The environment is still Java language based and the underlying host OS still irrelevant.

    Wrong, when I call native code from Java that code is not executed in the Java environment even if you think there is some magic that makes it do so.

    No magic. Just you fundamentally misunderstanding what I am saying. As the author that is my fault not yours.

  102. Re:Android is a Java environment, not a Linux env. by exomondo · · Score: 1

    What is being claimed is that the Android development environment is a java based environment where the underlying host OS is abstracted away and irrelevant to the java app.

    Then show me it running on another host.

    That Android is a java based environment, not a Linux based environment, that Linux is just a host OS that Android apps are unaware of.

    Then show me it running on another host, you'll quickly discover how wrong you are.

    Its not required by stock Android. Its not even required by most NDK based apps.

    Again, prove it, stop arguing with your weasel words and actually show me some factual proof.

    No magic. Just you fundamentally misunderstanding what I am saying. As the author that is my fault not yours.

    If i write a C++ application that calls a .Net assembly the application is no longer just a C++ application, it really isn't that hard to understand, just as a Java application that calls out to a native library is no longer just a Java application.

  103. Re:Android is a Java environment, not a Linux env. by perpenso · · Score: 1

    What is being claimed is that the Android development environment is a java based environment where the underlying host OS is abstracted away and irrelevant to the java app.

    Then show me it running on another host.

    You are arguing a tangential point that no one is disagreeing with. Android is hosted on Linux. That does not change the fact that stock Android completely abstracts away the OS from the app's and the developer's perspectives. There are Android devices where you do not even have the option to use the NDK to add a JNI wrapped C library that can access Linux, for example Google TV.

    a Java application that calls out to a native library is no longer just a Java application.

    Untrue. Java itself is partially implemented with native libraries. These libraries, like the Android libraries, are wrapped appropriately and from the apps perspective a Java implemented class is indistinguishable from a C implemented class. Whether a class is implemented in Java or JNI wrapped C is irrelevant, its an implementation detail the app knows nothing about.

    Some libc functions are implemented in assembly language. Calling those from your C or C++ app does not make these apps any less C or C++.

  104. Re:Android is a Java environment, not a Linux env. by exomondo · · Score: 1

    You are arguing a tangential point that no one is disagreeing with. Android is hosted on Linux. That does not change the fact that stock Android completely abstracts away the OS from the app's and the developer's perspectives.

    No I'm saying if the host OS is irrelevant then show me it running on a non-Linux host.

    a Java application that calls out to a native library is no longer just a Java application.

    Untrue.

    Then you show me how to run a Java application that calls out to non-VM native code without having that native code.

    These libraries, like the Android libraries, are wrapped appropriately and from the apps perspective a Java implemented class is indistinguishable from a C implemented class.

    And since Android requires these native libraries that are not implemented in Java it is not platform agnostic and is not built solely on top of Java. It's very simple to understand, go and actually try to run it on another host.

    Whether a class is implemented in Java or JNI wrapped C is irrelevant

    Again, bullshit. If it's Java it will run on top of Java and only the Java VM is required to be implemented, if it is native C then it requires a platform-specific binary that is not portable across operating systems hence the host os is not irrelevant. But I've explained this and it seems the only way for you to understand is for you to try to run it on another host OS so you discover this yourself but you still won't do that.

    You even said of Linux that Its not required by stock Android, so prove it, stop this nonsense and actually prove it.

  105. Re:Is there something similar that can tip a proje by Rinisari · · Score: 1

    There's a site that's apparently growing for bounties on open source stuff, too: http://bountysource.com./

  106. Re:Android is a Java environment, not a Linux env. by perpenso · · Score: 1

    You are fundamentally misunderstanding what I am saying. The Android APIs are portable by design, host agnostic by design. Android ***apps*** do not require Linux, even many NDK based ***apps*** do not require Linux since they just call libc or posix. Android ***app developers*** do not see Linux unless they make a special effort to do so by adding new JNI wrapped C libraries that extend Android.

    You keep discussing things related to hosting and or porting Android itself. I am discussing writing apps that run on Android. These are two different things.

  107. Re:Android is a Java environment, not a Linux env. by exomondo · · Score: 1

    The Android APIs are portable by design, host agnostic by design.

    That doesn't matter, the implementation of the non-Java functionality is platform-specific, you can wrap native code in a portable interface but that doesn't make the code portable, which is why you cannot prove your false assertion because it is tied to Linux.

    Android ***apps*** do not require Linux

    Apps aren't the issue, we're talking about Android and it isn't implemented on any other operating system which is why Android is tied to Linux and thus so are the applications. Until somebody ports Android to another operating system Android - and its applications - will be Linux only.

    Android ***app developers*** do not see Linux unless they make a special effort to do so by adding new JNI wrapped C libraries that extend Android.

    Android is made up of Java and native libraries, the Java libraries are portable, the native ones are not.

    You keep discussing things related to hosting and or porting Android itself. I am discussing writing apps that run on Android. These are two different things.

    You changed your argument because you failed early on in the discussion regarding the portability of Android, now you've changed to talk about apps that run on Android, which even then aren't necessarily platform agnostic so you fail even at this.

    So again, just prove it, prove that it doesn't rely on Linux by either your original argument about the host being irrelevant for Android or your new argument about the host being irrelevant for Android applications. All your weasel words won't help you so just provide some proof.

  108. Re:Android is a Java environment, not a Linux env. by perpenso · · Score: 1

    You keep discussing things related to hosting and or porting Android itself. I am discussing writing apps that run on Android. These are two different things.

    You changed your argument because you failed early on in the discussion regarding the portability of Android, now you've changed to talk about apps that run on Android

    No, the app and app developer perspective has been my argument since my first post in the thread. You simply misunderstood, perhaps that was my fault initially. However at this point you have no excuse.

    Android is made up of Java and native libraries, the Java libraries are portable, the native ones are not.

    No. Android's JNI wrapped C libraries are not Linux specific, they are cross platform: libc, opengl, sqlite, webkit, etc.

    Linux is a convenient host, nothing more.

  109. Re:Android is a Java environment, not a Linux env. by exomondo · · Score: 1

    No, the app and app developer perspective has been my argument since my first post in the thread.

    Wrong, you explicitly said Android is a Java environment which is clearly not the case because it requires platform specific libraries in order to operate, Android includes Java APIs but where those APIs call native code the implementation is only on Linux. So for the god-only-knows-how-many-th time stop your idiocy and weasel words and actually prove it.

    No. Android's JNI wrapped C libraries are not Linux specific, they are cross platform: libc, opengl, sqlite, webkit, etc.

    You only listed the cross-platform ones either because you are ignorant or because you're trying to be deliberately deceptive, go try and build surfaceflinger or bionic on a platform other than Linux...go on...prove it, oh right you can't.

    Linux is a convenient host, nothing more.

    Then prove it, you obviously don't understand Android enough to know that this isn't possible so the only way to convince you is for you to actually try to prove that you are right but you fail time and time again to even try.

  110. Re:Android is a Java environment, not a Linux env. by perpenso · · Score: 1

    No, the app and app developer perspective has been my argument since my first post in the thread.

    Wrong, you explicitly said Android is a Java environment ...

    Wrong. My fist post: "No, its not. End users and nearly all **developers** don't see it. The Linux kernel could probably be swapped out with a BSD kernel and few would notice. Even for those using the NDK and writing some C code they are probably making POSIX calls not calls to anything Linux specific."

    ... which is clearly not the case because it requires platform specific libraries in order to operate

    You use the word, "operate", you are discussing hosting Android. I am not.

    What Linux specific call appears in the Android API? This is what I have been discussing.

  111. Re:Android is a Java environment, not a Linux env. by exomondo · · Score: 1

    The fact that many developers don't see it is irrelevant, if an app relies on some native library and that library does not exist then the app won't run, which is again why you cannot prove your assertion, that's why your assertion is false, these libraries do not exist on operating systems other than Linux.

    Android apps rely on some native libraries, those native libraries are implemented on Linux (and some of it is linux-specific, like Bionic and SurfaceFlinger for example) so it is tied to Linux, you could - in theory - re-write and re-compile the native dependencies for another platform like you could for any application but until that is done it is tied to Linux. So show me it running on another operating system, swap the Linux kernel for the BSD one, actually show some proof instead of your continuing weasel words and idiocy.

    But you know you are wrong, that's why you can't prove it but you just keep posting these pathetic weasel word posts, if it as simple as you say and there is no Linux-specifc code then you can just re-compile with a different kernel and it will work, but it will not work and you know it, frankly your aversion to providing proof is getting pretty pathetic.

    So no more bullshit, no more weasel words, show me proof!

  112. Re:How to attract developers? by DaveV1.0 · · Score: 1

    And, who is going to offer the course, the OP who doesn't know how to code in the first place? Would you pay for course in Window Manager Design from someone who doesn't know how to design or code a window manager?

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  113. Re:How to attract developers? by DaveV1.0 · · Score: 1

    Plausible? The OP isn't a university professor nor a coder. He is neither qualified nor capable of giving a course on window manager design.

    Then, as other has noted, the issue of the output of such a course.

    And, what is described is not window manager design but window manager maintenance. IceWM has already been designed, this is just porting it to a newer version of Linux. How happy would you be if you paid for a course on window manager design thinking you would be able to design window managers at the end only to learn that you will only have one example that is already designed and you are supposed to do some maintenance programming? No discussion of how to actually design a window manager in a window manager course would result in charges of fraud and/or a high dropout rate.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  114. Re:How to attract developers? by DaveV1.0 · · Score: 1

    Except, the OP has already stated he doesn't have the skill to do as you suggest.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
  115. Re:Android is a Java environment, not a Linux env. by perpenso · · Score: 1

    The fact that many developers don't see it [Linux] is irrelevant,

    Not to my point because that was my point all along, Thank you for finally acknowledging that app developers don't see Linux. As I stated in my first post: "End users and nearly all **developers** don't see it [Linux]."

    Android apps rely on some native libraries, those native libraries are implemented on Linux (and some of it is linux-specific, like Bionic and SurfaceFlinger for example) so it is tied to Linux ...

    You are referring to libraries not exposed in the Android API. Bionic is a libc variant available via the NDK, just like the Linux kernel itself. SurfaceFlinger uses OpenGL and the GPU. These are part of the internal Android implementation not the Android API, in other words hosting code.

    ... you could - in theory - re-write and re-compile the native dependencies for another platform ...

    Thank you for finally acknowledging that Android could probably be ported to another platform, as I stated in my first post: "The Linux kernel could probably be swapped out with a BSD kernel and few would notice. Even for those using the NDK and writing some C code they are probably making POSIX calls not calls to anything Linux specific."

    We agree that developers don't see Linux and that Android could probably be ported to another hosting environment without impacting most developers (including those using the NDK for libc and posix). Where we disagree is whether being hosted on Linux makes Android Linux. You think so. I think not, I think it is the API that makes Android Linux or not Linux. As we agree that most apps/developers would not be impacted by porting Android from Linux to BSD I think I have a strong argument.