Language Selection

English French German Italian Portuguese Spanish

Science Behind The Controversial Design Decisions Of Ubuntu Unity

Filed under
Software
Ubuntu

Whether you like the Unity interface or not, it mostly depends on your personal preferences. But Ubuntu Unity is often criticized for many of the design decisions that went into its making. Two of the most criticized decisions are

1. Global Application Menus
2. Side placement of the Launcher

Some people say Mac and Win were the inspiration but something tells me its not only about inspiration. There is a reasonable amount of logic behind these decisions and a lot of careful thought process went into making such decisions.

Getting into the minds of the developers and designers help us understand the reasons why certain things end up the way they are and why certain decisions were made. Let's try to reverse engineer the thought process that eventually led to these decisions.

rest here




More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more