Slashdot Mirror
VM Enables 'Write-Once, Run Anywhere' Linux Apps
An anonymous reader writes "A startup will soon launch 'a kind of holy software grail,' according to an article at LinuxDevices. The dual-licensed technology is claimed to enable more or less normal Linux applications to run — without requiring recompilation — under Windows, Mac, or Linux, with a look and feel native to each. 'As with Java, Lina users will first install a VM specific to their platform, after which they can run binaries compiled not for their particular OS, but for the VM, which aims to hide OS-specific characteristics from the application. Lina comprises a platform-specific application that virtualizes the host PC's x86 processor... A lightly modified Linux kernel (2.6.19, for now) runs on top of the VM. Under the Linux kernel is a filesystem with standard Linux libraries modified to map resources such as library, filesystem, and system calls to analogous resources on the host platform.' Further details, including an entertaining video or two are at OpenLina.com"
I hope this lives up to its hype (and promise). I may have to finally break down and get an Macintel (much to the chagrin of my PPC army).
Namely, games. I see nothing on their FAQ or Features pages about 3D support. Without that, games-- and several subclasses of applications (CAD programs, simulations, scientific visualisation programs, etc.) will fall flat on their face.
This is a noble effort, though, but what about the 3D?
With spending like this, exactly what are "conservatives" conserving?
Interestingly enough, the word 'groundbreaking' was not used even once in the summary or the article. News doesn't have to be groundbreaking. It could be a very simple old idea used in an ingenious way to be a very useful tool for the masses. Like this, they aren't hiding that they're kind of copying what Java does. But, you know, if it was such an easy engineering task, why haven't you done it? I'm very interested in where this goes.
My work here is dung.
What Linux-only games do you want to run on other platforms ??
This is to port linux apps to other platforms. It sure applies to 3D linux apps as well. Of course, it won't be useful to port Windows 3D FPS games to Linux, but that is not a topic here.
Patents Drive Free Software as Hurricanes Drive Construction Industry
A: For performance reasons, we've written LINA in C and C++.
Why not just write the VM in Java, then it'll be truly portable, right? Right..?
"download: install: run".
That's what we do! It isn't 1979 anymore and having to compile source code isn't something the average user should ever be expected to do....
I have been a user for about 10 years. This ends Feb 2014. The site's been ruined. I'm off. Dice, FU
"Dear user: Insert the CD. Type make all; make install. Press return and go for coffee."
It should be
"Dear user: Insert the CD. Click 'Install'. Click 'OK' and go for coffee."
See the difference from a user's point of view?
"You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
Second, what about dependencies, how does she know to read the README file or anything else to figure out what she needs to build this source. You don't exactly include all the source of all the libraries you coded with, do you? Rarely have I seen a project coded from scratch with no dependencies.
See, the issue here isn't that she can't be instructed like a monkey to hit a button. The problem here is that if something goes wrong, she's out of luck. I mean, as it is, the concept of double clicking what you downloaded to install it was a tough one to drive home. And even now I worry about her willfully installing viruses or malware on the home computer. Because she just doesn't understand the concept so well. When you ask someone to build from the source, you're pushing them quickly into something they don't understand and it's just going to result in a bad experience. The ease of use for software is actually more important to most people than its efficiency or anything else. Why do you think Java is so popular?
->...you have to compile specifically for it, so it doesn't run legacy linux applications.l
http://www.linuxdevices.com/news/NS6279947776.htm
"In Lina's case, the VM is essentially a Linux environment that supports standard C/C++ applications, or even perl and python, if their respective interpreters are installed. CTO Nile Geisinger explained, "You have to compile binaries specifically for Lina, but it's fairly trivial, no different than compiling binaries for SuSE or Red Hat."
-> how is this better than cygwin/mingw???
Even worse:
"Open source developers will be able to use Lina for free, while commercial developers will pay an as-yet undecided licensing fee, the idea goes."
->so, better recompile for free for the three systems.
->wine is the other way round, but at least it doesn't need you to recompile or require you to pay to use it.
->no comments:
"Geisinger hinted that Lina's library set is fairly extensive, after four years of development by a team that has ranged from two to five developers. "There's a lot of code there," he said.
However, a few biggies are missing. GTK+ support is in the works, but not finished yet. There's no support initially for USB peripherals and possibly for other hardware interfaces. And, there's no slick installer to put non-Linux users at ease."
->compare with the resources put e.g. behind java or even cygwin
Well, recompiling an application doesn't port it to a different OS.
The work needed to abstract the fact that you are running on Windows or MacOS instead of Linux is highly repetitive, and therefore a good target for factoring out into some common -- thing.
The most accepted way for this is to develop a framework with WxWidgets. But what if you don't like the framework? What if you need a different framework? What if your language is not supported by the framework? Integrating a VM to the underlying OS is an alternative.
Another thing that I think is useful in this approach is potentially dealing with coupling of unrelated applications via common library dependencies. If one application requires a later version of a library than another is compatible with, you can't run them both easily on the same machine. Anybody who used non-Ubuntu repositories on Ubuntu has run into this.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
And I've had just about enough of you toilet users. If you can't plumb a toilet then you don't deserve to use it. Non plumbers should respect their "does a bear sh*t in the woods" heritage. You'll probably find a tree in the yard. Enjoy.
From their FAQ:
'A: LINA is dual licensed. For non-commercial users, LINA is available under the GNU General Public License, Version 2.
If you wish to use it commercially, please contact us to find out more about the LINA commercial license.'
Erm I'm sorry?! You can't stop someone using a GPL licensed program for commercial use.
Do they mean to say that if you want to sell it or do none-free changes then they will sell
you a non-GPL license?
Insert CD.
Phone relative because the CD does nothing.
Find Install and click it.
Cancel the dialog and click the other install.
Phone relative again and ask them why its going to take 3 hours.
Make coffee.
Return to computer and switch it off (thinking they were switching it on because the screen was blank)
Ring relative and ask why its not worked.
liqbase
So it looks like right now it mostly supports Qt with some gtk stuff coming along. Anyone else find that odd? Today you can compile your Qt apps on Linux, Mac and Windows and get native look and feel. Why would I want to wrap that with a vmmachine? Just yesterday I ran across an app written in Qt for HDR imaging that is written with Qt and is for the mac, linux and windows.
Do you changes clothes while making the "chee-chee-cha-cha-choh" transformation sound?
Imagine a world where everyone wrote software for virtual machines - the problem occurs when people write software for different virtual machines. Eg: if Pidgin was written in Java, Firefox in Mono and GNOME in Python, to run my ordinary desktop I would suffer the overhead of 2VMs and an interpreter.
Besides, its not hard to write cross-platform C++ code.
I don't understand how it deals with dependencies, especially for GUI applications for that "native L&F." I could understand statically compiled binaries, but it obviously must use some shared objects on the OS because in the introduction video, Windows still required Cygwin.
I don't doubt that this will be useful, but there's just too much hype surrounding it right now, and I can't tell the difference between the truth and the embellishments.
// file: mice.h
#include "frickin_lasers.h"
Please :)
Are PC games crucial in every situation? I think it's naive to believe that there can't be a success for a technology just because it means it doesn't apply for demanding 3D games. I'm sure they can live without PC gamers and focus on the multi-billion dollar companies who want their applications to work seamless no matter the operating system.
"People are stupid. Persons are smart" -- Agent K, MiB.
would it really be that much of a step for ./configure && made && make install to be compiled into a nice little gui so that gradma can just double click the CD and have it compile (automatically installing any dependencies), install, and then run?
There is no reason why compiling from source should be any more difficult than installing, it's just that no one's gotten around to making a simple graphical compiler.
Although people might complain about why it takes 48 hours to install OpenOffice.org
being vague is almost as cool as doing that other thing...
This time, for sure!
Sorry, that claim has been bullshit for decades.
-jcr
The only title of honor that a tyrant can grant is "Enemy of the State."
According to the LINA whitepaper, LINA encourages migration to Linux, because commerical OS users will be introduced to countless Linux applications.
I just wonder - if LINA became incredibly popular - would Windows and Mac users really feel compelled to change to Linux? I mean if you could run the vast majority of Linux programs, but still have a few favourite programs that are not supported in Linux (and assuming these don't even run using Wine) then it might be more attractive to keep using LINA and never touch Linux in itself.
Just think of all those people who started using Linux only to have amarok.
If you compile different versions, or if a machine automatically translates for you, that doesn't mean you don't have to test on different platforms. If you expect to have a robust product that runs on linux, windows, and mac, you have to test it on all 3. I think people are confused that this will somehow eliminate that step, so you'd save yourself some time. If it's all one source base, then you'll have tons of stuff like this:
-if running mac, then do this fix, if running windows then do some other fix, if running linux then do some third fix
so either your code gets very large and unweildly, or you have 3 different versions and let them branch a bit. Either has advantages and drawbacks, but neither is what VM promises in theory.
Remember: "in theory, there's no difference between theory and practice, but in practice, there is."
stuff |
install.sh
----------
#!
make && make install
What was your point, again ? Oh yes, there is no "Click 'OK' " step, do you care ?
I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
5% of a market of hundreds of billions of dollars is meaningful, whether you think so or not.
-jcr
The only title of honor that a tyrant can grant is "Enemy of the State."
The new thing about it is that is integrates the application with the host OS. Virtualization usually does not do this.
True enough. But it's just like porn-sites and the defence industry and velcro, if you get my drift: 3D games have a tendency to produce offspring in 3D rotating multiple desktops and those quivering windows when you move them. And _that_, my friend, a user can never do without.
Religion is what happens when nature strikes and groupthink goes wrong.
And come back to:And that's assuming the user knew enough to open a terminal and navigated to the appropriate directory, which you left out. Let's say after they got that error they look at INSTALL and discover your instructions forgot to include 'configure', and now they get:Let's say they go ahead and disable spell-checking, even though it would be a useful feature. They type 'make install' again, like the instructions said, and get:Maybe they're not quite frustrated enough to give up just yet, and they do a google search and discover that you forgot to tell them to run as root. Hurrah! It installed! They type the application name and getWhoops, still root. Maybe they realize this (smart user!), exit, and try running again as themselves. Oh, damn, the application installed in
DLL hell is a Microsoft only problem. There is no reason why you can't have more than one libc apart from a lack of disk space - it works by version numbers to avoid loading the wrong library. Your ten year old binaries will still run in most cases as long as you have the other libraries somewhere on your library path. Some distros have the old libraries neatly packaged as "lib*-compat" so you don't have to find them yourself to get an old binary to run.
They aren't crucial in every situation, however in this one they are. Gamers are much more likely to be the relatively geeky types who have relatively geeky jobs doing relatively geeky things and making relatively geeky decisions for large masses of people. Many of those relatively geeky people with relatively geeky jobs making relatively geeky decisions for large masses of people use Windows because their games work in it, so they spend their time using/learning/tweaking/promoting Windows. However, if said relatively geeky people with relatively geeky jobs making relatively geeky decisions for large masses of people were linux users (which will happen if/when the games start rolling in) then they will spend their time using/learning/tweaking/promoting linux. The problem with LINA is it provides no incentive for development to further areas where linux itself needs to advance, all it does is promote development to areas that are traditionally linux strongpoints while at the same time removing incentive for Windows/Mac/Operating System Whatever to use linux while at the same time essentially placing a penalty on linux because using linux means that for the most part you won't be able to run programs from Windows/Mac/Operating System Whatever in a reliable fashion without some performance penalty.
This is exactly why linux users get a bad wrap... wake up, seriously, if everyone was a tech guru you wouldn't have a job...
I can understand the hack value, but why, for the love of God, would i want to run binary Linux apps on Windows? Didn't they have anything better to waste four years on?
There are some binary Windows apps, which could make life easier (albeit somewhat unethical in FSF terms) for Linux users, such as MS Office and IE6, and AFAIK that's what WINE is for (although i've never had the dire need to actually try it). But vice versa??
All the FOSS Linux apps that are source portable - OpenOffice, Perl, Mozilla, SVN, Audacity etc. - already found their success on the Windows platform. Is someone weird enough to make an application which is binary-only *and* Linux-only?
Or am i missing something?
Oh cool. So Linux/Unix users are going to blindly run make all; make install for any software?
And people look down at Windows users for blindly installing/running anything.
On a related note: just wait till perl/ruby/python malware starts getting popular. No need to compile, even easier than make all; make install.
Let's see how the AV vendors cope with scripts that look innocuous at first sight, but once in a while do websearches and download malicious code (or grep your email for spam containing malicious code) and then run eval on it.
And it should be fairly easy to make these cross platform.
If MS had half a brain they would buy this company immediately! This could work like wine in reverse! MS could say to the suits, "you don't have to migrate away from our wind-turd OS, you can buy this emulator!" The suits are too stupid to realize that they would be missing the most important advantage of Free Software, namely freedom, but the suits would like not having to convert their powerpoint presentations to open office!" This is horrible news!
I'll say it very simply.
Do not force end-users to the command line.
"You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
I'm sorry, but the number of times I've seen the "Write Once, Run Anywhere" claim made for new "paradigms" is fairly scary. There are limitiations to all of these approaches. In this case, running software in complete OS emulation mode denies access to hardware features that have not been successfully ported to the virtual environment, enforces limits of the particular underlying VM hosting operating system in fascinating ways, and absolutely punishes the performance of any disk-accessing operations.
There are uses for virtualized environments, but they're hardly a new approach to code portability.
You can also use wxPython (http://www.wxpython.org), which seems to start a lot faster than LINA (look how many times the LINA app bounces in the dock before it starts), actually *comes with* Mac OS X Tiger, uses native OS controls whenever possible and as of 2.8.3 has a library called SizedControls which automatically applies OS HIG-compliant sizing and borders to your windows and controls on Windows, GTK/GNOME, and Mac (disclaimer: I'm the author of said library). Plus, unlike Qt and LINA, wxPython/wxWidgets is free for commercial development as well as open source.
:-)
So I've been using this 'holy grail' for years, but maybe the VM slowdown and commercial licensing will appeal to some people.
This mentality bothers me. While the command line is intimidating at first, and end-users should never have to learn how to navigate the command line, if I'm giving instructions, I would much rather have someone using a command line.
For example, a few months back, my girlfriend wanted me to put Linux on her computer. She was saving up for a Mac, and her anti-virus had expired on Windows. She needed a web browser, office suite (She used OpenOffice on windows to begin with), and an instant messenger. I had her install Kubuntu, answering a few questions when she had them. Once it was installed, I pulled up a terminal to start installing some programs and codecs with apt. She was deathly afraid of learning the terminal, so I started stepping her through the installation with Adept Installer. The instructions for installing Flash went something like this:
- Click the "K"
- Click add/remove programs
- Type your password
- Check the box next to "unsupported"
- Check the box next to "Proprietary software"
- See where it says "KDE"? Click the down arrow and select "Any Suite"
- Type "flash" in the search box
- It's not in multimedia? Try "Others" I guess.
- Check the box next to "Macromedia Flash Plugin"
- Click "Apply Changes"
- When it's done, click "quit"
Alternatively, I could have told her:
- Click the 'K'
- Hover your mouse over 'System'
- Click 'Terminal Program (Konsole)'
- Can you remember that? Next time I may just say "Open a Terminal"
- Type "sudo aptitude install flashplugin-nonfree"
- Type your password
I explained to her that I didn't expect her to learn how to use the command line on her own, but it's a lot easier for me to tell her a command when I'm giving instructions. She hasn't used the terminal once on her own, and she's enjoyed perusing the programs available through Adept Installer, but she knows if I have to give her an instruction, it will be a lot easier to use the command line.
I realize it's initially intimidating for users to have to open a terminal, and I'd like to see graphical interfaces for everything a normal user would need to do, but I also wish we could get the average user to where they realized the set of instructions is a lot shorter when someone gives you a command than when they have to explain dozens of clicks.
If Java's GPL then why do we need another Java?
Telling people how to fix problems fosters dependency on you. Showing them how to do it, in a manner that doesn't take years of command-line dorkdom to understand, is probably far more helpful.
:)
Though in this particular case, if your girlfriend's about to get a Mac anyway, maybe it doesn't matter so much. I'd be more worried about getting dumped once she realizes she doesn't need you to fix her computer anymore.
Make Slashdot readable! See journal.
The users don't have to compile silly.
With something like Qt, its "write once, compile three times". Distribute binaries for Linux, OS X, Windows. All with a native look and feel, using native compilers and libraries.
Its not clear how this thing works with the GUI. Is it a new toolkit? Is it a hack of the Gtk toolkit? (I thought it was funny how the demo talks about the "native Gtk looknfeel from within what looks like KDE).
WTF is that?
How can they expect to bar commercial *use* of Lina when it's a GPL'd software product--unless their software must be embedded in the end executables?
Meanwhile, the video describing Lina is terrible. It shows (in a ridiculously puny window) two people installing an Apache-backed *WEB APPLICATION* onto two apparently different systems: a Linux machine and a Mac machine. What's the point of that when a PHP-backed application will do just as well and is nearly as simple use? (And what needed Lina? Apache? The web app itself? Both? Beats the hell out of me.)
There's no word on actual performance of Lina binary applications either, and while they claim additional "security," the reality is that complexity does NOT breed security, and Lina is yet another layer which must be maintained, secured, configured, and reconfigured.
Java already provides all or nearly all of this, and targetting development at Lina would be a massive re-tooling. It would also appear that the LINA PDF is internally inconsistent on the matter of whether legacy *binaries* or just legacy *apps* would run under a Lina host. I'll guess that everything must be recompiled specifically for Lina for it to work properly.
Quite frankly, once Java's GPL'd code is ported to the missing OSes it needs to be ported to, there will be no barrier to Java adoption anymore. Plus, commercial devs can still create independently-licensed Java applications without worrying about Lina demanding their cut for commercial development under Lina.
It is the same dilemma (sorta, actually the same dilemma 'in reverse') that badly crippled OS/2. There was a Windows-16 compatability layer in OS/2. Because of said layer, there was little motivation for developers to come out with native OS/2 ports of applications. This made OS/2 really painful to try to run when all the Win32 apps started rolling out and there was no developed 'customer base' for 32-bit OS/2 versions.
Qt if you want a good one.
I'm sorry, have you ever USED a Qt program on anything other than Linux? I've yet to see a single Qt application that doesn't look and behave like ass on Mac OS. (That said, I've never seen a wxWindows one that didn't look and behave like ass on Mac OS either.) My personal favorite is RealBasic, since I've seen RB apps that look and feel native on Mac and Windows, but you'll never get the open source community to use it because it's proprietary.
Comment of the year
Given, I'm running a PPC machine, but from my experience with open source on Linux and Mac OS X... because something always, ALWAYS, goes wrong the first time you do "configure" or "make?" Always.
Either it's missing some libraries (my experience with GD), or it requires SUDO permissions but the instructions didn't say it required SUDO permissions, or the path its writing to is wrong, or it has a Good Ol American compilation error... something always goes wrong.
If you want to write a GUI to cope with every single possible error in the 'configure' and 'make' process, more power to you. But I doubt it's possible for any computer program to handle every case in an automatic fashion.
Comment of the year
That is the norm for Mac OS X applications.
Lemme tell you a small story here.
When MS released Windows 3 was when it started to become known in Brasil. At the time, there was a TV show called "Confissões de Adolecente" (no need to translate, since the name is not relevant). At the time, there was an episode where the main character was bitching an complaining about having to use a mouse and click on stuff. After all, if he wanted something, all he had to do before was to type the command. Now, he had to search for the icon, click on it, than click on something else etc.
So, to translate your comment into something that really means something (and is actually true), what you mean is:
"Do not force end-users to do something different"
Here is Brazil we have a saying for cases like this, which roughly translates as: "If you change the color of the grass, the mule will starve to death"
morcego
Believe it or not, this isn't as difficult as it's made out to be. The biggest barrier would be convincing your mother that she should know, rather than having her simply say "This is too complicated!" at the first hint that she might actually have to learn something.
But seriously, if you give me a half hour or so with your mother, I will be able to get her to understand it, so $500 is a pretty generous offer. And I could use the money now. Want to send me her email address or something?
I don't think it's particularly ingenious, either.
Except Java does it better. I don't even like Java, but I have to admit, it does it better.
Because it's an ugly, ugly hack -- I'd much rather do something useful, like, say, improve one of the real "compile-once, run anywhere" platforms, or improve package management to where such things aren't needed. We're already mostly there anyway -- no matter what the physical architecture, I can generally easily find a GUI package manager for my distro. If I choose the same distro on all platforms, it'll even look similar. And if I'm on something other than Linux, I simply download the binary for my OS. Even if I'm completely clueless, I can simply browse to the program's website, and it can auto-detect my OS and suggest a version to download -- Firefox does this, for example.
Bonus: It now really does run anywhere, not just "any x86 processor". Yes, I realize you can do emulation as well as virtualization, but that's just retarded -- why would I want to lose at least 50% of the speed because your mother is too lazy to download the right version for her platform? With actual binaries, I can get true 64-bit clean versions, on x86_64 or ppc_64, or even ARM binaries... Can you imagine trying to run Linux inside an x86 emulator on a PocketPC? No wonder so many cell phones use Java instead.
Also? Because it's already been done. Depending on the implementation, it's either called "user-mode Linux" (I am not sure if this runs on OSes other than Linux, but I imagine it'd run on OS X) or Qemu.
Ordinarily, I wouldn't bother criticizing them, but I think what they're doing is actually harmful. I would much rather have something written in Java, or cross-platform with QT or wxwindows, than something that's x86 Linux only because someone told them x86 Linux was "compile-once, run anywhere".
Don't thank God, thank a doctor!
Am I "net-blind" or is there no where to download this thing? Google around for "Download Lina" produces hits on some MP3s and some hits on the Lina logo. If there is a download version of this project I can't find it.
On the matter of the product itself:
From the videos on the website it sounds like Lina is a new type of VM for C/C++ code similar to the JVM. If that is the case I can easily contain my excitement and hope these guys have a good marketing department. The technology is not 10x better and as such will have a long road to success.
If you can write to Lina and distribute Lina "binaries" or native binaries (that is "exe" on windows) I don't think you'll see much resistance to Lina as a product. You may not see much fervor over it either though.
If you can recompile a Linux project and distribute either "Lina binaries" or native binaries for a program then I think we have gold here. I'll be very excited and it means that Linux could morph into a kind of super Java style API for all Operating Systems... a sort of meta System V.
If all Lina does is provide a VM to write to, (which is what I suspect), then Lina's success is going to be a matter of marketing. But not traditional big marketing... it will succeed on a combination of smart technologist marketing and viral marketing. If Lina has that it might carve out a niche for itself.
The question is, true believer, can Lina make your heart flutter like Linux, Ruby, Python, or PHP did? If it doesn't learn to make your heart go pitter-patter then I it will have to find a way to cut deals to make you want to learn to dance with Lina. Maybe folks at dLoo can cut a few deals that move a critical mass of developers over to the Lina side of the force.
I don't know if I like Lina or not, I haven't even met her. With a hook like this on Slashdot today would have been the perfect time for me to meet Lina and maybe have dinner. As it stands, I'm a desirable geek and get lots of young new technologies interested in my time and attention. I've got Beryl that I'm hanging out with right now, some python code from Numenta that keeps calling me back and looks mighty nifty, I've got new FX-y tech I'm going to spend some time with too... And, that's just this weekend. I may not notice Lina again. I'm sure she's a nice girl with great personality but... the other tech I can meet and talk to right now and Lina didn't even give me a month and day to get back to her on.
[signature]
Actually, knowing how to spell hinders typing Linux commands...
Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
(Almost) everyone making an application wants to be able to get to the Windows segment of the market, since that's where most of the users are. Writing to Mac or native Linux doesn't help with that, so in practice if its done at all, its often done in addition to writing to Windows, and must be justified by the additional cost.
Writing to LINA, ideally, gets you Mac, Linux, and Windows support all at once. But its not the first platform to claim "write once, run anywhere", so how well it fulfills that promise—and what the performance is like—is going to be key.
But, fundamentally, if it lets you target a wider market without increasing costs too much, it seems to make business sense, so if it does that well, I expect plenty of people will write to it.
Actually, most Windows apps take advantage of autoplay, which means it really is "put the CD in, push the big flashing button that pops up, click next a whole lot because none of that text could be important, wait".
To my knowledge, Linux doesn't have autoplay. While I agree that autoplay is awful, it does make things easier for endusers.
I don't know if OSX has autoplay or not, but in any case with OSX it tends to be "put disc in, double-click the disc icon that just showed up". I haven't seen any equivalent for Linux - you usually have to find the install program or similar. God help you if you have a package manager - then you have to search for what you want to install!
People's brains freeze up when confronted with a computer. They'd much rather just put a shiny disc in and let the magic computer do its work. Seriously, you could sell "Linux application install discs" which are just a pack of CDs where each one has "aptitude install gimp", maybe a hudnred bytes each, and people would buy them.
Breaking Into the Industry - A development log about starting a game studio.
On windows this program requires Cygwin. So yes you can run all these apps natively, as long as you first install a extraction layer. And hey I wonder if I can get Cygwin working under wine so then I can go through two extraction layers. Wait, maybe I can then install colinux in wine that pumps x output through cygwin, then I can install wine, and then get cygwin running, then I can install cygwin...
Just write a fucking app in good c/c++ and staticly link libraries not on windows. Compile it and wohoo, a binary for windows. The only thing the least bit interesting is the gtk/qt to native api layer. That should be the library they provide developers with for ease of compiling to different OS's.
LINY is not you!
You are reading a sig. Cancel or allow?
Considering I've never ever installed a program from a cd under Linux dont you think autoplay would be useless? :P
I think package management is far superior to cds. For one you cant lose your package management and spend half a day looking for it.
Most people, I suspect, want plastic discs to install software off. It's far easier conceptually to deal with. Linux really doesn't handle that case well.
Personally, I agree - I vastly prefer package management or online downloading. I suspect there will be some user re-training needed to get most people to understand that, however.
Breaking Into the Industry - A development log about starting a game studio.
I would much rather have someone using a command line
And therein lies the problem. You would rather have them using a command line. They don't want to. When you have a GUI, you always have prompts and a safety net. You can say, "Click on the button that says 'Change Setting.'" They have an automatic double check because there is something that matches, exactly, what they're being told to do. They have limited choices because they're working from a menu or from components and when one matches what they're told to do, they have some kind of confirmation they're pressing the right button. When you say, "Now type this," then you can hit any number of snags and they know it. You can tell them what to do and they can use a single quote instead of a double one or hear the word wrong or mistype it and, from their point of view, they don't know what's going to happen if they make a mistake.
You are much wiser than most developers I've seen post here who want to blame the uses for not knowing everything they know and you've got a good point. You and I can often move much more quickly with a console, but for users, the mere thought of having to type commands is frightening. They're looking at a blank screen with no feedback until they hit and then it could be too late.
You've realized, though, that it isn't about what you or I want, but what the user can handle or take care of on their own. That's the problem: It's our job to give them what they can handle. That is rarely a console. With my clients, before I got my software up to the point I wanted it, I had them install RealVNC on their computer and used a tunneling program I wrote in Java so it would go through their firewalls, then had them add me, and I configured RealVNC so it would only run when they wanted to run it and so it had a strong password. (And before anyone starts screaming, I'm simplifying and leaving out discussions with their bosses and IT departments about safety.) When they had problems, I just had them run RealVNC and add me, then I could fix, in less than 5 minutes, what could take 45 minutes or more if I were telling them what to do. When I finally got my own program to where I wanted it to be, that wasn't an issue anymore since I had enough failsafes they didn't need that kind of help anymore.
Ah, you've used Windows, I see. Installing things is much easier on pretty much every other platform (including macosx, most of the linux-based platforms, and most of the BSDs).
What are you talking about? One of the big problems in the Windows world right now is that applications are so easy to install, that the user often has to run special software just to keep applications them from installing all by themselves!
Well, I'm not so sure I buy that whole round plastic thing :) But I think your intentions are good.
I see plenty of people go online and click that little icon that says 'you must install this and ten other spyware executables, for which you cannot sue or, and you'll get spam, click ok to to play OUR version of solitaire which has prettier seashells on the cards.' Or you know, snood, which expires, and forces my mom and sister (not computer types) to learn how to uninstall it, and download a new copy every time it does. I think what people really want is a more clever use of smiley faces, now if you labeled your Plastic Discs with pretty colored smiley faces, with even more cleverly painted tongues hanging out of their squiggly mouths, you'd be able to have them run it on whatever operating system you like. They'd just learn it for the smileys. (Used to work for second graders too, way back when they'd get a scratch n sniff smiley sticker for passing what we used to call Spelling Tests. That's of course before they were illegal in the US - no I'm not even kidding about that.)
Speak for yourself.
, (to make things easier and for 'sharing' code), were obscure pointers to areas of memory.
that required a rocket scientist to figure out what the hell was going on. Wow! We had 'functions' - we could
share code a lot easier!
that required a rocket scientist to figure out what the hell was going on. Wow! We had 'objects' that virtualized
concepts. But why do we suddenly have 'fat' programs.
out what the hell was going on. We had objects that virtualized everything. 'fat' programs? - forget fat these
were obese.
figure out what the hell was going on. Forget trying to virtualize program space - heck let's virtualize the whole
damn O/S! What's a fat program without a fat O/S?!
So, what's next after O/S virtualization? We've tried in the past to objectify and virtualize program space
and to a large extent doesn't work as we either keep changing userland requirements or our methodologies force
us to change.
Don't get me wrong - love virtualization for all the right reasons. But, all we have at the end of the day
is faster and faster machines that sit there chewing up greenhouse gases, (Bring back the old days of the
TRS80!).
-- main(s){printf(s="main(s){printf(s=%c%s%c,34,s,34
So, let me start with my bias: I work for a tiny company that makes a programming language with interpreted environment (we're working on the compiler now) that runs on Windows, MacOS X, Linux, and Solaris, and I think AIX. (Those are the ones we've actually tried it on, it may run on others.) Our language and development environment facilitates rapid development of web applications. (And anything else you like, but web applications is applicable to this discussion.) Using our language you can write fully AJAX enabled applications (which work on IE, Netscape, Mozilla, Firefox, and Safari, and maybe others) in a Model View Controller pattern without knowing anything about Javascript, with no system dependencies, and in my opinion you can do it much faster with our tools (and be able to run it on all those OS's and browsers) than using traditional languages and APIs (and be able to run it on one OS and/or browser). Once you've written the app, our software will even serve it out (one line of code instantiates and integrates a web server!) so it can be used from various browsers running on various platforms.
Now, knowing as I do that this is all possible - which I'm sure of because I use it every day - it's my opinion that writing software specifically to any API which is tied down to any particular OS or browser is a waste of time. Why spend your time writing software for, say, Linux, knowing that it will just have to be rewritten (or at least altered) to run on Windows and Macos and Solaris etc, when you could write it once in some cross-platform language and be able to run it everywhere and use it everywhere, like Java promised we'd be able to do once upon a time? That promise of cross-platform, cross-browser, write-once run-everywhere computing is not an impossible fantasy, it's something that's here today if you look hard enough, and those of us who develop programming languages and tools for a living should be focusing on it in our work.
So, my point is that "thinking linux first" is indeed a bad thing: if a business person has to decide on what computing platform to use for their software solution and you make them think about linux, they'll just get annoyed because they don't want to have to think about what technology to use and why, they just want to see it happen, and use whatever they're familiar with. They want to think about their business first, and technology as little as they can get away with. The way to get businesses to adopt linux is not to make them think about it, it's to make it so easy they don't have to, and cheap while you're at it. Businesses care about two things, three if they're smart:
1) How to make money
2) How to spend less money
3) How they're going to make even more money in the future
If you can show them that linux will make them money that other OS's can't, they'll go for it. But, there's little that Linux can do that some other OS can't, so that's a poor argument.
You can argue that linux will save money because it's free, and that's good, because businesses like not to spend money, but it's also worrying because businesses like to have someone standing behind the product. Sure, there are companies that provide support and we as geeks all know that, but that's beside the point. Where you can really win is to say that using some particular system will enable the business to be doing the kind of business they want much earlier/faster than other technologies. For example, I watched my boss show a client how they could do something with our programming language in about five lines of code that a competing vendor had told them would take a year and cost over a billion dollars, so our client became *very* interested in using my employer's language a lot more, because it would save them a lot of time and money. So, if you want Linux to get wider acceptance, figure out how using it makes common business tasks go faster and easier than using competing products, and advertise that. So far, as a computing professional my experience with linux is that i
On Windows, they get told to change some text in the registry and type things they don't understand into cmd.exe. Where's the difference?