By now, you've probably seen the news about the Tizen-based Gear S smartwatch that was unveiled at IFA. Aside from having a massive curved screen (for a watch, at least), it also has GSM connectivity, meaning it can truly function as a standalone device.
If you're an app developer and that didn't get you excited, you should probably get someone to check your pulse (or I suppose you can have the Gear do it for you). We've talked in the tech industry about convergence devices for years, and this is exactly the sort of device we mean. And yes, various things have been getting cellular connectivity for years, but aside from phones, it's really only a recent trend that companies are legitimately working to build third party app ecosystems around these devices.
The Smartwatch market is certainly going to be a lucrative space for the companies that can be first to release their products, go through the lessons learnt cycle, and also be able to build a viable application ecosystem on top of it, which shouldn’t be confused with standard smartphone apps, as not all apps translate well to your wrist, and therefore you don’t need as many. No one is going to want to edit a picture on their wrist on the move, even if they can !!!
Operating System U: A new Linux based OS with a firm focus on you the user and functionality over UI overhauls, hits KickStarterSubmitted by Rianne Schestowitz on Monday 8th of September 2014 08:32:09 PM Filed under
There's isn't probably a piece of software that is as hated as Windows 8's Metro UI. Some seasoned Windows enthusiasts like it, but most of the normal day-to-day user had a hard time getting used to it. Operating System U is being readied with the regular user in mind, and is based on Manjaro Linux. A quick overview of the project.
Containers and hypervisors are often seen as competing technologies – enemies even. But in reality the two technologies are complementary and increasingly used together by developers and admins. This recent Linux.com article talked about this supposed battle, noting however that developers are using Docker in traditional VMs to bolster security. Containers allow users to develop and deploy a variety of applications with incredible efficiency, while virtualization eliminates any constraints and/or exposure to outside attacks.
Uniting these technologies helps developers and system administrators be even more efficient. Let’s take a closer look at how to achieve this with Docker and Xen Project virtualization, and why we expect more and more organizations to use them together in the near future. This will also be a key topic at the September 15 Xen Project User Summit at the Lighthouse Executive Conference Center in New York City. Register today to learn more about enabling Docker in Xen environments for a truly open infrastructure.
The Free Software Foundation (FSF) and the Debian project today
announced cooperation to expand and enhance h-node , a database to
help users learn and share information about computers that work with
free software operating systems.
While other databases list hardware that is technically compatible with
GNU/Linux, h-node lists hardware as compatible only if it does not
require any proprietary software or firmware. Information about hardware
that flunks this test is also included, so users know what to avoid. The
database lists individual components, like wifi and video cards, as well
as complete notebook systems.
One reason Docker is interesting is that all four answers are each individually useful, but can be used in combination. This causes cross-pollination of ideas and patterns. For example, someone might start using Docker because they like the speed and portability, but find that they end up adopting the configuration and Docker hub patterns as well.
The Docker technology is still fairly new; work is underway to add missing features, and a large ecosystem of related projects and companies is forming around it. There’s a lot of interest in the technology from the VC community, as we try to figure out whom to fund to do what, and how the story will play out in the longer term.
One of the main problems with Linux platform fragmentation is that there are a number of concurrent binaries available for various platforms and they are not compatible with each other. Linus Torvalds explains why he thinks that the binary concept on Linux is broken and why he doesn't use them for his projects..
You can take a Linux installation of nearly any distribution and turn it into a server, then back into a workstation by installing and uninstalling various packages. The OS core remains the same, and the stability and performance will be roughly the same, assuming you tune they system along the way. Those two workloads are very different, however, and as computing power continues to increase, the workloads are diverging even more.
Maybe it's time Linux is split in two. I suggested this possibility last week when discussing systemd (or that FreeBSD could see higher server adoption), but it's more than systemd coming into play here. It's from the bootloader all the way up. The more we see Linux distributions trying to offer chimera-like operating systems that can be a server or a desktop at a whim, the more we tend to see the dilution of both. You can run stock Debian Jessie on your laptop or on a 64-way server. Does it not make sense to concentrate all efforts on one or the other?
After watching classic TV shows such as Knight Rider and Street Hawk in his youth, IT professional and Raspberry Pi enthusiast Derek Knaggs was inspired to create a low-cost in-car computer using a Raspberry Pi.
The Pi sits in the centre console of his Ford Focus, wired to the display of an Xtrons DVD player (optional) as well as two TFT screens in the rear headrests. Control is via a Xenta wireless keyboard with mouse touchpad, while a smartphone can be used as a wireless hotspot to give the Pi an internet connection on the move.
Having recently added a reverse camera to his already top-notch project, we caught up with Derek to learn more about it…
Some plans for the GNOME 3.14 cycle didn't materialize but they're still being developed for future GNOME updates.
For the GNOME 3.14 development cycle was a plan to make most GNOME modules depend on a systemd logind-like API that would only implement the API bits actually used by the respective pieces of GNOME software. The goal was to make this minimal API a shim between the GNOME code and logind for allowing other non-Linux platforms to write an alternative implementation against the API. The purpose of this would be for the BSDs also using GNOME to only have to write a portable implementation of the logind-derived API calls actually being used by GNOME rather than a full, drop-in replacement.