Windows and Linux User Interfaces
Anonymous Coward writes "Greg Raiz, Boston based interface designer and former Microsftie takes a look at Linux and outlines key shortcomings and strengths of an OS that could take on a giant."
← Back to Stories (view on slashdot.org)
Perhaps there's some truth to this. If Linux is to gain more widespread adoption, then maybe that would help. If so, then I personally hope Linux remains a niche OS. What he doesn't seem to grasp is that some of us would rather remain true to the Unix ideals and philosophy than to chase mass market popularity. I want to just be able to extract an archive and run a binary contained within. I don't want to have to inform the OS that I've done so, and have to "install" the software. I want to be able to compile an app and run it from my home directory. Why should I have to register it with the OS in order to do so?
"The invisible and the non-existent look very much alike." -- Delos B. McKown
Linux should stop copying Microsoft feature for feature and embrace the differences and features that advanced users love.
I would disagree. What about enlightenment, fluxbox, openbox?
This article doesn't really make much sense overall.
"The core mantra should be: "Simple and easy in everything we do, but give me a command line and I can move the world.""
I'm guessing he hasnt spent a lot of time in OS X then. Especially since he says in the article that Apple took the simplistic (ie not technical) approach.
Make upgrading from windows as easy as possible, Standardize on your widgets, and Make Installing Software Easy and secure.
I tend to agree with most of the articles comments except for 1 random jab at Apple for choosing the lower ground of loosing functionality for better interface, where I believe that Apples interface is middle ground like windows but it is just better designed so it is easer. But I digress.
For Installing why can't Most Linux distributions support Loopback files, So they can install Linux on top of a Windows partition and if they don't like linux just delete the ISO file. Also a Non-destructive partition system like Partition-Magic.
More effort should be put into WINE, and MONO projects. It should be easy to run Windows programs. Just like the migration from Apple OS 9 to OS 10 or from DOS to Windows or Windows 3.1 to 95. People prefer "Optimized" to their OS applications, and will ask for them, but if they can't get it they want to run the old ones. These projects will not make developers think "Well Linux emulates it so we don't need to port it." they will think wow we have xx% of our customers using our product in linux, Perhaps we should make a Linux Version before our competitor does so we don't loose them.
Standardizing on the User Interface is extremely important. I can't even count the times I have to go to a newbe who is using KDE or GNOME and opens an Application build with the other tool kit or worse a different one like X11 and explain to them that they may have some trouble Copying and Pasting, and oh this is a x application you need to do it this way instead. And your files are by default saved here except for there. It is confusing and they do not comprehend why things are so diverse.
Installing, I really don't see why Linux can't take a lesson from Apple and improve on it. To install an application drag the folder to where you want to run the application. Have all its files that it needs to run self contained inside itself and uninstalling it is just deleting the directory. And try as much as possible to make the application statically built With Drive space below $1 per gigabyte the extra space lest be a little wasteful to make installation easy. Only spread the files across the OS when you Really-Really Need to.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Guys, we need to have an attractive desktop by default in order to make the user experience at least more appealing. In one installation of Ubuntu, I had to tweak the X.org conf file in order to have it display these fonts correctly! And believe me...it took more than 4 hours to get right! Who would have that time in the "real" world?
This probably won't be a popular comment, but I think Mac OS will eventually be bigger on the desktop than Linux.
1) Easier Support - your computer breaks, you know who to go to
2) Less of a learning curve.
3) Less confusing in terms of options (there are a lot of types and kinds of Linux, or so it seems).
4) Media acceptance. Macs are more well known than Linux, which isn't Linux's fault, it's just the fact that OS X has Apple behind it.
5) Application Support - Things are ported to Mac quicker than to Linux usually. Apple also stands to get more software compatibility when they go to Intel computers.
::Braces for "-1 Flamebait"::
___ In the words of Gen. Douglas McArthur: "I'll be right back."
As a corollary to the first rule, users don't like installing applications. Part of the fragmentation problem for Linux is that the fragmentation forces a problem for software installation. Users are forced to untar, un-gzip, copy, configure and sometimes compile in order to properly install software. To gain momentum Linux needs a central installation architecture that all applications must use to properly install and run. The OS should ensure that applications are installed before they can be executed.
Wow, I couldn't have described apt or emerge any better. Isn't it common that those who review Linux OS's vs. Windows almost always head to the biggest vendor (Redhat) which is exactly the wrong idea: directly motivated by Microsoft's position on the closed source market? Biggest is best is necessarily a universal philosophy. Also, there are rpm managers in Redhat that do the same thing as apt, I think you can even use apt on Redhat without too much trouble.
Sure one might say, "How would the avg. Windows user know to apt-get install ?"
I would answer, "They could figure that out long before they understood how to dl and compile source code, and would certainly require less user knowledge and decisions than going apt-get install , which rarely asks for user input"
I see a ton of skilled Windows IT folk that are scared away from Linux because they try to compile everything. Apparently they haven't heard, and/or common linux knowledge doesn't include important tips that would make Avg Joe Windows user's first Linux experience much more enjoyable.
Welcome to the Chicken and Egg problem. Hardware manufacturers and Software producers are not going to support Linux until it's popular. Yet Linux won't become popular until the Hardware and Software vendors support it. As a result, you need to make the product more attractive to users in another way.
Apple has the right idea. By pushing the technology far ahead of the competition, they convince users to accept some of the shortcomings in exchange for a large number of features unavailable on other platforms. This increases the Mac user base, forcing the Hardware and Software vendors to support them.
I know in my own personal case, I could run regularly Linux right now if I wanted to. The problem is that my kids have a large number of educational titles and other kids' software (no, they don't operate correctly under WINE) that they must reboot to use. If I leave the system in Linux, I hear no end of complaining from my wife who has to reboot the next day.
Now I (and a few others) have suggested methods by which the Linux Desktop could pull ahead of Windows, and possibly even the Mac. My own suggestions would be distro specific and would not harm any existing distros. Yet the community resists such changes strongly, stating that "Linux is perfect the way it is". Many automatically assume things I didn't say, based on their past experience.
So in the meantime, I and my small team will attempt to implement these ideas whenever we have sufficient time. Unfortunately, it is very difficult to reconcile our schedules, and without more volunteers I fear that the project will not get done in time to make a difference. Which is really too bad, as I feel that it could make Linux a significant competitior in the Desktop market.
Javascript + Nintendo DSi = DSiCade
I think he makes a good point that the clean solution is always better than trying to support older decisions that turned out to be less than ideal. But the problem is, users aren't interested in details. Details don't matter. They only want something to work, and keep working.
Most modern interface elements are implemented by most toolkits. I think a solution would be to take the concept of the X server, which implements low level functionality available via byte stream communications, and implement much higher level concepts using the same idea. Rather than linking in libraries (and tying your graphical concepts to one language - C for GTK, C++ + custom weirdness for QT) have an X server analog that can speak in terms of Menus, Canvas w/ Scrollbar, Button, Text Input, Text Output, etc. Instead of Xlib (or clx in Lisp) you would have a much, much higher level communication protocal. Language bindings for C, C++, what have you would build on the primatives and higher level widigets provided by this X-server plus, and themes and other details would no longer be different because of what language binding you happened to be using. Translating code between languages would also be much easier, since concept names in different languages could all build off of the standard in the server.
Look sometime at the problems people have writing Python bindings for QT. I think the idea of a high level graphical object server with server side theme configuration would take us a long way towards a common desktop look and feel.
"I object to doing things that computers can do." -- Olin Shivers, lispers.org
He makes it sound so simple, doesn't he?
Writing a complete VB clone isn;t as simple as writing an IDE. VB 6 worked because of the underlying Windows infrastructure — ADO, Access, COM, and all those other acronyms that could be glued together with VB to make an application. VB provides a great environment for hacking together in-house and vertical market applications. It's good for rapid prototyping, too.
The Unix world has some very strong biases that make cloning VB difficult, not the least of which is a general prejudice that all VB code sucks. I've worked in shops with VB programmers (I'm a C++ guy), and saw some darned ugly code; the anti-VB prejudice has some basis in fact. Be that as it may, VB is a powerful force that locks many developers into Windows. If any of this code is to move to Linux, we would need to replicate the entire foundation of acronyms used in VB programs — a daunting task that most Unix-oriented folk will find unpalatable.
In part, Mono was trying to accomplish Windows-Linux interoperability, albeit using .Net as the foundation. Mono, however, does not address the vast quantity of VB 6 applications. And Mono's viability is still open for debate, given Microsoft's proprietary attitudes.
A while back, I was tried to sell the idea of a FOSS Access and VB to several major Linux "players", without success. Perhaps my pitch just wasn't that good, or maybe, just maybe, Unix people really are letting their prejudices get in the way of a Really Good Idea.
All about me
Time for the FOSS community to start working on OpenOSX.
"The MAJORITY of all new servers today are slated to run Linux.
This is not going to change, I repeat, it will NOT change."
Right, because nothing better than Linux at running servers will ever come along. By the way, what OS always has the best uptimes? Linux right...
"How can you call Linux a "niche" OS?"
Because all of the estimates I have found place Linux desktop usage somwhere between 3 and 6%. If you need to ask now, it's because you don't understand what "niche" means.
"First off, Linux, or rather GNU/Linux, is an operating system KERNEL."
Man, you lost that battle years ago, give it up already.
"But more importantly, it is hugely successful and I am personally offended"
And NOW, FINALLY we get to the crux of the issue. YOU are personally invested, so rather than accept honest criticism, you get "offended" because someone spoke unfavorably about your hobby, and you feel that criticizing Linux is equivalent to criticizing you.
I'm feeling snarky, so I'm tempted to say that's patheitc. But I won't.
What I will say is that of that's the best argument you have, then Linux had better have someone else arguing for it. Luckily it does.
I do admit that VB may not be the best thing around, but it is fairly easy to learn, and it can get some simple jobs done. And I would venture that VB meets the minimum set of requirements of a programming language as defined by Turing himself.
So, VB is not for you. Thank you for deciding what is best for the whole world. For your next trick, please tell us what the solution is for world hunger or poverty.
Next, I suppose that you will be saying that VI is the only real editor, and anybody who uses anything else is dumb.
I apologive for appearing trollish, but this sort of attitude is quite annoying.
"-1 Troll" is the apparently the same as "-1 I disagree with you."
First off, Linux, or rather GNU/Linux, is an operating system KERNEL.
That's not even what the "GNU/Linux" people think. If you're going to advocate something like that, you should at least get your facts straight.
Linux is the operating system KERNEL.
GNU/Linux is the kernel plus the collection of (almost entirely GNU) applications and libraries that make up the OPERATING SYSTEM.
But, as noted above, even though Linux technically only refers to the kernel, the colloquial usage of the word has long been understood to refer to either the kernel or the operating system, depending on context.
Some of his comments are good, some are abysmal:
There is an opportunity for the open source community to create a VB compatible IDE that could compile applications for both to Windows and Linux.
Please, by all the gods you believe in, NO!. The very last thing we need is all this crappy VB stuff on Linux. VB is - by rights - famous for the shoddy software created with it. And don't tell me you can write good software with VB, the fact is that the vast majority of VB software are abominations that should've never left the author's imagination.
Entice users with well thought out end to end solutions
That entire chapter would've been much shorter if he had simply written: "Look to OSX for ideas on how to do it right, and to Windos for ideas on what to avoid at all costs".
Users are forced to untar, un-gzip, copy, configure and sometimes compile in order to properly install software.
Has the dude used any Linux distribution during the past 5 years or so? Now I do compile stuff occasionally, but then I want to be on the bleeding edge and some of that stuff was written by me. Almost all actual applications I use rely much more on apt-get and dselect than on tar and gzip.
Linux should stop copying Microsoft feature for feature and embrace the differences and features that advanced users love.
YES. Besides some of the stupid comments, he's got the basics right. Hey, wait. Some of us have been saying this for years. The problem is that too many decision makers in both KDE and Gnome believe copying windos is the road to heaven.
Assorted stuff I do sometimes: Lemuria.org