Google Chrome OS Flex and Broader Adoption of Linux

I recently read [Chin, The Verge (2022); Raphael, Computerworld (2022)] that Google is releasing a version of Chrome OS called Chrome OS Flex which can be copied to a USB storage drive and installed on computers that didn't come with Chrome OS. This seems very similar to how many popular Linux distributions work, so I initially wondered if Chrome OS Flex will succeed with the muscle of Google behind it where similar efforts by Linux distributions backed by smaller not-for-profit organizations have failed. At the same time, it seems clear to me that Google will not hesitate to use this as an opportunity to collect more valuable data from people who use Chrome OS Flex. This got me to think more broadly about how much ordinary people who might consider using Chrome OS Flex really care about their privacy (especially considering that such people would typically use Microsoft Windows 10/11, which are known to collect significant amounts of data from users) even after revelations about Facebook's practices, earlier revelations about government surveillance, and so on.

However, upon closer reading, I noticed that the first article makes clear that the target audience is schools & businesses which have many old computers whose Windows versions may no longer be supported. This makes more sense to me than targeting ordinary individuals, because I get the sense that the learning curve even to copy an ISO file onto a USB storage drive and install it onto a computer is steep for most ordinary individuals (despite the significant progress that distributions like Ubuntu & Linux Mint have made in making the installation process easy). By contrast, it seems more reasonable to expect specialists in schools & businesses to learn these things once and then do them for many different computers. Meanwhile, the second article makes clear that while traditional Chrome OS is capable of running many programs built for Windows, Chrome OS Flex will not have such capabilities. This suggests to me that while many schools may take up this opportunity given that few user-facing applications need to be installed on the computer and most user-facing applications can be accessed through web equivalents, this might not be the case for many businesses, so it is unclear to me which businesses will actually take this up.

Ultimately, I don't expect to see much adoption among ordinary individuals even though they aren't forbidden from installing & using Chrome OS Flex. That said, I would be interested to see how adoption evolves in schools & businesses over time.

Ongoing problems connecting a Canon CanoScan 4400F scanner to Linux Mint

This post is about the experiences I've had connecting a Canon CanoScan 4400F scanner to various computers, primarily focusing on my current laptop which, as of the time of first writing this post, ran Linux Mint 19 "Tara" MATE along with Microsoft Windows 10. For context, I am hoping to scan some of my personal & work notebooks for personal archival. I figured that this scanner, which I've had for a long time, does a good job at rendering images, even though it is quite old & slow, so I should continue using it for as long as it continues to work.

I used to use this scanner regularly with my previous laptop, which is an ASUS U30Jc and, when I last ran it regularly, ran Linux Mint 18.3 "Sylvia" along with Microsoft Windows 7; initially when I connected the scanner to the old laptop (a few years ago), it didn't work with Linux Mint out-of-the-box, so I decided to do all scans in Microsoft Windows and then transfer files between partitions later. I stopped using that laptop approximately 2 years ago, and since then until the beginning of this month, it just sat in a box gathering dust. At the beginning of this month, desirous of using this scanner again for the aforementioned purposes, I brought out the old laptop & scanner, but found out that in the intervening 2 years, the damage to the laptop's screen & hinge had worsened, the battery had completely died due to no charging in that time, and the laptop (on either OS) would randomly overheat & shut off. At this point, I now believe that old laptop should be junked.

My current laptop is an ASUS ZenBook UX331UN. I didn't think the scanner would work with it, because it uses USB 1.1, and I remember having trouble getting this laptop to read an older USB device. Just for the heck of it, I decided to connect the scanner to see what happens. Just as with my old laptop, in Linux Mint, the Simple Scan application didn't find any connected scanners. However, I had the idea to run the command "sudo simple-scan" from the terminal. That showed that the scanner was in fact being recognized, so this was probably a permission problem; I also realized that the earlier problem with another old USB device was specific to that device and not a general issue with this laptop reading any older USB device. That said, when I tried to scan a document, I got a window showing the error "Failed to scan: Unable to connect to scanner". Follow the jump to see more.

Second Laptop: ASUS ZenBook UX331UN

I was hoping that a post from when I got my first laptop, an ASUS U30JC, would provide a template for how to review my new, second laptop. Sadly, that post was from over 8 years ago, when this blog was just a year old, I had not yet started college, and my writing was much worse. With that in mind, I now provide a review of my new laptop; this review will be by no means a thorough review of hardware, but will be more of a summary of my experiences installing Linux on it and using it for around a month.

A few months ago, I noticed that part of the plastic frame around the screen of my old laptop, along with the hinge below it, had partially detached. A little over a month ago, that detachment had become much more noticeable, to the point of becoming a liability for me: the laptop would no longer close properly (without me risking breaking it altogether), so I would not be able to take it anywhere outside. Up until that point, I had experienced no major hardware issues with that laptop, and only minor issues such as the optical drive occasionally being unresponsive; I could tell that it was struggling a little more with newer software, but on the whole, it was performing quite well, so while I had from time to time over the last couple of years been looking casually into replacing it, this sudden development forced the issue. Given my disability, I wanted something a bit more lightweight, because my old laptop was 4.5 pounds, which was a bit heavy for me; that said, I still wanted something that would offer a reasonable amount of computational power, and while I didn't anticipate requiring a high-performance graphics card for gaming as I am not a serious gamer, I figured there may be some casual games as well as the possibility of getting into GPU programming for my work for which I may want a reasonable dedicated graphics card. Luckily, I found the ASUS ZenBook UX331UN, which seemed on paper to fit the bill on all counts, and I found only a few left in stock online for a reasonable price (just over $1000), so I went ahead and bought one. Follow the jump to read more.

FOLLOW-UP: Thank you, Microsoft

Thank you even more, Microsoft.
Not only has Microsoft recognized the GPL violations in the code for its Windows 7 USB/DVD manager, it has even fixed them (Emil Protalinski, Ars Technica) by releasing them under the GPL.
Not only does this mean that Microsoft actually care about OSS (even a little bit), it cares enough that it thinks the GPL will withstand the tests of the courts.
Thank you some more, Microsoft, for de facto legitimizing the GPL.

Thank You, Microsoft

Could I really be saying this?
Yes, I am.
Microsoft has finally owned up to a GPL violation - a recent one involving its USB/DVD manager in Windows 7.
They did not give any excuses or fibbing about how the GPL technically may not apply to them or any of that. They simply said that it should not have happened but did because of sloppy review of code contracted out.
Props to Microsoft for some much-needed honesty.