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

Graco Swing By Me - Battery to AC wall adapter modification

If you have one of these Graco battery powered swings you are probably familiar with the cost of C batteries! The swing takes four of them and they only last a handful of days. I'm not sure if the newer models support being plugged into the wall but ours didn't. If you are a little familiar with electronics and soldering, here is a rough guide on how you can modify yours to plug in! I wasn't sure how exactly to disassemble the swing side where the batteries were. I was able to open up the clamshell a bit but throughout this mod I was unable to determine how to fully separate the pieces. I suspect that there is some kind of a slip plate on the moving arm portion. The two parts of the plastic are assembled and the moving arm portion with the slip plate is slid onto the shaft. Because of the tension in that slip plate it doesn't want to back away, and because of the mechanicals that portion of the assembly doesn't appear accessible in order to free it. I was
Post a Comment
Read more

Memory efficient queuing of variable length elements

In embedded environments memory can be a critical driver of the design of data structures and containers. Computing resources have been expanding steadily each year but there are still a wide range of systems with far less than a megabyte of memory. On systems with tens of kilobytes of memory, structures are often designed to be compact to maximize data density. Rather than splurging on memory aligned elements that would be faster for the processor to access, a developer will typically use types with minimal sizes based on the known range of values that the element is intending to hold. Fixed sized buffers At my day job a fixed size pool of messages was implemented to hold message data. While this achieved one design goal of using statically allocated buffers, avoiding dynamic allocations that might fail at runtime, it isn't efficient if there is a wide range of message sizes. It isn't efficient because each message uses a message buffer. With small message sizes the buff
2 comments
Read more