Language Selection

English French German Italian Portuguese Spanish

Great Expectations for Linux in 2013

Filed under
Linux

Well another holiday season has come and gone, leaving more than a few jangled nerves and expanded waistlines in its wake.

Holiday pressures are bad enough by themselves, of course, but Canonical's splashy and yet profoundly confusing Wednesday announcement so soon afterward hasn't exactly helped.

Yes, it's Ubuntu for phones, but it isn't the same as the Ubuntu for Android you've been expecting for almost a year! Sure, makes perfect sense!

Oof, it's going to take more than a few triple Tequila Tux cocktails to bring back Linux Girl's hitherto cheerful post-holiday mood.

What May Come

Anyhoo, leaving all that Ubuntu wackiness aside for the moment -- Linux Girl knows she can't avoid discussing it, but will save it for another day -- it's time to look at the big picture.

This is the start of a momentous new year, after all, and as such Linux bloggers -- like so many others around the world -- have been forming their hopes for what may come over the next 12 months.

Ready for an obfuscation-free look at the future? Then relax, sit back and read on.

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