Language Selection

English French German Italian Portuguese Spanish

Putting Tizen in Context

Filed under
Linux
Gadgets

From the very start, Tizen has had the concept of device profiles, where there's a common set of core software components (kernel, coreutils, networking stack, etc.) that are applicable to every type of device, and there are specializations specific to whatever it is you're using. Take your hand and open it flat. Ok? Good. Your palm is the core software stack, and your fingers are the device-specific profiles - handset, IVI, TV, etc. Chances are good that many elements of the core stack will be the same, and in all cases you want to optimize for lower power consumption and better performance, but what a smartphone presents to the user is generally quite different from an IVI system, or a wearable device, or a camera, or a TV, or a refrigerator, or... I'm sure you get the point. One size doesn't fit all, but you certainly can be smart about not reinventing the wheel for each product class.

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