But really, the core of the issue that's been raised by Unity is that Ubuntu seems to be moving away from catering to power users to cutting features essential to them in favor of appealing to more amateur users. One can lament that decision, and even disagree with it, but I don't know how fair I think it is to criticize Unity for lacking those kind of power user features.
After all, it isn't like power users are exactly wanting when it comes to replacement options in the Linux space.
* When a maximized window is behind an active non-maximized window, the panel serves as its title bar. But it actually spells out the name of the active window. Very confusing.
* Additionally, in the same situation, all of they standard mouse gestures on the panel (e.g: double-click to unmaximize) do not work. Maximized windows don't get the right-click-title gesture to work at all.
* No window list at a glance (useful for remembering your context/state with the UI)
* Hides important buttons such as close window, as well as the menus, where non-power-users will not know to look.
* Panel unhide takes a relatively long time -- slowing down almost every interaction with the UI.
* Workspace switcher does not support window drag, unlike the gnome panel workspace applets.
* Workspace switcher requires multiple selections to switch to a window.
* Alt-tab switches applications, not windows, which is more confusing, as it associates unrelated windows together, as if the mere fact they're implemented by a certain application necessarily means they relate. This also requires more keystrokes to reach the window you want -- when you don't have many of them in a workspace, which is a typical situation for organized users that actually use workspaces.
I could go on and on. Unity is an immature, alpha-quality piece of work that seems to have been thrown out because of a deadline.
Usually in open source, real user feedback is better than guessing.
I think Unity is maturing and will grow to be what really draws new users to Ubuntu.
Keep in mind what has already been said, Ubuntu is not really geared towards power users (plenty other distros for that), its early motto was "Linux for human beings", and also bug #1 is "Microsoft has majority share on desktop".
I'm pretty much enjoying this new direction and it's not keeping me from doing anything I need to, be it programming or browsing.
Since it's new, I also understand that there will be lots of set backs if I want go around tweaking everything, but that will stabilize with time and I'm sure that Canonical will appreciate any feedback from users that do want to experiment.
Also, I think it's pretty unreasonable to expect them to realease something new that will entirely support every other tweak and customization made with the old features.
Certainly. But that doesn't mean it is a good idea to push unfinished stuff as default. Though maybe that is the only way to get people who aren't technology enthusiasts to try the new thing and provide feedback.
Any links? I've found a few results from months ago, but results/feedback there weren't so positive.
If this was an attempt to be Mac-like, then it was pure cargo-cult UI design. They clearly have no understanding of the actual design process.
The last Linux desktop environment I was reasonably happy with was KDE 2.x. I tolerated 3.x.
> When a maximized window is behind an active non-maximized window, the panel serves as its title bar. But it actually spells out the name of the active window. Very confusing.
This just doesn't happen in OS X that I've ever observed. It's in fundamental conflict with the OS X window management paradigm.
> Additionally, in the same situation, all of they standard mouse gestures on the panel (e.g: double-click to unmaximize) do not work. Maximized windows don't get the right-click-title gesture to work at all.
Again, this is just inapplicable to OS X.
> No window list at a glance (useful for remembering your context/state with the UI)
This is true for OS X, as far as it goes, but OS X UI practices seem to make it less of an issue than it would be on Windows or a typical Linux desktop environment.
> Hides important buttons such as close window, as well as the menus, where non-power-users will not know to look.
I'm not even sure what this one is about. It seems inapplicable to both Unity and OS X.
> Panel unhide takes a relatively long time -- slowing down almost every interaction with the UI.
Hiding off by default in OS X, quite fast to unhide.
> Workspace switcher does not support window drag, unlike the gnome panel workspace applets.
OS X supports this fully.
> Workspace switcher requires multiple selections to switch to a window.
Not true of OS X.
> Alt-tab switches applications, not windows
True of OS X.
8 properties total, 1 I can't make sense of, 2 that are more or less shared. If my post was hyperbole, the one I responded to claiming "many" of these were shared with OS X was, too.
Just a minor note, I just upgraded to 11.10 today. This seems to work correctly now.
It has a few bugs (e.g. try opening two terminals, then alt-tabbing... it doesn't switch applications), but it's definitely a step in the right direction IMO.
If that was really the case then Linux would be everywhere in the desktop by now.
Try the same line of argument in a different context:
"Our television ad campaign is responsible for almost the entirety of our increase in market share."
"Impossible! If that were true, we would have 100% market share!"
Except configuration is being hidden in binary blobs! And "The Ubuntu Way" seems to be being forced on "power users".
It's a great shame. Linux does need an easy to use OS, and Ubuntu has filled that role for a while now, and will continue to do so. But the great thing about Ubuntu was that power users could use it as well. Now some people are going to migrate to other distributions (debian for power users, mint for people who dislike the idea of an "easy to use, linux for newbies").
Ubuntu has almost always acted as a stepping stone for people to come learn Linux and then graduate to a real distribution. There have always been reason for power users to be put off, even back when Ubuntu was just an ancient african word meaning "I can't configure Debian". Are you saying that by putting those issues in the GUI it alienates them too soon?
Shouldn’t Gnome 3 instead have been a spin-off or separate project from traditional Gnome?
The Gnome project just decided that it was time to try and make a desktop that wasn't based on the Windows 95 (and up) desktop metaphor, and the only way that was going to work was to commit completely to that goal.
If user contributions are part of your business model you should also try to appeal to those users that are capable of delivering contributions.
I disagree. Enlightenment has been doing this from the start because it is faster to read and write than a specially formatted ASCII file and because the user is expected to do all configuration through the graphical interface.
antithetical to the kinds of philosophies that undergird Linux
This somewhat true but I believe editing text files by hand is the type of thing Ubuntu is trying to move away from.
ESR is an old hat who has been using Linux since way back in the day and is set in his ways. I am too, but he should know Ubuntu isn't for him. They are focused on ease of use for new users, not accommodating all the idiosyncrasies of the old ones.
- I've got a multitude of tools to choose from to evaluate and modify the files (editors, search tools, scripted modification, etc.).
- I can see with my own eyes what the contents of the file are, and generally, what is wrong. GNOME went the wrong way on this a long time ago by allowing non-intelligible values within gconf, a'la Microsoft's Registry.
- I can make atomic edits and deletes to/from the file (add/remove a line). I can carry those atomic edits around with me (configuration bag of tricks).
- I CAN COMMENT THE MOTHERLOVIN FILE TO EXPLAIN WHY THE FUCK I PUT (OR REMOVED) A SPECIFIC VALUE. Configuration files are NOT there for the convenience of the computer / interpreter / system they are managing, they are there for the administrators to understand what is configured and why.
Removing the ability to comment files, or to make atomic updates in a commented system (e.g: git) removes a core value of configuration management.
Yes, GNOME jumped the shark, but it happened years and years ago.
gsetttings list-recursively > gsettings-all.txt
for line in $(cat gsettings-all.txt); do gsettings set $line; done
gsettings list-recursively | wc
gsettings list-recursively | gzip -9c | wc -c
$ gsettings list-recursively | wc
1037 3367 56466
$ gsettings list-recursively | gzip -9c | wc -c
$ gsettings list-schemas | wc -l
The issue I'm trying to understand is exactly how the fuck it is so fucking slow to parse 56 fucking kilobytes of text at session login time that it justifies encrypting my fucking desktop settings in a fucking binary configuration file.
I thought maybe the default configuration had ten megabytes of shit in it or something, which could conceivably sort of explain it, although then that would be another fucking stupid decision that would require explanation. But 56 fucking kilobytes? Which gzip suggests would be 35 kilobytes with a human-oriented syntax?
Give me a fucking break.
As someone else has put it in other thread sequential reading is fast. Random reading from 50+ files which involves seeking the disk is not.
Of course the gconf configuration may have had other alternatively smart ways of doing things and gsettings authors are just optimizing where it is easy to do.
And by the way the gconf stuff is still necessary
sudo apt-get remove gconf2
How many milliseconds does it take to parse YAML, XML, or any other file format for which a parser written in C is widely available?
> the user is expected to do all configuration through the graphical interface.
Changing configurations using the GUI is exactly what Unity and GNOME 3 don't allow the user to do. Try changing anything other than the desktop background.
YAML and XML may be slower than this, but Python 2.6's built-in 'json' module averages less than 20 milliseconds to parse a simple 1000-element "object"/dict on my system.
This isn't even the highest-performance JSON parser for Python, and parsing into less dynamic C or C++ datastructures would probably be somewhat faster still.
Either way, the principle stands. If a desktop environment wanted to standardize on JSON + C/C++-style comments, they could extend their standard parser easily enough without meaningful performance impact.
There are a number of standardized binary formats that support all sorts of data configurations. Hell, use sqlite for all I care, but at least use a format that can easily be examined and manipulated manually when the UI inevitably breaks it.
I try to use the mouse only when necessary (even when browsing the web), and I like to launch my applications through text search. Actually I don't need the Unity sidebar at all, unless perhaps when I want to see what hidden apps are running. I arrange my windows using ctrl-alt + numpad and I switch between workspaces with ctrl-alt + arrow keys. The new active window switching with alt-tab and alt-shift-arrow keys is nice. All in all I'm happy with Unity and it got better with 11.10. Being 50% on Ubuntu and 50% on OSX I have to say that I wish OSX had a little bit more of Ubuntu-UI in it.
Just writing this to offer a counter-point to all the anti-Unity posting. Perhaps everyone should try to play around with Unity shortcuts and see if it's really that bad.
Here's a post detailing some of them: http://blog.sudobits.com/2011/09/04/ubuntu-11-10-oneiric-oce...
Which works pretty well... until you realize that these desktop environments are also pretending to target the tablet market, where text entry is an order of magnitude less convenient than it is on a regular computer.
that's why you have large-ish icons for frequently used applications and why you can pin them to the launcher bar.
I doubt that the text-search paradigm is the right way to go about developing a tablet UI of the kind that we need. Anything based on mouse clicks would seem to be a much better starting point for the transition to tablets. Unfortunately, both Unity and GNOME 3 require a lot of clicks to get around, which is equal to a lot of screen-tapping on a tablet.
In Ubuntu, neither Unity nor GNOME 3 have any desktop icons by default. Unity at least has a dock on the left, but GNOME 3 requires you to click "Activities" before you can do anything else.
In both, the only way to have desktop icons is by changing an obscure setting in an application that isn't installed by default.
Unity's dash is also far from a "grid of icons". You need to open the dash, click the "more apps" button, and finally click a relatively small target at the top of the list before you can see all of your installed apps in a grid.
In tweaking a few compiz settings, through their config GUI, I managed to crash compiz hard enough to need to reboot several times.
Unity itself is incompatible with Desktop Cube for some reason, and trying to force it just breaks everything. (I like Desktop because it seems to be a more reliable desktop switcher, anecdotally.) I don't mean "force it" like changing the config directly. I mean "force it" like pressing the button that asks if I really want to activate it.
So I tried out Gnome 3 for the first time. It tries so hard to LOOK like OS X, yet it winds up being way worse than either OS X or Gnome 2.
Maybe I'll try Kubuntu. Or Linux Mint. Or just keep trying to like this new crap. I don't know.
If you still like or prefer Ubuntu's system administration style (apt, packages, PPA, whatever), and you're just horrified by the desktop, then use another desktop or window manager.
- Lubuntu (LXDE on Ubuntu, similar to Xubuntu)
- LXDE and OpenBox manually installed.
- OpenBox by itself manually installed.
- XFCE manually installed.
Or go upstream to Debian, or downstream to Mint, or over a branch with Crunchbang. Or a stream over to an RPM based distro. Or over into the next valley with Arch, Slack, etc. Get some strange with FreeBSD.
If the mainstream Ubuntu desktop sucks for you (it does for me), then moving some small or large distance to fix it is going to be much easier than suffering day in and day out.
Once you settle on one, you maybe want to start over with a backup and a fresh install.
sudo apt-get install xfce4
sudo apt-get install xubuntu-desktop xfce4
I just checked my command history, and that is exactly what I ran. Install xfce4, log out and log back in with the new WM, and everything just worked.
I'm pretty sure the Desktop Cube can be made to work seamlessly with Unity. But it's not Canonical's job to make it so. And if Canonical somehow managed to lock some of the desktop features into Unity, than we must simply pressure then into building something more flexible so as to allow other open source providers to work with a more pluggable interface.
And then another very short matter of time before it is non-functional again, since the then-current generation of developers will want to "build something new".
I wasn't messing with my X configuration or any other insanities. I clicked a button in the settings, and had to Google around just to get back to a working computer.
What other landmines are waiting for me? What if I install KDevelop or some other KDE-based program? Will that cause everything to break too? I don't know, but I never before had to be afraid to just try things. Now I have to worry if whatever I'm doing is "Canonical-approved," and I'm not okay with that.
(I really doubt KDE is going to cause a problem, it was just an example.)
For the record, I played with Gnome 3 a little more, and I'm willing to give it a longer chance. Avant Window Navigator is a must, though.
Overall, it just seems like Gnome 3 and Unity have all of my least favorite parts of OS X jammed into it for no good reason.
I'm actually quite surprised more people haven't spoken out against Metro in the new Windows for the same reason; that interface looks dreadful to use with a mouse. I've been told that Microsoft at least left in a "classic" interface that holds true to the name. If that's true, Canonical needs to take that page from their book...
As a user, nothing about Gnome was broken for me. But in switching to Unity, now Ubuntu feels a lot less useful to me.
Fully agree about the config hell, though. One time I wanted to back up my gnome terminal profile settings using gconftool, to discover that the terminal settings are stored in the middle of an XML file that covers a whole slew of gnome settings. So to do the backup/restore, I would either have to back up all of my gnome settings, or write a custom script to patch just the section of the XML file I need changed.
I'm fed up with Ubuntu pushing alpha-quality releases on users to get free testing. It's making Linux look bad. A couple years ago, Ubuntu was Debian that "just works" on the desktop. That's all I ever wanted, and I think I've found it again in Linux Mint Debian Edition.
Back in 2006 I made the move to Ubuntu from Gentoo because I was tired of constantly tweaking things to make my system work. Ubuntu ushered in an era of Linux ease that nobody before them had, and as far as I'm concerned, nobody has since. Sadly, they've started to muck that all up. I don't see anyone else out there making a distro that "just works" and has the out-of-the-box functionality Ubuntu does either, which is the most upsetting part for me.
I'm all for sane defaults and making design decisions and keeping options away from the users - not having huge preference panes. But keep a hand-editable text configuration file.
I spent some time using IceWM (shipped with EEEpc 701) and the jwm. So I guess I'd be using jwm again.
Next do you get to 'binary blobs for code should be considered evil', have a LISPiphany and found Symbolics?
When I first used Gnome 3 (back when it was first released) I hated it; it was buggy and the whole concept of gnome-shell seemed flawed. Now its seems many of the bugs have been worked out and the usability improvements of gnome-shell is starting to show. Gnome 3 is still far from perfect and there are still A LOT of things missing that I had grown to rely on from classic Gnome (like being able to arrange my panels) but Gnome 3 seems to be progressing and I have high hopes for its future.
I am less hopeful for the future of Unity frankly because it has so many bad ideas built in to it. One such bad idea is the heavy reliance on hidden elements that need to be hovered over for them to be visible.
Personally I think Ubuntu would do well to pick up Gnome 3 and run with it instead of Unity.
Kubuntu is great, although a lot of people who say that seem to eventually settle on XFCE anyway.
Then I remembered the original reason I started using Linux, as a native Windows user, and that is "Choice". So you don't like Gnome. Guess what? Don't use it! You have so many other choices of window managers available to you.
Shed a tear for those users on proprietary systems who don't have choice. Don't like the new Start menu? Nobody cares.
Also, maybe since all the power-users are so dissatisfied, they could join and manage a new packaged Ubuntu, maybe OUBUNTU (old ubuntu). They have that choice.
I for one am happy to have a linux distro geared towards everyday desktop use and modern devices, and that I can show my family/friends as an alternative choice and have them not reply that it's just so damn ugly.
I'm generally a fan of text-based configuration files but in this case I think the benefit exceeds the cost. Reading configuration used to take a non-trivial amount of time on startup.
Best of both worlds: rapid parsing / memory management (really, does it matter that much), while preserving human management.
Oh yeah: and the textual version is definitive.
One way out would be to compile the text-based config files into the config blob and rebuild the blob if the text-based config files change.
I can't quite figure out an attack vector, but I always have a bad feeling when I trust a binary blob and load it into memory without any parsing.
The middle ground would be to cache settings in a binary file.
Now, if your configuration file is textual, power users will want to edit it by hand. Look at the rest of this thread for evidence. This means that your application needs to be (more) robust in the face of errors in the configuration file syntax. Not insurmountable, but it's a bit more work. It would be good if your application recognises when the configuration file has been altered too, and reread the configuration so people don't have to restart the application.
Power users will also want to version control the configuration file, and compare different revisions to see what has changed. This means that when you write out the configuration file you need to preserve the textual structure and ordering of the elements from when you read it in. The power user reordered the settings to group things in away they consider more logical? Your configuration file editor needs to preserve that.
Most plain text configuration file formats also have some way of adding comments, and you'll need to preserve that. Oh, and all that whitespace that's not significant to your program but is significant to your typical power user.
So the problem is pretty much comparable with building a syntax-aware text editor for programming languages. There was loads of research done on those (Google 'syntax directed editor') and their success can be measured by the fact that lots of programmers still choose vim, emacs, textmate and other plain text editors precisely because they don't try to do anything clever with your text. Eclipse and similar IDEs are probably the closest you get to a syntax directed editor these days, and they've still stuck to the plain text editor user interface.
More sophisticated attempts to round-trip from program source code to editable UML diagrams or GUI layouts and back are routinely laughed at by the power users that you're hoping to win over with your clever plain text configuration file system, so don't think they'll be an easy audience to please either...
As for the old schema, there were two options separate xml files in a directory per-app and a big consolidated xml file. There were some measuring showing that the second variant which was opening just a file and not 50 was a lot faster and considerably reduced startup times.
But now if you are going to put everything in a big pile of xml where it is hard to find and edit/remove/add options without a specialized tool you can as well use a binary format.
At least, that's my reconstruction of events.
How about making opening the 50 or so files fast instead of putting everything into one big file and, then, into one smaller blob?
Or we actually do like to make the same mistakes Microsoft does?
Sometimes pathological problems result in pathological solutions and I'm not going to step up and try to identify which spawned which. Goodness knows the happy UNIX story of happy text files configuring your happy isolated services has all kinds of horrific exceptions that don't appear in the happy part of the story, like Sendmail or .emacs.
The config system may have been designed with Windows registry in mind, because Miguel de Icaza, the leader of Gnome project back then Miguel de Icaza (of Mono fame), was copying windows, and gconf-editor is a _registry editor_.
As whether they'll make the same/worse/better mistake as Microsoft did, you guess is as good as mine.
I think the OP is a perfect candidate for Arch Linux.
Lemme try to explain some background on configuration storage in gnome.
But first, the main complaint in the article is that you can't modify the layout of the fallback mode panel in gnome 3. This is just not true, you can modify them in the UI just like before, only you have to hold down alt when you bring up the menus, etc. This was done because a lot of people accidentally changed their panel around causing problems. I'm sure this change could have been better documented and whatnot, but it is possible.
Once upon a time there was a design decision in Gnome to use so called "instant apply" configuration options, rather than having each config dialog button have "apply" buttons. You can disagree if you want, but this decision drives the design of the configuration framework. Basically, it implies having some kind of service that handles configuration changes that will tell other applications of configuration changes. Thus was born GConf.
The original on-disk format for GConf was an on-disk tree that mirrored the gconf key hierarchy, where each directory had a %gconf.xml file that listed the keys in that directory.
However, it turns out that this is a major performance problem when reading settings. Each such file you open causes two random access seeks on the hard drive. One to read the inode and one to read the data. Hard drive consecutive data read speeds are pretty high, but seeks are very slow (for physical reasons), which was significantly affecting login and app startup speed of gnome.
So, we merged the all the separate files into xml tree files, using one per application. This cut down on seeks a lot and improved performance. (Of course, a negative aspect of this is that the xml files are not very human readable anymore. But the vast majority of readers do not access the text files directly anyway.)
However, even after this gconf reads was a problem for log in performance. We do of course do local caching of gconf data in each process and we preload it in chunks, however during login the gconf daemon was acting as a serialization point for all processes that were starting up. Also, all these xml trees were pretty verbose, so parsing and loading also took some time.
Over the years we increased our knowledge of the problem space, and eventually we came up with a replacement for GConf. It has two parts, one is the API, which lives in glib, called GSettings. Its an abstraction for settings with change notification that has client-side schemas (as opposed to server side schemas like with GConf, another thing we learned). The implementation is pluggable, there is an ini file backend, a win32 registry, and the DConf backend, which is the default for Linux distros.
DConf uses a binary on-disk format that is mmapable and readable without "parsing". I.e. each app maps the config file readonly (sharing this memory), and lookups is done directly in the in-memory mapping without an intermediate parsed copy of the data. The data is stored in an efficient hash-table which allows very fast key lookups with few pagefaults in the file. The actual data is stored using GValue, an immutable binary datatype for recursive types that is in glib. So when a value is returned we don't even duplicate it but just return a wrapped reference to the data in the mmaped file.
Writes to dconf do go through a daemon which handles write serialization and change notification. Communications with the dconf daemon is through dbus, which incidentally has an on-wire binary data format that is a subset of GValue.
So, how does this help us? Well, for one thing we never block during login for reading configuration, as all reading is parallelized. Secondly we don't spend any time parsing files, as the config file, once mapped, is already in a compact "parsed" format. Thirdly, we never waste any memory storing copies of configuration data on the heap.
Now, there are some obvious drawbacks with binary formats. For instance, you need tools to modify them, like the dconf-editor GUI app or "gsettings list-recursively". Secondly, you can't use text based tools like e.g. git, emacs or diff/patch to maintain them.
But, you got to realize that we are not unaware of these problems. We are well aware of them, but we made the conscious decision that the real life problems with the many-text-files approach to configurations (as listed above) outweigh the advantages. Especially considering that most of our users don't need to directly modify the config files.
Also, resurrecting panel items that have accidentally been deleted can be difficult. The "Add to Panel" menu is missing some critical panel items that can (for unfathomable reasons) be removed, such as the "Applications" menu!
I am a little worried though. I have been a Gnome user for the past 10+ years, and this is the first time I don't understand the Gnome vision. I really don't know where you guys are going.
A lot of the rants on the web seem to point that before Linux was trying to copy Windows to lure users, then there was a moment of innovation that created the Linux feel. Lately I have read a lot about Linux trying to imitate Mac.
I don't know if it is true. Right now the vision seems incomplete, and using Gnome hurts. And Hurts bad. I can't seem to use a product that I don't understand.I guess I'll wait a couple of versions to see if I can finally understand Gnome.
The Alt key thing is a problem, though. I never would have found that on my own, even after finally finding out that you have to hold Alt to shut the machine down. I still don't know how to reboot without logging out first (which, I haven't tried, and I don't remember if LightDM has a reboot option either. So yeah, I was CTRL-ALT-F1-ing and rebooting from the command line.)
I mean, it looks very pretty, but how can I recommend this to friends and family when I can't even tell them to "try rebooting it" when there is a problem?
I get the feeling Gnome 3 is going to be awesome. I'm just not sure I'd want to unleash it on non-experts just yet.
To you it's a "major performance problem". To me, it's how I was able to unfuck my panel when I accidentally deleted the NetworkManager applet from it, because it was possible for me to see what was different in a freshly-created (!!) account.
I assume (based on your extensive explanation involving cache hits and disk seeks) that you have benchmarked this. How much time is actually saved by this change?
EDIT: Also, http://blogs.gnome.org/desrt/2010/12/19/more-on-dconf-perfor...
I can't seem to find out how to add new entries in dconf-editor, nor can I figure out how to add applets to the panels (I _need_ bubblemon)...
I have been using GNOME since 1.something.
Regarding the one-big-file: the time saving is nice, but that speed gain is kind of defeated when logging in hangs for 15 seconds (perhaps trying to find out why X doesn't do 3D on my graphics card, or something else?) - and the end result being _slower_ login in GNOME 3 compared to GNOME 2.
I remember seeing KDE for the very first time when it was in beta and saying, "Wow!"
For a while I'd have a horrible feeling of disappointment when GNOME and KDE would come out with new versions because each would seem to be to buggier and less usable than the last. Sometime around 2005 or so I gave up. It became less of a PITA to configure a Windows machine to make a decent workstation than it to use Linux. I still use Linux on the server, but almost never as a desktop.
I used Linux first in 1993, and back then it was leaps and bounds ahead of Windows in every way. It wasn't until 2000 that Windows brought brought out a stable operating system based on a good foundation that was actually competitive with Linux. Windows has grown a lot since then, and Linux has either been standing still (or almost, on the server) and going backwards (on the desktop). It's a tragedy.
It's a lua binding to webkit that allows you to fully customize your web browser as well, with a configuration scheme similar to Awesome. By default it's configured with VIM bindings, imo better than the vimium or vimperator plugins.
> "AppleWebKit/%s.%s+ (KHTML, like Gecko)"
in globals.lua and it will.
It would be great if Canonical concentrated their resources on making the system faster, like they did until recently (improved start up speed etc). However, now they seem to be dumping all work into reinventing the wheel by creating yet another Linux desktop GUI.
Anyway, that wouldn't be a problem at all, but Unity is still flawed, is totally unproductive for development work, and there's a distinct lack of customisation:
The launch bar is useless, and doesn't work at all if you let a window snap to the left hand side.
You can only add application shortcuts to it (why can't I add bookmark folders?).
There are no configuration options to be seen (what if I don't want auto-hide?), and whatever options there are, they're minimal.
Workspace switching isn't smooth at all and requires a strange number of clicks to make any use of.
Auto-hiding menubars just obscures GUI elements I'd like to be able to see at all times. If they're not there, I have to stop and remember where to look, because I can't just glance at the top of the screen. The actual name of the app is always visible, but clicking it does nothing. This is unbelievably unintuitive.
As for it replacing the classic desktop, I'm not sure what exactly was wrong with it, and why a GUI fit for a netbook or tablet is now being shoehorned into a desktop OS before it's had enough care and attention to bring it up to par with the standard desktop experience.
I regret running the upgrade and as soon as I can I'm switching to something more productive and usable, because 11.10 and Unity feels like too big a jump into unfamiliar (and unstable) territory.
And this is coming from an OS X user (who only uses Linux at work).
Wonder if we could have USERS to say what they want in each release? If Ubuntu continues this path, I'm afraid tech-savvy people will stop using it, not to mention many new users will never start trying.
What I don't like about ubuntu since 10.04, is that it the UI has become "opionated", without having the customizability that pre-gnome desktop managers have.
Specifically, there should be options to put the close/minimize/maximize buttons on whichever side I prefer, and whether to use mac-style menus or windows-style menus.
That said, I don't get all the bashing on GNOME and Unity; yeah, there are rough spots (and obligatory "power users" who think GUI means a window that shows one checkbox for each command-line option), but they're trying to do good and I applaud them for the attempt.
They are providing a free software option for you, and they work very hard on it. If you don't like it, you don't have to use it. But why be angry at them?
As for Ubuntu 11.10, I am posting this from there. Yes, Unity has some annoyances. But overall things work quite well.
But overall things work quite well.
It's an opinion. Clearly the author begs to differ.
> Yes, all those better ways to do the configuration, such as gconf2, oneconf, and other shit is really annoying, same like people who missing power and flexibility of a text file, not an XML but plain old var=value, or, OK, some Yaml.
But what can we do? The mediocre crowds are migrating from windows realms and they like to copy and paste, not to think and learn. ^_^
I just wanted to respond to schiptsov's comment by pointing out that copying and pasting is something you can do if you have a name=value or YAML text file, but not something you can do with gconf-editor. So if there are "mediocre crowds" who "like to copy and paste", they'll be better served by text-based configuration files.
For background ESR work is not in UI but in small but important stuff like GPSd, etc..
He is work here..both GNOME and Ubuntu have made decisions that are making an impact as far as driving adoption of new users to the platform..both sets of developers deserve big round of applause..
All Linux desktops before Unity sucked. Gnome 2.x sucked, big time. It looked ugly, and had only ugly themes. Its applications menu was completely useless. Its panel sucked. Its model for putting and managing launchers/shortcuts on the panel sucked. It was a complete mess.
Most Linux users were using Docky + GNOME Do.
I personally was using XFCE, because at least its panel was prettier and more customizable.