The GNOME Roadmap
glockenspieler writes "Recently on the the Gnome Foundation mailing list, Dave Camp posted a draft Gnome Roadmap for versions 2.8 and Beyond. Issues up for discussion are Mozilla/Epiphany, incorportation of peer to peer filesharing, blogging, addition of more media widgets, and many others. Time for Gnome users to weigh in on what improvements that you would like to see. If that's not enough, then there's always the the C# versus Java versus ? discussion."
Personally I use KDE, but I used to use gnome. Not as pretty, but its faster and lighter than KDE. Take out C/C++ (forget which they right it in), and use Java or C#, they just made it bulkier and much slower. That would be their main opinion IMO. Gnome doesn't look bad, but most people I've talked to think KDE looks better. Take away Gnome's advantage in this situation, and they don't have much going for them.
Help Fight SPAM today!
Can't people just install their own peer-to-peer and blogging apps?
Why not make an installation system that works as simply as clicking setuppackage.msi is in Windows and let the other problems solve themselves?
Why not just make a working desktop first?
Sheesh. Yeah, this year will be the year of linux-on-the-desktop now that we have integrated blogging. That was sure the barrier for entry to me.
I don't need no instructions to know how to rock!!!!
Do we really want blogging software, p2p software, etc included with gnome? Is gnome so perfect in other respects to justify adding features that 0.01% of people are going to use? I think a better use of resources would be improving and debugging the current Gnome programs before adding this -- someone else can always program p2p apps and blogging software.
After reading this roadmap, I'm left with nothing but warm feelings of loveliness.
:) Looks like all those Sun corporate installations helped a little bit! Also, the close work the Gnome community is putting in alongside freedesktop.org is a *very* good thing. Integrating the desktop with the hardware is something Windows has been able to (alledgedly) do since '95, and it's about time we had that too! New users certainly need to be able to plug their digicam in and have it "just work", and if this can all be incorporated with Nautilus and the CD burner module, transferring pictures could be as easy as insert camera, insert blank CD and click Go. Gnome could fast be approaching Apple levels of usability!
First off, working with Mozilla Firebird is a stroke of genius. There are a heck of a lot of man hours being put in on that project, we should utilise them rather than recovering ground already trod upon by the lizard.
Secondly, integrating both Ximian, Gnome-DB, calendering and address book tightly into Gnome could be a great leap towards a working Dashboard project. This alone looks like propelling Gnome into pole position - it's a genuinely innovative feature, not yet seen on any other desktop, and only hinted at by Microsoft so far. Beating Microsoft to the punch would certainly be a coup.
The other really encouraging thing is the following paragraph:
--
One area in which GNOME has lagged behind other desktop operating
systems like Windows and Mac OS X is tight integration with hardware.
GNOME is working with the freedesktop.org community to make
plug-and-play hardware management just work.
--
For me this highlights that Gnome has moved well into position as the premier Linux desktop, and rather than concentrating on what KDE are doing, they are focusing on bigger fish
I want my 2.8!
Sunday you're Thinking Different, Monday you're a huge tool, paying too much and waiting to think like everyone else.
But it doesn't count if you do it anonymously. =)
I think blogging integration would be nice to have. Some sort of dockable panel that you could type up your blog in, put in a picture for upload, etc.
"Quis custodiet ipsos custodes?"
Mozilla integration would be great. Maybe this could mean they're thinking of getting rid of Nautilus. I won't hold my breath, but it would be nice.
This signature has Super Cow Powers
not implementing any of those? actually, how about taking it a step further and getting rid of a lot of stuff in there already?
... if anyone knows why Unix should be simple, it's him
i don't understand why windowmanagers need to do everything under the sun. the footprint of freebsd's gnome port is damn near 1GB. perhaps if the gnome and kde camps could focus on simplicity instead of features, things would be farther ahead than they are now. maybe we could all agree on a unified copy/paste for once for pete's sake.
Unix is very simple, but it takes a genius to understand the simplicity. Dennis Ritchie said that
vodka, straight up, thank you!
C# versus Java versus ?
Real men use Assembly. They should code it in assembly.
Evolution or ID?
I think they should really move on to use ?. It's the most superior language of the three, after all it's based on the earlier Jeopardy language where all statements are expressed as questions.
For example the familiar Hello, World! application is written in ? as follows:
what is the procedure the OS calls first?
{
what is the output of the most common small example program?
}
John.
Anything but Java, please, I can't afford the hardware it'll require to run it!
Mod me troll, if you must, I can't help it.
Check out some nice screenshots of this book collection manager written using the Ruby/GTK bindings.
The Army reading list
GTK is easily the most painful widget set, both graphically and programmatically, that I have ever used.
Never used MFC then, have you?
Basically gnome is great, but it lacks attention to detail IMO. I think future versions should focus more on detailed quality and not on expanding featureset.
1. The Menus should be much more customizable; treated like folders that you can click and drag into (I hate to say this, but "Like Windows").
2. Better Video control properties; take advantage of XFree's extended features and have options like TV switching and such.
3. Better preferences; the control panels are quite lacking.
4. Other aesthetic enhancements that will make gnome pretty enough to compete with other window environments (like win XP's or OSX's). Smooth scrolling, the zoom-on-hover icons in OSX are sweet, and _drop shadows on windows_ would be real nice.
5. Some kind of Linux-version-of-Active-Desktop would be real nice, so I could have an IRC session running as part of my wallpaper,anchor the weather channel radar map to the background, etcetera.
Cool, that could mean:
1. RSS feed client integrated into Gnome (maybe even displaying RSS feeds on the background?)
2. Blog API client integrated in Gnome. BloGTK seems to be a good candidate.
Good to see D-BUS and HAL integration on the roadmap for 2.8. Just set them up on 2.6 last night, and they're quite fancy.
ATM, all they do (in conjunction with gnome-volume-manager) is automount/unmount/run removable media. Pretty much what you got with autorun for years on Windows, but more extensible in that you can tell the daemon what program to run, etc. Its also setup to detect/play dvds, and import photos from a digital camera automagically. Long overdue perhaps, but still very nice to have.
I suspect the best improvements are coming in the future once this is all integrated. Basically it gives the system a queryable, extensible device manager. In the future, I would expect all software that does hardware interaction will interface with this layer, for detection, hotplug, identification, and so forth. Long story short, its an absolutely critical piece of Linux on the desktop.
I think GNOME 1.4 is faster than the newer version. Right now I still use 2.4 and shut nautilus desktop off because hog the memory.
So I want new version as fast as GNOME 1.4
-- There is four mistake in this sentences.
I'd like to see Ed Dumbill's Gnome Bluetooth subsystem get picked up by Gnome. I'd also like some UI to turn on and off spatial browsing. It's got real potential, but I'd like to be able to switch it off without gconf-editor.
Also, now that x.org's CVS has Damage and Composite on the way to working, someone should sit down and cook up some new eye candy using this stuff.
Also, using Python paves the way for universally integrated scripting, somewhat like the VB script possibilities in MS-Windows (and, despite waht MicroSoft did, that is a good thing).
Secondly, integrating both Ximian, Gnome-DB, calendering and address book tightly into Gnome could be a great leap towards a working Dashboard project.
Didn't Microsoft get flamed pretty badly for integrating a browser into their Desktop/OS? Just amusing to see how easily this is overlooked with the list of new Gnome "features".
Hint to Gnome developers: KISS. Manage my desktop, don't manage my applications.
For the love of all the is good and right let X die! You want a road map for devlopment, copy each and everything the is in OS X and then go from there. Of course, I am one the weird ones running XFCE with Rox filer.
[RIAA] says its concern is artists. That's true, in just the sense that a cattle rancher is concerned about its cattle.
Why look for such a big jump? C++ has a proven track record and none of the legal ramifications that Java or C# might. Plus it would interface so easily with C files.
Nullum magnum ingenium sine mixtura dementia (There is no great genius without a mixture of madness) - Aristotle
To install package 'foo' in windows:
Compared with
Which one is simpler?
Sincerely,
Seth Finklestein
UI Guru
Maybe if Gnome came with a defragger, a backup utility, a DRM media player, and a Windows Update tool it would be improved.
C'mon... none of these address simple usability issues like those noted by Nick Petrely. I don't agree with him on many things, but let's get usability going before we start throwing applets in.
Try fixing the sound recorder app. in core 2. Segfault is sloppy coding.
TCAP-Abort
Why not make an installation system that works as simply as clicking setuppackage.msi is in Windows and let the other problems solve themselves?
Oh man, you just opened the floodgates with this one. Prepare to be lectured on why the 37 different packaging standards make software installations easier than with Windows. Of course, the reality of the situation is that it's a crapshoot as to whether or not a package will work with whichever one of the 10,000 Linux distributions you happen to be running (chances are it won't), but hey.
Why not just make a working desktop first?
That would require setting aside this childish "Linux has to do every single thing that every single person on the planet could want it to do, and then some" attitude that plagues the community. No one wants to sit down and say "OK, let's mandate that all distributions have, at minimum, THESE particular packages that operate in THESE particular ways." No, no. That stifles choice somehow. Of course, everyone conveniently ignores the fact that some amount of standardization has to occur before Linux can be accepted on the desktop.
Yeah, this year will be the year of linux-on-the-desktop
You must have missed how the zealots are spinning this one now. See, there's no particular "year of Linux on the desktop" anymore, now it's "EVERY year that Linux gains popularity it's getting closer to the desktop!" Some clever guy came up with that one after everyone pointed out that Slashdot has been proclaiming every year since 1998 as the "year of Linux on the desktop."
The fact is, Linux needs games to be a success in the home. Windows 95 didn't really take off until DirectX - and MS's attendant publicity efforts - boosted it along. I feel that the Gnome people should be taking more care not to break SDL for the greater good of the Linux community.
It's especially amazing, considering that Gnome is an important part of GNU. What's up, Gnome foundation? Don't you care about documentation freedom?
With regard to the plans for new media and networking features in GNOME, I hope that the GNOME team leverages efforts from the x.org project to work towards a common implementation of those features. In particular, I think that the Media Application Server looks very promising. Since future versions of GNOME will likely be running on x.org anyways, the wheel should not be re-invented with respect to advanced media features.
Because most people do not install much software and when they realize they do they make terrible mistakes in choosing the biggest most colorful box or the first website that hits on google. IF you include more software that would likely satisfy upcoming trends and needs of your users you reduce the chance that they will go get ripped off or buy something incompatible.
An Education is the Font of All Liberty
It seems like the ROX and Zero Install folks had the same idea...
As far as my Gnome experiences have taken me, I find that there are a lot of features that are incomplete and/or not fully stable. I think the developers should focus on getting everything that they have working first, and then start fleshing it out with more applications.
As for the 'long term' projects, I don't really have a necessity for a blogging application. Which services will it integrate with? Or will it use one of the common APIs? I ask this because a friend and I are working on a content management system.
Since when has Linux desktop environments started to integrate exclusive programs into the respective environments? Will this eventually end up like the integration of Internet Explorer with Windows? I thought one of the aspects of Open Source was about choice, and so, will this integration limit choice? What if the DE was designed to be modular, where you can install/uninstall components at will? I agree with a previous poster, that software should be easy to install.
Regardless, I'm looking forward to the new release.
Amen. Features come second when your core framework is fucked.
IMHO, MS is finally getting something right - the framework they're designing for Longhorn is goregeous. XML GUI and class definition and all the crummy header and import crap, and C# for the procedural code. Basically, C# as a scripting engine, one almost as fast as straight C. Compare that with the sluggish Python scripts other systems use.
OS coders could do this. Just because moronic Java developers converted platform agnositicism from a nice idea into ideological zealotry doesn't mean OS coders have to. GNOME has a wonderful idea with using Java.
Think of it this way: you code all your heavy lifting code in painful C and C++. Your 3d model renderrers, your window placement, etc. Then you code all the mostly event-driven procedural crap in Java. Tons of apps do this already, but with sluggish VB or Python or Perl. Instead we do it with Java, which, compared to real compiled languages is slow, but compared to a scripting language it rocks ass.
This is what Microsoft is doing with Longhorn, and its a wonderful system. Try modding Unreal Tournament to experience a game engine built along the same paradigm (albeit without the wonderful XAML concept of Longhorn) and you'll see how much of a joy this is to code with.
Regardless of all the monstrous feature creep (like giving IE a complete copy of the Firebird feature set) of Windows, the new coding framework of Longhorn has got me twitching with anticipation. Unfortunately, it looks like its up to the OS team with the shittiest track record (GNOME) to try and make a counterpoint for this.
Linux On The Desktop will be ready just in time for Windows On The Desktop With Super Fast R.A.D. Trustable Networked Operating System.
The tools are available, Longhorn is behind schedule, its not like an OS counterpart framework with an intelligent window manager couldn't be ready long before Longhorn. But I doubt it will happen.
It seems to me that with this roadmap, Gnome is planning on becoming the swiss army knife that KDE is. That is the exact reason why I do *not* use KDE. Gnome in its current incarnation (2.6) as well as the last several versions have appealed to me because they provide just the right amount of eye candy.
I am not particularly an X fan. I don't go for the shiny point and click thing because its just another layer separating the user from the system. Hence, I often have maybe a dozen terminal windows upen spanned across my 4 desktops.
That's not to say that X doesn't have its virtues. I wouldn't want to use Lynx as my sole browser, for the Web really does have some neat interactive and graphical content. However, things like IRC, News, and even P2P filesharing really don't need a GUI. Oh sure, I use X-Chat, but that doesn't mean I don't appreciate Epic. And I actually really like Pine.
How would you like it if you could do realtime management of email on your computer from anywhere? And I mean anywhere. Run the email client you use at home from school, work, your mobile phone, etc? To do that, you need a client that can run in a terminal. This includes Mutt and Pine (amongst others). Hell, I even use (http://www.idokorro.com) idokorro mobile ssh to access my box from my car!
That said, everything has its place. But making Gnome into KDE is not the right way to go. If this happens, I will probably keep a backup of version 2.6 on CD somewhere and downgrade any new version from that my distro ships.
Ads? What ads?
oh, and 4 should be possible with Cairo and the new X servers. 2 sounds interesting, but I don't agree with 1 and 3.
If you don't get all the criteria right, well, it's back to compiling the software, or searching for the package you want (just like with Windows), huh? Personally, I prefer the Windows route.
Yeah.
:)
<sarcasm>
Having a set of standards for an installation to adhear to would just be wrong, after all, name one thing in computers that ever became predominant because of a standard
</sarcasm>
If I had mod points, I would mod you up
This space for rent. All reasonable inquiries will be entertained at proprietors discretion.
What about the vector graphics plans?
Is a SVG based window manager so far away?
Exactly. Package management is a distro issue, *not* a desktop problem. Of course, it's nice if you can just click an ebuild/RPM/DEB/whatever and it's installed automatically.
LOAD "SIG",8,1
Why not just make a working desktop first?
because for some reason today programmers can not understand the ideas of.....
Smaller.
Faster.
Better.
I really hope that someone will come in from the sidelines with a nice fast and easy to use desktop manager that has NONE of the added crud that is going into KDE and Gnome. I want all the added "features" to be add-on programs. if I want a battery meter, I'll download and install it.
If I want a blogger I'll download and install one.
I just wish that someone would either rip out the Gnome desktop functions, and Both KDE and Gnome copy paste and drag functions and strap them onto xfce after removing the bloat. (Oh and add a decent menuing system so programs can self-install launch icons easily by dropping a symlink in a directory location!)
I want the speed and TINY footprint of XFCE with the decent desktop managebility of Gnome and cross app cut paste.
that is it. no video editor built in, no mp3 ripper built in, no web browser integration, no launch feedback, no nothing but the job it is designed for.
coule we PLEASE get some genius programmers working on a fork of Gnome and remove 70% of the cruft? or they can do KDE... I dont care...
the rest of us simply want small fast and capable.
please?
Do not look at laser with remaining good eye.
Compared with
1. apt-get install foo
Which one is simpler?
Reading Package Lists...
Building Dependency Tree...
The following packages have been kept back:
[long list of packages]
112 packages upgraded, 0 newly installed, 0 to remove and 125 not upgraded.
Sorry, but the following packages have unmet dependencies:
[long list of dependencies]
Disorganized series of thoughts follow.
Make everything as simple as possible, and no simpler.
It seems the Gnome architects often forget the important second part of that goal. Or they are, frankly, deluded into thinking that there is no limit to how simple and appliance-like they can make the computer. There is a limit, and that's when I can no longer adjust it to fit me.
In contrast, this is Microsoft's lofty goal, which is good enough as it stands, but they too still forget the nuances in that goal.
Make the easy things effortless, and the hard things possible.
Desktop designers can't just cherry-pick a few simple problems and write a few lines to make it easy. While it's noble to strip out the rarely used options, or the options that "confuse" the newcomer, it is NOT ACCEPTABLE to bury the familiar power interface behind a gconf/registry setting, or to make the familiar power interface unreachable. (You hear me, Nautilus?)
Allow configurability. Allow personalization beyond just the stupid passive things like wallpaper and skins. Let a user choose their favorite way of presenting information, and be smart about it.
Commit to finishing the features you start. How long has a Gnome-Menu editor been promised, but neglected? Ever since Gnome 2.0, they've said, "well, real soon now." We thought it just barely missed the deadlines for the first distros with Gnome 2.0, but I still can't edit my launcher menu. If obvious features aren't usable, then don't go announcing major X.0 version releases.
[
I'm with you, they need a good installer.
# Distributions that don't have apt-get. Or yum. Or emerge. Or the other 23 different, incompatible package managers.
...or you use aptitude, which lets you find appropriate packages.
I use Debian. All my boxen and all my lusers use Debian. What isn't available for Debian?
# The possibility that what you're looking for isn't packaged.
Improbable. When you want to make software available for windoblows, you make an EXE and an MSI and a DLL. When you want to make it available for Linux, you make a DEB and maybe an RPB. And you release the source as a TARball.
# That you know offhand what the package name is.
# The need to point your installer at different repositories if what you're looking for isn't at the default one.
Debian's repositories have over 89,000 packages available, including the one you want.
Ditch metacity as the windows manager. Please. Also, after installing both the latest Gnome and KDE I can say without any doubt (at least on my machine and configuration, etc) that KDE is *much* faster than GNOME as almost everything now. It's now GNOME that feels bloated and out of touch.
*Fortitudo, aequitas, fidelitas.*
I'd like to be able to print directly from the Snapshot app. I'd also like to be able to select a single window instead of just the entire desktop.
How about being able to have a different wallpaper on each workspace?
apt-get dist-upgrade, then.
Debian is the gold standard by which Linux shall be judged. And it shall be judged worthy.
Use aptitude. It installs all the packages you want, as many times as you want, and is free.
Don't have mod points, so I'll just weigh in with an "I agree."
Believe me, I'm as surprised by my comment as you are.
I use Debian. All my boxen and all my lusers use Debian. What isn't available for Debian?
Typical childish behavior. "I use Debian, therefore the whole world uses Debian!"
Improbable. When you want to make software available for windoblows, you make an EXE and an MSI and a DLL.
Well no, not really. You can release the software as is (ZIP of the contents), use InstallShield, MSI, etc. Any route you take, when you download the installer, it works.
When you want to make it available for Linux, you make a DEB and maybe an RPB.
Ah, but you're forgetting that there are RPMs for Redhat, SuSE, and Mandrake (and possibly others, I'm not sure), each of which may have issues that prevent the RPM from working across those three distros. Then there's Slackware TGZs, and other obscure package formats I'm sure I haven't even heard of yet. And you still haven't guaranteed that what you've packaged will work on any given Linux system.
Debian's repositories have over 89,000 packages available, including the one you want.
And yet, people make their own repositories, why?
So that'd be WindowMaker then.
By summer it was all gone...now shesmovedon. --
I hate to say it, but I really think that right now M$ is unbeatable on the desktop market (at least for i386...lotsa people are switching to OSX). If we can beat M$ at running M$ apps. and providing an even simpler interface, then I'm sure the market will swing. I think that GNU/Linux developers don't want to do that though, since the goal was to write GOOD software, and just because we win over windows users doesn't mean we're writing good software.
Finally (I guess I'm blabbering): Why Do We Care So Much!? If people want to use windows, what's it to us? That's one less person in #debian complaining about X telling them there's no screens found.
I use linux because I like having control over my system. I like that I get to control everything. But if you're using windows, you want dumbed-down software (in most cases).
-Garrett (the carrett)
I'm against picketing but I don't know how to show it.
It's not even a gnome thing. I'd like to see a package format defined that everyone can use.
.tgz package. Maybe an rpm or something (but rpm2tgz never worked for me), so I'd end up installing from source.
/bin, /usr/bin, /usr/local/bin... /opt/bin (what does opt mean?) hell OpenLDAP seems to like to put it's daemons in /usr/libexec.
/*/bin folders on seperate read-only partitions or network shares, /tmp on a ramdisk, /home on an nfs share, etc.. But who does that on a desktop system? Most have one big partition for all of it.
I used to use slackware (still do on most boxes) and I'd find some app I wanted to install, alas no slackware
So now I'm trying out gentoo. Oops, no ebuild for what I want. Or maybe I don't know the name of it. After browsing around the portage trees for an hour or so, I'm back to installing from source tarballs again.
Distros, well even projects, all have different ideas of where stuff should go, too.
I frankly don't see the point in the unix style "binaries in this folder, config files in this one, data in this one" thing. I like the c:\program files\nameofprogram and "My Documents" way of handling things. That'll never change in unix land, but it sure is nice.
I understand the logic.. You can have all the
I don't need no instructions to know how to rock!!!!
You had pencils?!? Lucky bastard. Why in my da...OOF!
SFX: ashen club striking sack of meat...
SFX: thud
One of the highlights of KDE as far as making it usable for grandma is being able to search through the installation and find applications that aren't in the menu that could be incorporated into the menu.
If gnome is truly about usability, putting programs into the menu should be a piece of cake. I'm not sure if KDE has the end-all solution on menu management, but it could be improved in gnome.
On the other hand, gnome has done a nice job at being able to modify the menu directly from the menu (where it makes sense).
Some drag and drop capabilities in the menu would also be nice.
Free Ipod here
Here is my take. Linux will succeed on the desktop when more developers and ISVs jump on board. This won't happen until GNOME is a better development platform. How can you make it better? Well, I'll share my opinion (even if you didn't ask.)
Developers want to quickly build applications. Right now, a lot of the development focus for GNOME apps is using C. That's a generalization, but a fairly accurate one. They have bindings for many other languages, but they usually don't get the spotlight. Fold the bindings projects into the main project. For example, fold Gtkmm (C++ bindings) into the bigger GTK effort. Likewise for other language bindings and other libraries. Make sure these bindings are as identical as possible accross target languages, so the learning curve from one language to the next isn't so great. Right now its easy for a newcoming developer to find the main project (ie Gtk), but no so easy to find information on how to use it with his/her preferred language.
Once that has happened, stress the fact that using GNOME you can develop apps in a wide variety of languages. Lay the whole Java/C# thing to rest and support both. Linux has an opportunity to become the premier development platform (which should rest nicely with geek and open source ideals). Everyone says choice is key, but then they try to rope you into a development methodology. This isn't necessary. Build incredible libraries (likely in C) and then bind them to as many higher languages as possible, and always keep these bindings current with the mainline. Developmers will come in droves, and make great applications, if they can pick and choose the most appropriate technology rather than having it dictated to them.
-- Fighting mediocrity one bad post at a time.
i wish.. windowmaker has horrid desktop control, horrid cut and paste and horrid integration... I cant add anything to the program menu without a fight.
those are all VERY simple things compared to a built in blogger tool.
You know what I'd like to see? Real virtual desktops. The current "virtual desktops" are really just virtual screens, not desktops. Full virtual desktops should act as completely separate desktops, with their own set of icons, etc. Obviously this would not be for everyone, but I would love to see it as a user-selectable option.
This is related to a problem I have with Gnome 2.4 (I don't know if it's been fixed in 2.6): when I double-click a desktop icon, I expect that program to launch on the desktop where I clicked the icon. But if I switch desktops before the program window shows up, it opens in that desktop instead. Maddening, especially on a slow computer such as mine! Also, dragging items between virtual desktops needs to be made easier (again, apologies if this has improved in 2.6).
I also have to second the idea of a sound server replacement, though I'm not thrilled that it's in the "Long Term" section of the roadmap. The current situation is frankly an embarrassment for a desktop environment of Gnome's stature.
In the pie-in-the-sky department, I would love to see options for a Mac-style menu bar, and Acorn-style file choosing via drag-and-drop rather than with a file selector dialog.
Mike
I know exactly what you mean. KDE, as it's default, just makes me angry and i can't tell why. It's as if they try to be just a bit more flashy or bubbely then windows and everything seems just, slightly not how you expect. It's like walking from a yellow room to another yellow room that is 3 shades off, just frustrating. Now if the room was blue, you wouldn't notice or care. Frankly, I just use fluxbox. Now that's a clean desktop.
Granted, if I help someone switch over to Linux, i set them up with KDE, but donig so just makes me angry inside...
The Neo-Bohemian Techno-Socialist
It wasn't mentioned in the article at all. Neither was the word "speed" or the word "faster".
I guess Gnome is destined to remain the slowpoke of the GUI world. Who would have thought KDE would be the quick one.
Deleted
"the rest of us simply want small fast and capable."
And everyone else can stick to Windows or the Mac.
I wouldn't mind so much but this Gnome/KDE cruft is permeating into otherwise useful programs. GTK used to be excellent; it's still good but why does the file requester insist on forcing Gnomisms on me?
I could go on but I won't. Suffice to say, the moronification of UNIX is continuing apace.
a Windows Update tool
Now why would I need Windows Update on my Linux machine?
Oh, wait. You must be talking about something like apt or yum that's included in pretty much every damn modern distro.
Sheesh. Yeah, this year will be the year of linux-on-the-desktop now that we have integrated blogging. That was sure the barrier for entry to me.
... oh brother, i might do a "rm -rf /" and go cry myself to sleep.
the day that "find / -name blog" gives me some found files
1. Scratch the plans to add everything under the sun to the desktop, and focus on reducing the footprint (heh) instead.
2. Stop the user-hostility effort (disguised as a usability effort). Gnome 1.2 was way more usable than 2.x is. Spatial nautilus is a typical Gnome 2.x disaster (see also several "features" of the new filechooser and just about everything about Metacity): "abstract principles we dreamed up (and artificial usability tests, on occasion) tell us that, contrary to what the vast majority of real users may say, this is the way to go; since we're so much smarter than our users that we always know what's right for them and they don't, the ability to change this behavior should be well-hidden or nonexistent."
- more stability.
- Good, complete and easy to navigate configuration tools.
- less integration, more modularisation (it should be easier to use another wm for example)
Gnome aims to be a complete DE and thus to also be an option for beginners - it has to takes care that is is not squeezed between a clean small DE like xfce on one side and an fully bloated KDE in all its might on the other. Advanced users also tend sometimes to go for the leaner wm-only solutions like *box, fvwm and the like.I think this comptition explains the above list. The first point is essential for beginners and advanced users alike. The second a result of gnomes obscure usage of gconf and essential for beginners, while the third was always the unique selling point of gnome over KDE.
That's quite an facile editorial but you can't expect better from normal users. My screenshot looks better than yours. Evolution is better than KMail, GNOME looks more polished than KDE and so on. I do use XChat, Abiword, Rhythmbox.... ...usually you get stuff like these from normal users. And this is ok since you can't blame them for stuff they simply don't know about or don't have a slighest knowledge about.
Such editorials are hard to take serious since they are build up on basicly NO deeper knowledge of the matter. Most people I met so far are full of prejudices and seek for excuses or explaination why they prefer the one over the other while in reality they have no slightest clue on what parameters they compare the things.
If people do like the gance ICONS over the functionality then it's quite ok but that's absolutely NO framework to do such comparisons.
I do come from the GNOME architecture and spent the last 5 years on it. I also spent a lot of time (nearly 1 year now if I sum everything up) on KDE 3.x architecture including the latest KDE 3.2 (please note I still do use GNOME and I am up to CVS 2.6 release myself).
Although calling myself a GNOME vetaran I am also not shy to criticise GNOME and I do this in the public as well. Ok I got told from a couple of people if I don't like GNOME that I simply should switch and so on. But these are usually people who have a tunnelview and do not want to see or understand the problems around GNOME.
Speaking as a developer with nearly 23years of programming skills on my back I can tell you that GNOME may look polished on the first view but on the second view it isn't.
Technically GNOME is quite a messy architecture with a lot of unfinished, half polished and half working stuff inside. Given here are examples like broken gnome-vfs, half implementations of things (GStreamer still half implemented into GNOME (if you can call it an implementation at all)) rapid changes of things that make it hard for developers to catch up and a never ending bughunting. While it is questionable if some stuff can simply be fixed with patches while it's more required to publicly talk about the Framework itself.
Sure GNOME will become better but the time developers spent fixing all the stuff is the time that speaks for KDE to really improve it with needed features. We here on GNOME are only walking in the circle but don't have a real progress in true usability (not that farce people talk to one person and then to the next). Real usability here is using the features provided by the architecture that is when I as scientists want to do UML stuff that I seriously find an application written for that framework that can do it. When I eye over to the KDE architecture then as strange it sounds I do find more of these needed tools than I can find on GNOME. This can be continued in many areas where I find more scientific Software to do my work and Software that works reliable and not crash or misbehave or behave unexpected.
Comparing Nautilus with Konqueror is pure nonsense, comparing GNOME with KDE is even bigger nonsense. If we get a team of developers on a Table and discuss all the crap we find between KDE and GNOME then I can tell from own experience that the answer is clearly that GNOME will fail horrible here.
We still have many issues on GNOME which are Framework related. We now got the new Fileselector but yet they still act differently in each app. Some still have the old Fileselector, some the new Fileselector, some appearance of new Fileselectors are differently than in other apps that use the new Fileselector code and so on. When people talk about polish and consistency, then I like to ask what kind of consistency and polish is this ? We still have a couple of different ways to open Window in GNOME.
- GTK-Application-Window,
- BonoboUI Window,
- GnomeUI Window,
Then a lot of stuff inside GNOME are hardcoded UI's, some are using *.glade files (not to mention that GLADE the interface buil
Can't people just install their own peer-to-peer and blogging apps?
Sure, but they can install web-browsers, mail clients, et cetera too.
Why not make an installation system that works as simply as clicking setuppackage.msi is in Windows and let the other problems solve themselves?
Often it is that easy, with a number of caveats, however. If you use a distro and stick with packages for that distro, you won't have a problem. If not, well, you made that decision. People who aren't Unix saavy should stick to packages designed for their distro, meaning they should be using a mainstream distro like Fedora, Mandrake, SuSe, et al.
Why not just make a working desktop first?
News to me that it doesn't work, considering I'm using it now, and been using it for years. I'm a bad example of course, being Unix saavy and all, but I have several friends who switched to Linux on their own, over a year ago.
Sheesh. Yeah, this year will be the year of linux-on-the-desktop now that we have integrated blogging. That was sure the barrier for entry to me.
Well I'm always glad to hear of another Linux convert...
Sticking feathers up your butt does not make you a chicken - Tyler Durden
Exactly. Package management is a distro issue, *not* a desktop problem.
.NET for people to develop for. Until then, GNOME and KDE are exactly what they were when they first came out--hacky desktop emulators stuck on top of X to make it look like Linux is in the same league as Apple and Microsoft in the desktop market. "Look, we have an integrated browser too! Look, a taskbar! 7 second app startup time? Ignore that, here are more screenshots!"
Absolutely, 100% wrong. Your abitrary mindset is the primary problem. "I've randomly decided that application installation should be handled by the distro!" No reason or proof or logic is given.
How will you ever have a seamless, professional, sane desktop environment that doesn't even have an installation/uninstallation API? The very idea is so backwards and laughable, I fully expect Linux to take another 10 years to reach the level XP and OS X are at now.
Since Linux crunchies are absolutely dead-set on never replacing the interface failures that are taskbars and start menus, I want to at least be able to have applications install their links on the menu and give me shortcuts to their uninstallers automatically.
I want to be able to just download an installer for an app onto my desktop and double-click it. A desktop environment should keep track of the desktop applications it has installed. Forgive me, but I want my desktop to be self-aware of what the hell it has installed and how to uninstall them. We're trying to compete with OS X and Windows here!
You have two options:
Do it in "bundles" like OS X, where applications install to folders in an Applications directory, and you can remove the program just by dragging the folder to the trash.
Do it like Windows does, where applications register their locations, tell Windows how to uninstall itself, and adds appropriate shortcuts and entries in the start menu and "Add/Remove Programs" dialog.
High school Linux zealot: "B-but we have a hundred possible external package managers to run all that!" Yeah, good luck remaining 15 years behind everyone in the GUI department just because nobody can be arsed to stop working on new sidebar buttons and integrated blogging functions in order to create a sane API in the vein of Cocoa and
You want a litmus test? The day someone can buy a printer that comes with a CD, stick the CD into the drive, a menu comes up to install the binary driver, and afterward the printer works. All done in a Linux desktop. Then it would truly be the "year of the Linux desktop (tm)". At the current pace, that is definitely not going to ever happen with either KDE or GNOME. They both are horrible desktops, and people overlook it because they don't want to admit that Microsoft still gets this part right. To Linux guys, it's a penis length test of shoving in as much pointless crap as possible to compensate for the lack of very basic functionality.
"Sufferin' succotash."
While less intuative, there are several other desktop or windows managers that are light weight, easy to use if you have an intermediate level of knowledge (not for joe user, that's who Gnome and KDE are trying to cater too), and about as stripped down as it gets. Best part, they don't try to be windows at all.
Personally, I use fluxbox and it's a dream. It comes with a couple of x applications (i'm sorry if x-calc is too much bloat for you) but otherwise it's the least imposing interface i have ever had teh good pleasure of useing. Window tabbing, and no damn start bar or menu icons (unless you want to add them) adds to a much cleaner interface.
If you're comfortable using terminal a lot and fiddeling with system files, then why bother with KDE or GNOME. Let those be what they are trying to be, an interface and solution for the average person.
A KDE Lite would be nice though.
(note: This does not mean i support allowing joe user the ability to write blogs. Infact a blog crippeling patch for everything wouldn't upset me inanyway)
The Neo-Bohemian Techno-Socialist
I like Firefox just fine but it has one gigantic mis-feature that keeps me using Epiphany: profiles. I hate 'em. They really don't make much sense on a mutli-user OS anyway (individual user preferences are handled at that level, where they belong). Most of the time when you open up another instance of Mozilla/Firefox, all you *really* want is another window. It's high time they killed profiles!
I really hope GNOME sticks with Epiphany, or fixes Firefox's wart(s).
How appropriate. You fight like a cow.
It works on my Fedora system.
Download an RPM, double-click on it, voila, it is installing!
Get out of the dark ages.
"Fighting terrorists with millitary might is like killing a mosquitor on your Dad's forehead with a rifle."
It seems like features disappear and nothing is added. I just finished compiling KDE, it's time I gave it another try...
This saddens me, I've been a Gnome fan for a long time... but the whole .Xmodmap fiasco has me fairly annoyed right now.
One of the MSDN tech videos demonstrated a guy writing a 10-50 line XAML app that updated his website blog for him via .NET.
We're basically chasing someone's tail again--as we have done for the past 10 years. I agree with another poster here, I want a working desktop first. Where's the sane development API? Oh, I forgot, everything is about "choice" and we need 23 different libraries, APIs, and window managers that all conflict with each other (I have to install two entire fucking desktop environments to be able to run each other's apps! Amateurish and unprofessional). For crying out loud, my GNOME memory footprint is sucking up more RAM than XP does on my laptop. I don't even want to think about that krudgy slow thing we call KDE...
How is it geeks can get so many things right--Linux kernel, Apache, PHP--and so many things wrong--KDE, GNOME, XFree86, and basically anything attempting GUI usage? It's like when it comes to moving away from the technical stuff and actually getting creative and interacting with people, geeks fall short not only in social life but in their application projects. Not a troll but a real observation here--the problem is who is developing these projects and how they approach them, which is illustrative of the community as a whole (including Slashdot)...
"Sufferin' succotash."
Case in point. How do I install it? This the typical thing you see in Linux land.
Well it appears that you haven't ever heard of the Linux Standard Base project which can be found at http://www.linuxbase.org/ The goal of this project is to set a standard base for linux distros. Several of the major linux distros are members of this and try to adhear to its standards. There is also http://www.freedesktop.org which is working on standards for the desktop to make it easier to write programs for linux. Before you go on a rant and rave you should definantly do your research.
No, he didn't open the floodgates. You just did.
.twmrc files, to .fvwmrc files, to WindowMaker dialog boxes, to Gnome and KDE dialog boxes. I've gone from spending two days configuring dialup over ppp on my 486DX2, to clicking a button and watching it all set up.
Oh man, you just opened the floodgates with this one. Prepare to be lectured on why the 37 different packaging standards make software installations easier than with Windows. Of course, the reality of the situation is that it's a crapshoot as to whether or not a package will work with whichever one of the 10,000 Linux distributions you happen to be running (chances are it won't), but hey.
Dude, fragmentation is what happens in healthy, competitive markets. And the fact that several packaging formats exist is a side effect of a healthy, competitive market of ideas. We don't WANT a monoculture in Linux, and for GOOD reasons. It might be a little inefficient to have competing standards.. but it leads to furthering the pace of development. It provides more ground for ideas to be tested on.
That would require setting aside this childish "Linux has to do every single thing that every single person on the planet could want it to do, and then some" attitude that plagues the community. No one wants to sit down and say "OK, let's mandate that all distributions have, at minimum, THESE particular packages that operate in THESE particular ways." No, no. That stifles choice somehow. Of course, everyone conveniently ignores the fact that some amount of standardization has to occur before Linux can be accepted on the desktop.
It's that childish attitude that's gotten us this far. I've been with this OS for a long time. And from what I've seen, the REASON that it's where it is today is BECAUSE, not DESPITE, of the fragmentation, and breadth and width of scope that Linux provides. That is the operating system's MAIN advantage.
That's why I can sit here, typing up a post in KDE on my Linux workstation desktop, while indexing gene sequence databases on a Linux server, and also run a massively parallel BLAST across the entire NCBI sequence database using on the 32-machine Linux cluster with no hard drives. I can do it because people who wanted these tools to do something different, to accomplish THEIR goals, were able to do so, and took the time to do so. This is true across the spectrum of Free/OSS software. Who are you to lambast their efforts?
This shit might not matter to you.. but it does to others.
You must have missed how the zealots are spinning this one now. See, there's no particular "year of Linux on the desktop" anymore, now it's "EVERY year that Linux gains popularity it's getting closer to the desktop!" Some clever guy came up with that one after everyone pointed out that Slashdot has been proclaiming every year since 1998 as the "year of Linux on the desktop."
The "year of the desktop" guffaw you chide us over is a sign of this community's general unbridled optimism. We know what we have is better, and every year we say to ourselves.. "they'll understand this year.. they'll finally come around". Every year is the year of Linux on the desktop. It's also the year of Linux on the server, and the year of Linux on the cluster. Because Linux's desktop feature set, and server featureset, and every other featureset evolves and improves every year. I've gone from twiddling config options in
Nobody is above elitism. There are the elites who whine about how the unwashed masses are flowing into what used to be an almost private club. And then there are the other elites.. the reverse-snobs.. the ones who, ironically, whine about Linux "elitism" because it doesn't serve THEIR needs RIGHT NOW, JUST THE WAY THEY WANT IT. Populism has the ability to be just as incestuously corrupt as elitism.
-Laxitive
Those are being done on the X level in the new x.org server. Not GNOME's problem.
Anything is better than KDE's completely hilarious, amateurish icon label dropshadows. They don't even fade out gracefully. How did anyone think that should be something to include in an official release?
Someday, just someday, I'd like to see hardware acceleration. The Y-Windows boys are already planning it.
"Sufferin' succotash."
It's staticly type checked wherever possible. It's compiled using free tools (GNAT Ada compiler). It's trivially easy to import/export to C. C++ is harder but possible. There are bindings to Gtk+ and Gnome libs. Garbage collection is optional so you can be fast and dirty when needed. Oh, and it's had proper typesafe generics and emumerations (cor!) since 1983.
n gu age has a pretty good overview.
There are no polictical or patent timebombs unless you hold being invented by the military but then so is this internet thing you're using. In fact the only real disadvantages are a lack of Free Ada software and the fact we haven't standardised on a collections framework yet (Ada 200x where x>=5).
http://en.wikipedia.org/wiki/Ada_programming_la
Sig pending!
#include
The Neo-Bohemian Techno-Socialist
Y-Windows
Their IRC channel is active, and they're already working on the widgets. They plan a 1.0 release within a year. Full hardware-acceleration, network transparency, and a complete replacement of X with a user-level X-compatibility layer. The PDF describes all the reasons why they're replacing X. Stuff even I didn't know.
"Sufferin' succotash."
How about making it possible to login onto two different machines with the same account and home directory? I'm not sure with newer versions of Gnome then 2.2, but it really dosen't work well at all.
Why in all the nine hells would including Mozilla, a Web Browser, allow them to get rid of Nautilus, a File Manager?
BTW, GNOME already depends on Mozilla. It's one of the requirements for Epiphany, which is included in the Desktop package set. Mozilla is _not_ defined as part of the Platform (developer packages) because Mozilla constantly breaks API/ABI, making it impossible to develop an application on top of it and expect it to actually Just Work(tm). Mozilla may move into the Platform once the GRE is out and stable.
The Roadmap, if you actually read it, states that the Mozilla work is in regards to cooperation with the Firefox developers, as the development goals of Firefox and Epiphany are pretty close, except Epiphany is all GTK/GNOME while Firefox uses that unfortunate cross platform hack.
And yes, cross paltform UIs are hacks. You either end up with Mozilla/Firefox, where the app looks like an alien everywhere, or OOo, where the app looks native on Windows and like an alient everywhere else. A far better strategy is something like Abiword where there is a single core and multiple frontends targetted at specific platforms, or something like the Mozilla GRE where the Mozilla core is provided for easy deployment of multiple platform specific front ends (like Epiphany or Camino).
obstacles that unnecessarily hamper the user experience."
Are gnome developers aware that speed, or lack off, is an obstacle that hampers gnome users' experience? I might be in minority, but speed was the only obstacle that made me look (and still looking) for a gnomeish alternative.
(Redundant, I know.)
Personally, I'd love to see D being used instead of .NET or Java. For one, I don't trust Microsoft to let Mono live when an important part of the Linux desktop is dependant on it. Second, as for Java, it leaves too big of a memory footprint, and it is still not available on all distros. :)
Besides that, I don't like VMs, but that's a personal thing.
So, why not D? Most people knows the advantages, or can otherwise check the website [http://www.digitalmars.com/d/index.html]. It's very clean, familiar, fast and gives most or more advantages than C#/Java. It has gotten far in development. The frontend is being integrated to GCC. So why not?
"So unmerciful is life, that everything afterwards is too late."
So you go to freshmeat.org or just type what you're looking for in google with +linux and +software. Wham, you get a list of all the different things that may be applicable. Then you open up your graphical package manager and type the name of the programs that you found that are interesting. Hit install, try them out, uninstall the ones that you didn't care for.
It's all very slick, and the only way I can see this getting better is to add better search to freshmeat and automatically turn it into a debian/fedora/gentoo repository so that you simply click on the program in your browser to install rather than switching to a different package management tool.
Michael
I personally prefer to use Firefox in my Fedora Core 2 box. I believe it would be wise to standardize around Firefox and have Gnome's brower be tied more closely with Mozilla's community.
No matter what happens with the default browser situation, I'll end up using Firefox no matter.
Brandon Petersen
Jesus, how many PCs do you work with? I have endless hassles with windows installer crapping out for no reason all the time. And this is on software that was paid for at exorbitant rates. It can't even make it past the installer. Absolutely pathetic. Of all the lousy products in the world that's got to be one of the worst. That's not a model I'd emmulate.
I know how you feel, but gcc has been able to compile Java source straight to native code for quite some time now :-)
Stick Men
One additional point.
Linux _has_ standardization. Choose a distribution, and stick with it.
For example, Mandrake Linux + kde:
One method of installing software - CHECK
One interface and widget set - CHECK
One set of 'canonical' programs - CHECK
Well, looks like it has everything you want right there. Perhaps you'd like to use the Mandrake Linux standard?
Or maybe not.. maybe you'd prefer the RedHat Fedora Core standard:
One method of installing software - CHECK
One interface and widget set - CHECK
One set of 'canonical' programs - CHECK
Or maybe you would like to choose the Debian standard? Or perhaps the S.u.S.E standard?
"But wait!", you say, "There are too many standards! There should be only one!".
Perhaps.. maybe there should be a Linux standard. But then, how are you going to choose between the Linux standard and the Windows standard and the Apple standard? How are you going to handle that choice?
We should roll that in to one standard too. The OS standard. But shit.. we're not home free yet. How are you going to choose between all the different competing hardware on which the OS standard runs? Honestly, why should you be expected to invest time and effort finding the one that's right for you when you could make one that FITS ALL SIZES?
But hey, no chance of that ever happening. So I guess for now, the world remains complicated.. and we remain forced to make choices.
What a travesty!
-Laxitive
Outside of locked down corp desktops, I have never seen a machine where the user did not install something, even if it's only WinAmp.
for proposing this usability nightmare, but how about a filemanager that can handle hidden files easily?
I still can't get over the fact that people writing a linux desktop think it is a gain in usability if you have to press Ctrl+L and then Tab to select a hidden file in the filemanager.
try using the tool that comes with your distro (or one written for your distro)
i use slapt-get in slackware
ther people use:
apt-get - deb
urpmi - mdk
red carpet - ximian
various others for other distros
plus, there's kpackage, which supports many formats
Why, apt-get install aptitude of course.
1. KDE has been defining its UI with XML for years.
2. Mozilla did XAML first. They called it XUL, though.
3. KDE has Java bindings to do all sorts of stuff, like write applications or whatever.
4. Through KDE's DCOP, you can script applications to respond to whatever events you want, with whatever language you want.
5. Python isn't as slow as you think it is.
Before bashing things, you should probably learn about what the hell it is you're talking about.
Dude, fragmentation is what happens in healthy, competitive markets.
No, in competitive markets there's different, competing products. The kind of fragmentation Linux has only works against it. How does anyone expect to focus their efforts when everyone's attention is split 1,000 different ways? Why should Linux compete with itself? Duh?
It might be a little inefficient to have competing standards.. but it leads to furthering the pace of development.
A little inefficient? May I nominate you for understatement of the year?
And riddle me this: how can the pace of development be furthered more with hundreds of similar, but different projects instead of one focused project?
And from what I've seen, the REASON that it's where it is today is BECAUSE, not DESPITE, of the fragmentation, and breadth and width of scope that Linux provides.
And just imagine where it would be today if everyone focused on creating one standard piece of software for everything they needed instead of creating 20 or 30 of everything, when 9 times out of 10 it's clear that there is only really one superior piece of software in the whole bunch.
Yet another thing Linux zealots need to shed: Their snotty, elitist attitudes.
I remember the first months after OS X came out and the *NIX geeks were starting to come over to the platform. New OS X users would post technical questions, and these snotty *NIX types would come back with their arrogant RTFM type comments. It was very satisfying to see the Apple community dress them down properly for being the arrogant snots they were and told them if they weren't willing to be helpful and supportive to get the hell off the platform. The real jerks among them went back to Linux.
You can tell a great deal about the character of a man by observing those who hate him.
No, I have heard of LSB. However, adoption of the standards is what matters, not sitting around talking about it. As it is, Linux is horribly, horribly fragmented due to the hundreds of available distros, only a few of which are compatible with the LSB. I find it very funny that you mention that the major distros are "trying" to adhere to the standards -- should they be able to definitively state that they DO adhere to the standards?
Software is not supposed to be about how to work around a useability issue. - Ken Barber
The optimist proclaims that we live in the best of all possible worlds. The pessimist fears that this is true.
Insightful? Come on moderators...
Why not make an installation system that works as simply as clicking setuppackage.msi is in Windows and let the other problems solve themselves?
Of course, the core goals of any desktop environment like GNOME: invent your own packaging format. Hello?
Why not just make a working desktop first?
Not even a well-disguised troll. Try some subtlety next time.
Do you even know anything about perl? -- AC Replying to Tom Christiansen post.
... some divine entity will chime up in the alt.creation newsgroup and end that "back in the day" joke with some incredibly easy answer. I doubt 42 will cut it, but who knows...
Fight hunger. Filet a politician and send him to a 3rd world country of your choice.
That's what projects like LSB and FHS are for. Theoretically, if your distribution complies with these standards, a standards-compliant package will integrate beautifully into your system.
But that day is still a long way off, it seems. Right now, at least, I think our collective job is to be vocal to our various distributions that LSB/FHS compliance is important to us, and that if it doesn't agree, some other distro does.
WeRelate.org - wiki-based genealogy
Real men use punch cards....
They should rewrite it in LISP and integrate within emacs, that's The One Right Way.
... It's faster, has better integration (kwallet, addressbook, etc), DCOP, and Konqueror URIs are wicked cool (man:/find)... That plus the latest Baghira theme/window behavior makes it OSXy enough for me.. I _love_ kicker popups (integrating with kopete, apollon, juk, etc) and all the other candy that I expect in my GUI.
I'd like to see konqi cleaned up a bit (every app's first menu should be 'file', I'm sorry) and a few of the 'political' decisions in apps are impediments (kmail IMAP filters via headers vs sieve, kopete tray popups should display connected buddies, etc), but I'd rather run it than GNOME any day.
1, 3, 4. I did not know that. Only developed on Gnome. I think I may be giving KDE a second look - I had discarded it as "Windows, except that it's _almost_ free software".
2. Yes. Unfortunately:
a) nobody uses it and
b) I am not personally impressed with its performance.
Maybe XAML will be the same, maybe not.
5. Python is slow. I've used it extensively, and know how the interpreter works inside and out. Maybe native-compiled python or Jython is fast, but Python is slow, compared to JIT languages like Java and C#.
And riddle me this: how can the pace of development be furthered more with hundreds of similar, but different projects instead of one focused project?
Because hundreds of developers will never agree on the focus of one, focused project. And you shouldn't be expecting them to. A developer doesn't start a new project because he wants to improve an old one. He starts a new project because he thinks he can do better. Maybe most of them don't do better. But some do, and when they are better, they generally end up replacing the old ones. And we have an easier time replacing them since it's an unrestricted market.
And just imagine where it would be today if everyone focused on creating one standard piece of software for everything they needed instead of creating 20 or 30 of everything, when 9 times out of 10 it's clear that there is only really one superior piece of software in the whole bunch.
That'd be pretty awesome. About as awesome as it would be if the entire wold all held hands, hugged, and promised to be nice to each to each other from now on.
-Laxitive
Frankly, if the were to move to either of those two enviroments I'd switch to something else, KDE perhaps. Heck I'd go back to CDE/Motif if I had too.
I've never seen a Java app that worked well consistantly. I think the whole model has problems.
I love Gnome. I think it looks great, I think it works great. I don't mind the lack of options too much. But, I still use KDE for the simple reason that konsole is actually usable and gnome-terminal isn't. It takes more processing power for gnome-terminal to *scroll the text* from a compile than it actually does to compile. As a software developer that has 5-8 tabs open on a couple terimals and is compiling a lot, that just doesn't cut it.
I've read past mailing list logs trying to figure out why gnome-terminal got slower over time and the culprit seems to be the "functionally elegant", emulate anything, terminal emulation library. While I'm sure the code is easy to work with, the actual product isn't. One of the posts mentioned that Miguel doesn't even use the modern gnome-terminal any more.
I guess since the average user isn't a developer this hasn't been an issue. I guess I'll continue working with KDE (which is also a great system, but not perfect).
Dan
Why not make an installation system that works as simply as clicking setuppackage.msi is in Windows and let the other problems solve themselves?
Oh man, you just opened the floodgates with this one. Prepare to be lectured on why the 37 different packaging standards make software installations easier than with Windows.
Yes, but I can't get RPMs to install on Windows, now can I? (which is about as stupid a statement as calling it a "crapshoot" when RedHat RPMs don't install on Debian.)
Why not just make a working desktop first?
That would require setting aside this childish "Linux has to do every single thing that every single person on the planet could want it to do, and then some" attitude that plagues the community.
Or we could just point out that GNOME is a working desktop. Oh, that's right, Linux has to be just exactly like Windows in every way before it replaces Windows. Just being a good desktop isn't enough. Got it.
Yeah, this year will be the year of linux-on-the-desktop
You must have missed how the zealots are spinning this one now.
Is that what is says in the article? Oh, wait, the article doesn't say anything about "year of the desktop".
Oh, I get it, this is how the Windows zealots are spinning it now...
I swear people around here have the shortest memory author is of course oGalaxyo trolling as usual. And this is just the one's google caught. He posts the "EXACT SAME THING" in every story that mentions GNOME.
Because hundreds of developers will never agree on the focus of one, focused project.
And yet, somehow it happens in the commercial software world: Windows and OS X, Microsoft Office, etc. Any way you slice it, in the free software world there's thousands of man hours spent doing the same things, over and over again, when that time would be better spent concentrating on making the "superior" piece of software even better.
That'd be pretty awesome. About as awesome as it would be if the entire wold all held hands, hugged, and promised to be nice to each to each other from now on.
Your sarcastic hand waving does nothing to back up your point. It is entirely possible to focus software development efforts into making "the best solution" instead of aimlessly pouring effort into "100 different, equally crappy solutions". You just want to shake your head and pretend like it can't happen, simply because it doesn't happen in the world of Linux and OSS.
No, in competitive markets there's different, competing products. The kind of fragmentation Linux has only works against it. How does anyone expect to focus their efforts when everyone's attention is split 1,000 different ways? Why should Linux compete with itself? Duh?
Exactly. Everyone keeps falling back to that point. It's like a country that has been involved in a civil war for the majority of its existance trying to get immigration.
Not everything is analogous to cars. Car analogies rarely work.
Joe Desktopuser wouldn't know what a desktop environment is if it bit him in the ass.
Joe Desktopuser doesn't know what an operating system is, for chrissakes.
All Gnome needs to do is persuade Joe Desktopuser's CIO that they can switch the company's desktops to Gnome-on-Linux and by doing so save money and increase productivity year-on-year, with minimal retraining needed.
And after that, persuade Dell, Gateway, whoever, that Gnome-on-their-branded-distro is a better solution to bundle on their crappy PCs.
Joe Desktopuser won't be installing Debian; he doesn't need to know what Debian is.
What Gnome needs is security and ease-of-use to impress the CIO, a short transition period to impress the CFO, and pretty buttons to impress the CEO. Joe Desktopuser doesn't enter the picture.
I think Gnome's interface is elegant and KDE's inteface, while very colorful, it cluttered and knobby.
That is probably reason enough to make you irritated by KDE. It's a great project for the needs of many people but for others like you and me who get irritated by needless clutter KDE can be very annoying to use. And being irritated and annoyed is a pretty good reason for emotional exhaustion -- I think you already answered your question without knowing it.
501 Not Implemented
I mostly like Epiphany. It's well integrated with GNOME, and mostly it Just Works. After a crash or sudden shutdown, when you run it again it brings back all the pages you had open, which is great.
It's biggest problem for me is sucky performance. If I hit Ctrl+N to open a new window, my CPU usage goes to 100% and stays there for 3 seconds or so. And I dread saving a bookmark; CPU goes 100% for 4 seconds or so. I suspect there is some sort of N-squared behavior in the bookmark management or something like that, and if I get time I might build a debug version of Epiphany and run a profiler against it.
If they could somehow merge the Epiphany and Firefox projects, that might be interesting. If Epiphany could run some of the plugins from Firefox, I'd be very happy. But I wonder if the two projects are too diverse, and it might be more work than it's worth at this point.
steveha
lf(1): it's like ls(1) but sorts filenames by extension, tersely
Download an RPM, double-click on it, voila, it is installing!
That is assuming that you have all the dependencies satisfied. It's not the double clicking that's the problem, it's the tree of dependancies and sub-dependancies that is the problem.
Not everything is analogous to cars. Car analogies rarely work.
I know everyone seems to like Firefox, but I still like the old Mozilla project. While I like the fact that Firefox is standalone, with the old Mozilla, I can middle-click a link in my mail client and have it open up a new tab in my browser. Whereas if I prefer, I can regular click the link, and have it open in a new window or the old window.
I posted these observations to a mozilla help group, and the best they could come up with is something that forces the browser to automatically load new links into a new tab (which was a pain to set up on linux anyway).
Oh, and one other thing for both old Mozilla and Firefox (that someone mentioned before): please get rid of the profiles. It's insanely redundant to have each user with multiple profiles. This is a hold over from the Windows 95/98 days, and certainly isn't necessary anymore.
"he drew his sword Ringil that glittered like ice... and he wounded Morgoth with seven wounds..."
You are right. I think we should take this to the logical extreme and each distribution should include their own incompatable version of C, so that we get the luxury of having even more choices! After all, this would give us even more diversity, right?
DrLunch.com The site that tells you what's for lunch!
Distributions that don't have apt-get. Or yum. Or emerge.
Go ahead and name a distro in common use that doesn't have a package manager.
The possibility that what you're looking for isn't packaged.
I can release a source tarball for a Win32 app too. Whose fault would this be exactly?
That you know offhand what the package name is.
As opposed to Windows, where clairivoyance is built into the operating system...
Do you even know anything about perl? -- AC Replying to Tom Christiansen post.
Oh man, you just opened the floodgates with this one. Prepare to be lectured on why the 37 different packaging standards make software installations easier than with Windows. Of course, the reality of the situation is that it's a crapshoot as to whether or not a package will work with whichever one of the 10,000 Linux distributions you happen to be running (chances are it won't), but hey.
Wrong lecture. The lecture should be from Debian or Gentoo users who say how easy it is to apt-get or emerge packages.
Being a Debian user, I have to say apt is really nice most of the time. But its only as nice as the package repository. There will be issues that the average Joe simply won't be able to deal with, at least with testing/unstable. I have no experience with stable, but I would imagine a pure stable (no backports) should work with no hickups. Too bad its so out of date.
#!/
They would not install winamp if something similiar was already installed like xmms. The point is including those "killer apps" and lessening the need for more lib checking and incompatibilities. Not to mention the GUI for some Linux applications is wholly different than their windows counterparts.
An Education is the Font of All Liberty
And yet, somehow it happens in the commercial software world: Windows and OS X, Microsoft Office, etc. Any way you slice it, in the free software world there's thousands of man hours spent doing the same things, over and over again, when that time would be better spent concentrating on making the "superior" piece of software even better.
Yes, because in the commercial world, the guy in the big office gives you a wad of cash, and in return, you agree to spend 8 hours a day caring about what he wants you to care about.
Now, if you are interested in the products and results of that kind of model, then you are very free to choose to use Windows or OSX or whatever fits your brain, and pay the good man what he wants for the privilege of doing so. You are also free to choose the results of the free software model of development, and pay the price of having to choose the kind of system you think fits you best.
Directed development has its benefits. And it _can_ be applied to good uses in a small scale. On a large scale however, centralized management becomes intractable. And the set of all Free software is NOT a small scale system. It's HUGE, and attempting to manage it centrally, or even considering that it _can_ be managed centrally, is a waste of time.
That's not to say that cooperation should not be encouraged. However, cooperation cannot be enforced. And to have free software follow the rules that you would have it follow, would require enforced cooperation. That just doesn't work.
Your sarcastic hand waving does nothing to back up your point. It is entirely possible to focus software development efforts into making "the best solution" instead of aimlessly pouring effort into "100 different, equally crappy solutions". You just want to shake your head and pretend like it can't happen, simply because it doesn't happen in the world of Linux and OSS.
Yes, it's "possible", for the most expansive definition of possible. And if all the developers saw the light and decided to follow your suggestion, then it would be great. But to sit and wring our hands over "possibilities" missed because of simple facts of human nature accomplishes nothing.
-Laxitive
As opposed to a gigantically bloated "Platform" that's about as speedy as a quadrapalegic on ketamine? And where one business has a very strong interest in the platform, interests which can quickly lead to conflicts of interest which will make the whole thing drown in politics?
D looks like a good idea. I'd actually support that, the language is clean and straightforward. Although I don't know how open it is, but it was consciously designed, and doesn't have a VM or a religious mania about it so I think I like it already.
I want to be able to sort it manually or by group instead of by process ID. I want to be able to drag a taskbar item/window to my desktop switcher and have it show up there (instead of putting it on all windows, switching desktops, then putting it only on the second desktop). Kickstart
The possibility that what you're looking for isn't packaged.
... you have to know the name of the software first.
I can release a source tarball for a Win32 app too. Whose fault would this be exactly?
What? I was simply saying that it's stupid to assume that any piece of software you're looking for is packaged using the particular package format your distro uses.
And unless I'm mistaken, in most cases it's the responsibility of someone involved with the distro that does the packaging and includes it with the OS, not the person who originally wrote the software. That software isn't going to get on the APT repository by itself, you know. Someone involved with Debian has to put it there before your magical apt-get will install it.
That you know offhand what the package name is.
As opposed to Windows, where clairivoyance is built into the operating system...
I was saying that if you don't know the package name offhand, you're going to have to go searching for it, much like you would with Windows. This is the counter to fools who respond to everything with "apt-get <obscure package name>! It's so easy!"
Even on MacOS X that's not true. NeXTSTEP had a far more functional Installer.app which would install, uninstall, and archive packages based on the bill of materials (essentially a list of files that belonged to the package) and this was more useful than the current MacOS X strategy (except that the NS Installer didn't handle conflicts at all).
On MacOS X you can't be sure that a package's content are only in the .app directory because some apps are installed with an installer program that does who-knows-what to your system. Programs that come with the OS are not always desired and don't come with uninstallers (how does one properly uninstall Microsoft Internet Explorer and be sure that all of its parts are gone; how can we know all the parts are in the .app folder? Why can't the installer let you tell it what not to install if you are reinstalling the OS and you know you don't want some program?). Many MacOS X users commonly run their machines as administrative users where they have the ability to write to system directories. Therefore it's possible for a program to see that some file isn't installed somewhere else (like a system dir) and then place a file there. Also the .app directory grants virtually no dependency tracking (modulo that which is built into an application). If program A depends on program B and B is removed, there ought to be a complaint and some kind of extra effort required to break program A but none will occur. As a result, programmers are implicitly urged to not reuse code in this way.
Then there's the inconsistent uninstall procedure -- uninstalling the developer packages appears to have somehow messed up a friend's ability to use Software Update on his iBook running MacOS X. He was lucky there happened to be a Perl script to do this job in the first place -- the developer packages install a lot of stuff in a lot of different places. Software Update complained of a permissions error on a /tmp subdir it was trying to write to. A reinstall of the OS fixed this (and also forced making a backup of personal data which was needed anyhow, so this wasn't a complete waste of time) but it sure seemed like overkill. Depending on each program to supply its own uninstall seems problematic and unnecessary particularly when you have the installer "receipt" which lists what files belong to which package and you could let packagers run a pre- and post-uninstall script to do things that aren't strictly file-based.
Making all of this worse is that so many programs on MacOS X are non-free software; inspecting the program's source code to see what the program really does is not possible. In the end, I think Apple sacrificed a lot for perceived simplicity that ended up not being so simple after all. I think MacOS X has some important user interface improvements other systems would be wise to build upon, but this way of doing package management is not one of them.
As for making a printer (and, for that matter, a scanner) work, I prefer the approach I've used in Fedora Core GNU/Linux: plug in the USB printer and run the printer manager program wizard. The wizard could be improved to automatically sense the new printer and configure itself (or the desktop could do this), but no additional software was needed. Scanning was even easier for me with my Epson scanner -- plug in the USB scanner, start the scanner program, scan. OS X required additional non-free software to do both of these tasks and that means another dependency I have no ability to share, modify, or inspect. I'm not willing to give up my software freedom for user interface enhancements and I don't think I should have to. Looking at how things used to be, history suggests I don't have to either.
Digital Citizen
You bunch of jerks!
If i download an rpm and click on it with konqueror or nautilus, BOTH WILL run the appropriate visual installer application (kpackage or synapys or whatever) in ALL of the most popular distros.
What the FUCK are you guys talking about not having an installation standard. Redhat CAN and DOES install deb packages in a single click, debian CAN and DOES install rpm with a couple of clicks.
Geeze
Its been this way for four years !
NO SIG
URPMI, Apt-RPM, Apt-get, Portage, whatever that thing that slackware has now...
Anyways my point is that dependancy checking is handled automatically now.
Just a Tuna in the Sea of Life
The point is, I'm not the one asking for forced, artificial standardization. Where it occurs, and if it occurs for the right reasons, it is good.
But who decides which standardization is good? What are the right reasons? You, and I, and everybody else has their opinions on that.
This is the reason we delegate responsibility to self-organizing systems. And it seems to me that the Free Software system is reasonably well organized. It's well organized because most decisions happen through concensus. If there is a lack of concensus, then forks occur, or new projects are started. That's how the system works.
Forcing either artificial standardization, or artificial diversity, is a useless venture - especially in a system as loosely held together as the body of free software developers. For any given case, you might feel that two projects would serve a better purpose by coming together as one. But for other cases, you might feel that a project should be split into two to function effectively.
Arguing blindly for an overarching uniformity, however, is NOT the correct way of approaching things.
-Laxitive
That said, someone needs to write a simple app that associates itself with package files and puts up a Windows-like installer GUI. Aunt Tille doesn't want to 'apt-get install' anything.
It's hard to be religious when certain people are never incinerated by bolts of lightning.
Because it's very easy to expose a C api to practically any language in existence
Absolutely.
but very difficult to expose a C++ one to anything except C++, and in fact it's generally done by flattening the API to a C one
Are you sure that's still true? It was true the last time I checked, but doing a look around today, it seems that SWIG has become very good at wrapping C++ in anything from C# to Tcl.
And so forth, you're a Nazi...Godwin's law...end of thread.
I was simply saying that it's stupid to assume that any piece of software you're looking for is packaged using the particular package format your distro uses.
If you use a main-stream distro (RedHat, SuSE, Mandrake, Debian, Gentoo) then most software that your typical desktop user wants is going to be available packaged for your distro. My point is that anyone can write "app X" and release a tarball, but that anything mainstream isn't only available in that form.
That software isn't going to get on the APT repository by itself, you know.
Software I have written is in Debian, so yes, I know.
I was saying that if you don't know the package name offhand, you're going to have to go searching for it, much like you would with Windows.
You probably have one place to look though.
Do you even know anything about perl? -- AC Replying to Tom Christiansen post.
Anyways my point is that dependancy checking is handled automatically now.
Well that's not what I got out of it.
Even if that's the case, it is extreemly annoying for those of us that do not have broadband. For the vast majority of downloadable Windows applications, you just download it and install.
This is not always the case in the *nix world. If you download something that you believe is 20 MB on dial-up, it takes some time. It is very frustrating when you try to install it and find out that it has two dependencies which are also 20 MB. So what do you do here? Spend time downloading the two files and hope they don't require anything else?
I don't. I boot back into windows, download one file, install it and I am ready to go.
Not everything is analogous to cars. Car analogies rarely work.
is long term, this is highly important, a lot of people that want to do things like copy an image from the web browser and paste it into the word processor, etc, and it doesn't work. Having to save to a file and then insert from a file just isn't good enough.
Anyway: that is what I thought the ome of Gnome stood for.
Where's the list of applications - indexed by function?
That would be here.
NO TOUCH MONKEY!
Actually one could just run a scripted install. Many commercial packages work this way, like LokiGames. The old Star Office installer did this too. It can be and has been done.
If something is FOSS then it one can just let the Package maintainers for a particular Distro handle it though.
Just a Tuna in the Sea of Life
There is already a LSB v1.1 which has been created and it is included with redhat/fedora and several other distros which I can't remember off the top of my head. I know for a fact though debian is choosing not to adopt it. The main reason it is a challenge to adhere to these standards is that they have been doing things their own way for so long that it is a lot of work to change things. A prime example is rpms...several distros use rpms but due to package names and dependancies it can sometimes be almost impossible to install a fedora rpm on say suse. That is one of the problems with open software is that many users have different thoughts and opinions on how to do things. Personally I use fedora though and all the software I try and run and install works fine and I never have any problems with it.
Like minkwe said, get out of the Dark Ages ;-)
Seriously though, you're right. It's one of the problems that Gentoo solves - you can build a package with whatever options you want. One of my biggest frustrations was getting aspell and all sorts of other crap just to upgrade Gaim on Mandrake or SuSE. With Gentoo
will get you a nice stripped-down version of Gaim. Once Gentoo matures and someone builds a nice GUI on top of it, it'll be greatLOAD "SIG",8,1
From the roadmap post:
Does this mean I'll be able to search inside OpenOffice.org and Abiword documents for textual content through the Nautilus file finder? This would be very nice. A friend recently switched to using RTF documents so he could do this (OO.org documents are compressed and not easily searched from the Nautilus search panel).
I like how integrated Epiphany is into the GNOME functionality and how easy Epiphany is to use. I would not expect Mozilla Firefox to be so integrated into any desktop because it would decrease portability.
Is this going to be based on Coaster?
Digital Citizen
Pick two.
DNA just wants to be free...
Hmm..
* Blogging integration.
* Peer-to-peer data sharing.
* Metadata framework
- Possible implementations include Novell's Simias, GNOME
Storage
I'm thinking p2p blogging will result. Well, you gotta do something when solitaire gets dull..
1) Improve the task/panel bar. M$ has a much better one. Study theirs, and change GNome's. This is one of the most frequently used item, so as usability thing, 1st priority. Things such as resizable using the mouse to resize, fixed size icon, but variable size panel, icon arrange in the order of creation time, coloring of the selected/open icon and the minized icon must be easily identify, etc.
2) Add add/remove software management. This should be one tool that knows what's install, what's not, and how to remove/configure each one of them.
3) Improve the mouse software. M$ has a much better/smoother experience with a same mouse. This is the most frequently used device, please improve on this.
4) Double click on RPM to install/reconfigure, add uninstall infrastructure/standard so software makers follows
5) Easier way to manage the Menu. With M$, you open a folder, drop shortcut into it. You can right click and open the menu folder, etc.
6) Improve the file dialog/chooser. Double clicking on a file/folder many times edit the name of it. Lengthen this time much longer to distinguish between edit a name and double click/select. Add last directory button to the file dialog, so that clicking on it will go to the last time users use the dialog (regardless of application).
7) Many times, users have to use "su" to do things. Make this completely graphical, such as popup asking for this if needed.
8) All of the configurations must be able to do through GUI, including fixing misconfigured computer.
9) Instead of having user's settings under user home's hidden folders, all of those should be under user home's "Settings" or "Preference" folder/sub folder. (this is a standard thing, because it's the software, not GNome do this, but GNome should set the standard, and api for getting this (such as : GetUserSettingDir())
10) Create/edit short cut, start in location, running under different users should be easy and GUI.
11. Delete files from Floppy should put it somewhere un the trash inside the floppy that can be empty, not just make it hidden, and the floppy still is full.(this could be a bug though).
i don't like nautilis, in the three years thats its sitting here on my desktop i barely used it twice, but it crashes on me every day, not to mention the very strange (and backward?) shape it took up in gnome 2.6. gnome could lose that file selector to, i miss bash-style auto-completion. what i really miss from gnome 1.x is the control center that had all of the preferences applets under it. and there were alot more preferences to choose from. especially window manager preferences, metacity barely leaves you any tweaking, not even in g-conf. one good thing i could say about gnome today is the configurable international keyboard they added.
Anymore you select the package and let the package manager download it and the dependncies. For instance with Mandrake and urpmi:
urpmi foo
To satisfy dependancies package bar and bar2 must be installed Ok to proceed Y/n?
It then proceeds to download, and install or upgrade as needed.
Just a Tuna in the Sea of Life
* A gnome-terminal that can open multiple windows without requiring multiple processes.
* Faster startup time and lower memory usage for GNOME applications.
* A GUI method of enabling emacs keymappings and user-rebindable accelerators.
* User-rebindable accelerators on contextual menus, rather than just regular menus.
* OpenOffice working like the rest of the GNOME applications.
* All config directories (dotfiles and dotdirectories) being moved from ~/.appdir to ~/.config/appdir (including gnome/gnome2 stuff. Less garbage in ~/.
* More types of data being supported in cut-and-paste in GNOME apps. This means being able to cut-and-paste from the GIMP or Inkscape to Open Office and back again.
* The introduction of an "infinite progress bar" widget containing barber pole stripes, a la the Mac OS, to be used on tasks with an indeterminate completion time.
* The finishing of *some* instant messaging client for *some* protocols. All of the GNOME-based IM clients have issues. This is mentioned in the roadmap. IM is a standard feature even at many businesses. To use GNOME, I need to be able to send/recieve files with it and send encrypted messages. This is currently a tremendous pain in the ass (for some reason, encryption support *still* has not been merged into gaim mainstream, despite the fact that the US no longer places encryption limitations on people).
* Security. The GNOME people are busily putting in auto-discovery stuff and the like. If GNOME talks to the network, it needs to be tied down very tightly. I get *very* unhappy when my desktop environment needs to talk to the network.
* Network management. GNOME's GxSNMP is currently dead, and there are no GNOME network management apps. There is nothing like Intermapper.
* Make a GnomeTreeView that's a more intelligent GtkTreeView. It should natively have the ability to reorder or hide columns (say, a popup menu can come up from clicking in an icon in the title line of the GnomeTreeView that has a checkmarked list of columns to make visible) -- this sort of functionality shouldn't really require the application to do anything.
May we never see th
Uhm no. Only Microsoft and Apple themselves are involved in the development of their own OS. Third parties make third party apps, that's all.
And there *are* duplicated effords in the Windows world. How many Win32 text editors do you think exist? How many Win32 HTML editors? How many Win32 firewalls? How many Win32 virus scanners? How many Win32 image editors? Etc. etc. etc.
In other words: no, it doesn't happen in the commercial world.
That's only assuming all those people will actually work on the same single project. If you kill off GNOME there's no guarantee all GNOME developers will work on KDE. I wouldn't be surprised if lots of them just quit programming entirely.
Not to mention that if you download a third-party/proprietary app, it is likely to be binary-only and statically compiled, or at least only depend on glibc.
still do
love it
don't think it should be the language of choice for the majority of development
there are times when it has to be done in assembler
but generally if you can do it in something else, you probably should
Of course the core libraries, and the apps too, would all be a lot less leaky and crashy if they were actually written in C++, but superstition rules all.
So what you're really saying is that Linux (GNU/Linux/KDE/GNOME/Etc.) is a system designed by a committee of camels?
Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
You understand the reason for this, don't you? It's because Windows `install bundles' include every single library etc they will use. This is a simple method, but it is hugely problematic:
The Windows installer stuff is a seriously horrible ball of hair; that it works at all is more a testament to the sweat lavished on it than any inherent merit.
We live, as we dream -- alone....
Here is a sample of how it looks: Check under code listing 2
it's cool to see what packages there are. You can also do emerge search nameofpackage
Of course, if you have no idea what you want to install, then it is no better or worse than any other install method.
Gnome feels slow.
Gnome panel has a pathetic autohide (which feels slow too).
Gaim is not good (mainly because of it's GUI). Kopete all the way...
Gedit is way behind. GTKSourceView has weak syntax highlighting.
By the way, I have both Gnome and KDE installed and switch between them often.
I know you are psychotic, but please make an effort.
Exactly--once you make your choice, the road is clear. Why do so many people point to the profusion of distros and assume that each company will have to manage among at least several of them? They just have to figure out the _one_ distro they're going to use. And it really should be Slack, BTW.
Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
Hopefully trollback has seen this comment. You really riled up the fanboys.
Jesus was all right but his disciples were thick and ordinary. -John Lennon
From a written works author's perspective, nothing more frustrating than finding out that the GNOME people insisted on adopting a spellchecker framework for which hardly any dictionary is available outside the realms of the English language. Please dump that aspell crap and apply the MySpell/OpenOffice spellchecking infrastructure across the board ASAP!
Software is not supposed to be about how to work around a useability issue. - Ken Barber
It is entirely possible to focus software development efforts into making "the best solution" instead of aimlessly pouring effort into "100 different, equally crappy solutions".
But you're forgeting that each of those 100 different solutions is best for 100+ different types of people. FOSS allows that fragmentation. Commercial software needs to take the "shotgun" approach. Throw a bunch of features and hope some of them hit. FOSS takes the the "sniper" approach. Choose the right caliber bullet and aim for the kill zone. The analogy even carries over to availablity. There are a handful of shotgun gauges available while a large selection of caliber for rifles.
Wow, I'm sounding like ESR now.
That's just stupid. Linux is ready for the desktop when companies can happily develop programs for it, just like they do for Windows (and Macs). When they can have 2 folders on the CD that they sell, one labelled Windows, and one labelled Linux. Inside the Windows folder, you have install.msi. Inside the Linux one, right now, you have...
1) install.rpm
2) install.deb
3) install.tgz
4) install. no_space_left_on_CD...???
We need a unified install mechanism, which, I believe, is where http://autopackage.org/ comes in. Believe me, we need it.
Most distros, including all significantly large ones, adhere to the most important part of the LSB: The filesystem hierarchy standard. As for the rest of the standard, it varies. Adoption of the LSB is not that bad, actually, even if people aren't talking about the LSB left and right.
If at first you don't succeed, skydiving is not for you
I've always thought that a GNOME equivalent to ActiveScript would prove useful. Imagine adding scripting capabilities to your application and allowing the user to choose whether they want to use ECMAScript, Ruby, Python, Perl or *gasp* VBScript.
Hmm...anyone know if this already exists for GNOME?
Your courageous and selfless spelling corrections have made me a better person.
> You know what I'd like to see? Real virtual desktops. The current "virtual desktops" are
:0 and another on :1. Then, you can hit CTRL+ALT+F7 to get to the first desktop and CTRL+ALT+F8 to get to the second desktop. And you could probably add an icon that binds to that key combination or does something else to switch to the other desktop. And you could have KDE in one and GNOME in the other, or you could have two XFce desktops (though they'd probably have to be under two separate users, though not necessarily).
> really just virtual screens, not desktops. Full virtual desktops should act as completely
> separate desktops, with their own set of icons, etc. Obviously this would not be for
> everyone, but I would love to see it as a user-selectable option.
Well, you can kind of do that my editing inittab (or placing an extra xinit entry somewhere in your startup scripts) so that it starts up multiple X sessions. Let's say, one desktop on
There are perhaps problems with this approach (for instance, switching from one vterm to another could take a second or three, and that's annoying if you want instant switching), but it is essentially what you're asking for.
For what it's worth, KDE supports Mac-style menu bars. This works for any KDE app and probably most Qt apps (with the Opera web browser, it works, but you have to tell Opera to hide its menu bar or you see the menu bar in both places). Also, KDE remembers which desktop you asked a program to load in. Not that I'm evangelizing or anything....
--
-JC
FreeDominion, a WIP Civ clone
http://www.jc-news.com/coding/freedom/
when will it sucking ?
As opposed to that childish "Windows has to do everything that anyone or any company on the planet could want it to do, and then some" attitude that plagues Microsoft?
I think you're completely missing the point of what's going on in Libre-Desktop Land. GNOME isn't a monstrous application which does everything everyone could want, whose responsibility is the administration of a software system. The current focus is on the model. Gnome can't do all these marvelous things. Gnome can enable all these marvelous things, and then someone goes out and writes a 500 line program to demonstrate it.
Observe the focus on freedesktop.org. They're working on making the design of GNOME communicate with D-BUS. The killer feature of Gnome 2.x is GCONF. They're working out the communications layers of the system. What you COULD do with Gnome is breathtaking at this point. What you COULD do with D-BUS in Gnome 2.8 will be even more so.
So, why can't you yet? Two reasons. First of all, there aren't quite as many developers as in the Windows world, simply due to relative scale. Secondly, the Gnome developers are thinking this through. I mean, they're really thinking this through. Here's an example:
Do you see a Clipboard Viewer yet? No. You won't. The Clipboard Viewer circa Windows 3.1 was a hack to give you access to a feature that hadn't been fully fleshed out. I had to use the clipboard viewer in Windows 3.1. It just didn't work completely right. Drag and drop was a joke, and a major feature of Windows 95 that turned into a gimick for demos of Office 95 that never really worked right, and were stripped out prior to shipping.
There have been very long and surprisingly interesting conversations about the idea of a clipboard, and exactly what it's supposed to accomplish, and what exactly it should do, and especially how. For example, if you copy some data from within an application, and close the application, what happens? What is the status of your copy?
Let me start with something else. Let's say you copy a bit of styled text, with bolds and underlines. Now, you want to paste it into an application that only understands plain text. Should you be denied? Quietly? Loudly? Gnome developers feel you shouldn't be. It's text. You should be able to paste it. The thing is, you can't just go duplicating any bit of data that happens to be selected as "copied". What happens is that when you paste, the application you copied things from has a list of data formats it can export some bit of data out as, and it tries to match the best choice with the application's acceptable list. If you paste that rich text into a hypothetical program that only accepts text/html, it could get converted to HTML 4.0 Transitional.
They're working things like this out. You don't see much of it on top of things. They're doing things like GStreamer, which isn't a program, but there's a program called GStreamer which uses GStreamer. They are, as you contradicted, working out standards. Where applicable, they're working with freedesktop.org to develop and impliment those standards. One day in the not too distant future, you'll probably see Apple, and then Microsoft, announcing support for the industry standard D-BUS Interface, or some such.
I'm as mimsy as the next borogove but your mome raths are completely outgrabe.
Actually, I believe KDE has something like this.. I just tried opening a konq window and switching, and it opened in another window. What I also like about KDE, is that if you use the KGestures thingy and make it open a new tab for a gesture, the command opens a tab on a window on the current virtual desktop (if any), otherwise, it just opens a new window. Funky stuff.
Plus, the Slicker project (which seems to have been abandoned) is an interesting concept. Screenshot. Although the damn thing compiled and ran, I got nothing to show up. Clues?
Founder of Mirror Moon - Tsukihime Game Trans
It's very lightweight. I use it on machines with 32MiB RAM or less (like my laptop).
If you use ssh X forwarding, you can start a gnome panel remotely and you've nearly got a gnome desktop.
Although, you don't want to start nautilus... only thing that doesn't really work in this scenario is the workspace changer. You can do remote gnome panels + working workspace changer with XFCE though.
There are some things about GNOME development that strike me as falling short in comparison to the KDE team, but I could never prefer KDE over GNOME on the basis of looks alone. KDE seems to start out taxing on the eyes and then stays that way (for me).
I think it was FA Hayek who said that people hate freedom/capitalism because they are forced to choose, they are forced to make tradeoffs. Summarily, communism is attractive because these people BELIEVE that these tradeoffs somehow magically disappear because they aren't the ones doing the choosing anymore. Basically, it's appealing to a certain psycological mindset that we have to want things simpler. The morlocks and eloi as it were.
----- Question authority, but not ours. Hate the man, but we're not him.
Dude, I don't want my particular installation to end up anything like your vision of a linux desktop. I don't want "uninstall links" embedded in an application launching menu. I don't want programs launched behind my back to "save" 7 seconds. I don't want to fumble with cdroms that contain outdated drivers when I can automagically install them off the net in the first place.
Shouldn't that be up to the distributer? You really don't need to install the entire GNOME Desktop to have functional "GNOME". Gentoo has a light version of GNOME that only includes basics:
metacity-2.8, gnome-session-2.6, eel-2.6, nautilus-2.6, gnome-terminal-2.6, control-center-2.6.0.3, yelp-2.6, gnome-mime-data-2.4.1, shared-mime-info-0.14, gnome-vfs-2.6, gtk+-2.4.0-r1, pango-1.4, atk-1.6, glib-2.4, gconf-2.6, gnome-panel-2.6, gnome-desktop-2.6.0.1, libbonobo-2.6, libbonoboui-2.6, libgnome-2.6, libgnomecanvas-2.6, libgnomeui-2.6, librsvg-2.6.4, libglade-2.3.6, libwnck-2.4.0.1-r1, ORBit2-2.10, gnome-icon-theme-1.2, gnome-themes-2.6
Doesn't come with a blogger, or a media player or anything!
Java VM is just too slow
Well I would assume that the code would be written in java, but compiled into native machine-code by GCJ or something and run at native speed.
From what I understand, you don't need a JVM to run java apps that have been compiled into machine code, just for java apps that were compiled into Java bytecode.
I also remember hearing something about how when this is done the speed difference is negligible compared to other languages.
"Sometimes, I think Trent just needs a cup of hot chocolate and a blankie." -Tori Amos on Nine Inch Nails
unknown command 'apt'
Michael J. Ryan - tracker1.info
This is exactly why commercial vendors are picking one or two vendors of linux to support, most of them being behind RedHat or SuSE, one gnome, one kde based... Okay, this leaves us with GTK+, and QT for primary gui interfaces... now, if we could get at least most distros to agree on a "default" install that will have libraries x, y, and z, so that they can be programmed against.. something akin to the windows api, and direct-x... pretty close with kde or gnome with opengl, but linux audio support falls short every time I try a few different distros... graphics isn't much better... if there were at least some core libraries that an author can *count on* to be there, and where it belongs, or at least in a means of being able to find them, this would be a great start.. now add in a higher level platform like java and/or mono, and there you go... if LSB, or whoever would make a concentrated effort to make this area rock solid, could still use any number of things above this for your specific solution... you can replace explorer as your desktop interface in windows, and programs generally still work... because the core apis are established, this isn't even 50% true in linux. that is the problem..
/rant
Michael J. Ryan - tracker1.info
It's a set of programs that run on versions of unix guys - systems that are multiuser, where everything is a file, where you have pipes and sockets and don't need to re-implement weird windows style OLE stuff that didn't work properly on windows for the first six years anyway.
Gnome became popular because it was good when they focused on code instead of politics, but now they are going all political again aiming to make a better MS Windows than Microsoft.
What I would like to see on gnome is either plain text configuration files, or a configuration database that is actually accessable, old *nix traditon of providing man pages (or info if you really have an emacs agenda to push) and a documentation web page that does more than list that a ceratin person wrote documentation on a certain date (actually letting people read it would be nice). Several packages have been abandoned as being complete while still having major flaws, like gdm needing root intervention to delete files to get X going again if a session of X crashes or a user presses CTRL ALT BACKSPACE to get out of X. Gnome is big, so they are not bothering to maintain it all - join mailing lists on moribund projects like gdm if you don't beleive me.
There are a lot of good things about gnome, but some things do not appear to be done well, and the whole obfiscated MS windows registry style thing should have been finished before things like gnome-panel used it. Years after it's introduction you still can't migrate to panel settings of one user to another. It's a multiuser system guys, and a "filesystem" is not a collection of pictures, it's how the operating system gets things off the disk - didn't the leading lights of gnome pay attention in the indroductory CS class that engineers take for easy credit?
no, inside the Linux one you have an install shell script and the stuff you want installed; this is no more difficult than using a .msi
PLEASE get some genius programmers working on a fork of Gnome and remove 70% of the cruft? or they can do KDE... I dont care...
Wow, I wish I had mod point to mod this up.
It's really painful to have to use the crippled components they keep building into the window manager instead of special purpose apps that do one thing and do it well. The damn desktop-file-browser-thingies should be the first thing to go.
ok smaller and better...
because smaller equates faster no matter how you look at it.
examples? Sure, palm OS...
better than anything microsoft has conjured, massively smaller than the competition and is certianly faster as it runs perfectly on a really slow processor.
if we cant do as good as palm OS then as open source programmers we all suck really freaking bad.
I frankly don't see the point in the unix style "binaries in this folder, config files in this one, data in this one" thing. I like the c:\program files\nameofprogram and "My Documents" way of handling things. That'll never change in unix land, but it sure is nice.
/opt/nameofprogram
"My Documents" = ${HOME}/
"c:\program files\nameofprogram" =
Granted, your home directory in Windows contains much more than just the "My Documents" folder, but the rest is essentially what you get in hidden files and directories (~/.foo) in Linux. Also, if you'll look inside your "c:\program files\nameofprogram" directories in Windows, you'll often find that they have binaries in one subdirectory, config files in another, and data in another. Sometimes they mix and match, and sometimes they just dump it all together, but often it looks a lot like a "/opt/nameofprogram" directory tree in Linux.
Esound requires too much manual fiddling to get working accross networked applications, while NAS was designed with exactly that in mind. NAS also happens to be supported out-of-the-box by several X terminal devices made by HP, NCD, etc.
Software is not supposed to be about how to work around a useability issue. - Ken Barber
Its very important that the GNOME community develops a elegant framework for developers, so that normal developers can design applications for GNOME. Currently, the framework is difficult to understand with documentation adding to the woes.
The community should focus more on Ajunta, and make it a superior IDE like Visual Studio.Net.
If people can build simple GNOME applications using Wizards, something like with Visual Basic.. it will give a great boost to the environment.
Java may be promoted for development because already there is an established army of Java developers... GCJ can be to avoid java speed-pitfalls... so a java subset may be used.
In short, the focus should be on developers...we need a compiled and interpereted language for
the environment... Java and Perl are good contenders.