Language Selection

English French German Italian Portuguese Spanish

Gnome 3.12 review – work Ubuntu could have benefited from

Filed under
GNOME
Reviews

In a nutshell, I think Gnome teams have done an incredible job with 3.12 and created a desktop which is extremely simple, extremely secure and privacy respecting compared to Unity, and doesn’t need any learning curve. If there are free software advocates who want to convert Windows XP users to GNU/Linux, Gnome’s ease of use will certainly help.

What amazes me the most about Free Software and GNU/Linux is that there is always something for everyone. At one hand, you have KDE Software which is extremely polished, and mature – which can be customized to your very needs. It’s more or less like customizing your own Harley Davidson; on the other hand you have something as simple, secure and elegant as Gnome which doesn’t require any work and offers a very easy PC experience.

Since both these heavyweights of the free software world have matured enough you can now sit back and enjoy. I never miss either because I have them both installed on my openSUSE/Arch side by side.

Why to make compromise when you can have the best of both words!

Read more ►

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