Skip to main content

Is Windows 11 Microsoft's way of asking people to consider OSX and Linux?

If you've been keeping up on tech news you've likely seen the positive stories reassuring you about the upgrade to Windows 11:

There are a number of unpallatable things being pushed in Windows 11 (specs):

  • "You need a Microsoft account" - what? why do I need this? any privacy concerns?
  • "Trusted Platform Module (TPM) version 2.0" - again, why is this necessary? Windows 10 works fine without it...
  • Shifting CPU requirements - A month ago the Windows 11 compatibility tool said you needed a pretty new CPU (for no technical reason anyone can figure out), now it looks like a wider range of processors are supported. This is a remaining area of confusion.

Not excited about Windows 11? There are some options:

  • Switch to OSX (via Apple) or Linux
  • Remain on Windows 10 as long as possible
  • Upgrade to Windows 11 and deal with the requirements
  • Hope Microsoft will ease up on user tracking, TPM, and CPU requirements due to the bad press

I think we'll see a few things:

  • Many, if not most, Windows 10 users will upgrade to Windows 11 in the next year, certainly all of the corporate users that need Windows 11 and home users that have hardware that meets Windows 11 requirements. It's a free upgrade for Windows 10 users.
  • A number of users will remain on Windows 10 for years, just like users are still running Windows 95 and XP.
  • Some people with hardware that doesn't meet Windows 11 requirements will give the new M1 Macbooks a shot and some of the brave may try out Linux.

    • I've been pretty happy with OSX on a Macbook with containers, and when necessary using Windows and Linux VMs. It will be interesting to see from the sidelines how this Windows 11 thing plays out.

Comments

Post a Comment

Popular posts from this blog

Debugging an imprecise bus access fault on a Cortex-M3

This information may apply to other cortex series processors but is written from practical experience with the Cortex-M3. Imprecise bus access faults are ambiguous, as noted by the term "imprecise". Compared to precise bus errors, imprecise errors are much trickier to debug and especially so without a deep understanding of arm processors and assembly language. Imprecise and precise flags are found in the BusFault status register, a byte in the CFSR (Configurable Fault Status Register). BusFault status register bits The definition for imprecise and precise bits is: [2] IMPRECISERR Imprecise data bus error: 0 = no imprecise data bus error 1 = a data bus error has occurred, but the return address in the stack frame is not related to the instruction that caused the error. When the processor sets this bit to 1, it does not write a fault address to the BFAR. This is an asynchronous fault. Therefore, if it is detected when the priority of the current pr...
5 comments
Read more

Travelling on Spirit airlines out of Boston Logan airport? Here are some tips.

I attended CES 2017 in Las Vegas. Booking the trip late I ended up on Spirit airlines. It was both non-stop, making it six hours to Las Vegas from Boston, and affordable, less than $300 for a one way trip compared to around $700 with JetBlue. Here are some tips that might help you when travelling on Spirit from Boston Logan airport. Eat Spirit is located in the B-terminal, gates B-37 and 38, with its own TSA security checkpoint. While it does have restrooms and places to sit the food selection is limited to a single food stand. I'd recommend eating at the Legal C Bar (number 77 in the image below) prior to going through the terminal security checkpoint. The food and service there were great. Drink The water and other drinks are cheaper if you buy them at the food cart rather than on the flight. Seats The seats on Spirit don't recline. They do this to reduce weight, seat cost, seat maintenance costs, and so seats don't impact the free space of other passengers,...
3 comments
Read more

Yocto recipe SRC_URI for a BitBucket / GitHub ssh git repository

This is a particularly geeky post but because Google searches didn't turn up any information I thought it would be helpful to document the issue and solution for others. I was writing  Yocto recipes that pulled from BitBucket git repositories in ssh form and ran into several issues getting a SRC_URI that worked. GitHub uses the same syntax for their ssh repositories. A BitBucket / GitHub git url, in ssh form, looks like: < username >@bitbucket.org:< account name >/< repository name >.git a more concrete example for a git repository in one of my BitBucket accounts looks like: git@bitbucket.org:cmorgan/somerepository.git Yocto recipes can pull from git repositories by setting the SRC_URI variable appropriately. Unfortunately you can't just do: SRC_URI = "git@bitbucket.org:cmorgan/somerepository.git You'll get errors because the Yocto won't know what kind of url this is. You need to specify the protocol for Yocto to k...
2 comments
Read more