ChromeOS is currently rolling out to users on the Dev channel. So far it seems stable and only brings a few subtle changes. I have gone through the changelogs and here are the highlights.
It is healthy for people to have hobbies outside of their day jobs, one of my personal hobbies is 3D Printing. I have been planning to cover more 3D Printing stuff on my blog (along with the normal stuff I cover). I have covered a few 3D printing posts in the past but I feel it is time to start posting more. My first post will be getting my favorite slicer, Simplify 3D to run on a Chromebook via Crostini.
As I have mentioned on this blog in the past, the build of debian that is used for the default “penguin” container is very vanilla aside from a few extra packaged used to bridge some of the functionality with ChromeOS. These extra packages are not always updated via the primary Chrome OS update utility and thus must be manually upgraded via the command line. Google has released a upgrade for one of the packages – cros-garcon. Fortunately upgrading this package is very easy.
It is no secret that Android tablets are not as popular as they used to be. With the exception of the Amazon Kindle Fire and the Samsung Galaxy Tab line of tablets, it seems like many Android tablet manufacturers have given up on Android Tablets. Google has been working hard to replace Android with Chrome OS on future tablets and while this is a refreshing change, Could a Chrome OS Tablet replace your aging Android Tablet? For this post, we are going to put two leading flagship devices in a head to head battle – the Samsung Galaxy Tab S3 (Android) and the HP Chromebook X2 (Chrome OS).
Chrome OS is already one of the most secure operating systems in use today – light-years beyond MacOS and Windows in many ways however it is far from perfect. Here is my security wish-list for features I would love to see in future Chrome OS devices. Note, this page is just for security related changes, there are plenty of non-security feature I would like to see as well.
Normally it is a very trivial process to get a typical Chromebook into developer mode however this process is very different on the HP Chromebook X2 and other future Chrome OS Tablets. This is because Google actually requires dedicated circuitry to ensure the switch to developer mode was a deliberate action done by the user and not accidental or by a malicious application. Here are the steps to get the HP Chromebook X2 Into Developer Mode and these instructions should also work on all future ChromeOS Tablets