Windows 10 is still supported until 2032 if you use LTSC

Vibe coding with Github copilot, no less

They do as the slop king Satya guides (yes).

Copilot Tuesday

> I've been on Fedora now

I hope you are using KDE Plasma instead of the default GNOME which is going the Microsoft way.

If you are not on KDE, I strongly recommend it.

Source: daily driving Linux for 25+ years.

My experience has been somewhat different. I've had a linux server for a long time so I'm not new to the OS but my main computer which I use for development and gaming and everything else has always been Windows. I recently added a dual-boot Ubuntu for some performance-heavy development where the better docker integration made sense for me to use.

I had to try three window managers until I was able to use fractional scaling in such a way that my main 4K 32" screen shows 150% and my secondary screen shows a sharp image because Gnome cannot do fractional scaling only on one screen and for some reason 100% resulted in a blurry image.

The window manager crashed multiple times when I tried to unlock it.

Whenever I woke up my screen the whole system froze, apparently because of the USB hub in the monitor which registered. So far the only solution has been to disconnect the USB hub.

Fan control doesn't work properly because the chipset isn't supported.

I see rendering issues with window decorations all the time.

That's just after two weeks. I can't remember the last time my windows froze or crashed or had display errors. Whenever I'm in the console or do IO heavy stuff I feel right at home but as a desktop OS it's still inferior to me. I don't have fewer problems on Linux, just different ones.

This is the result of letting “devs” that only use JavaScript, that think JavaScript is an good language, and now only use AI to code, to do anything at all.

Microsoft is a joke; all of the formerly glorious tech companies are.

I was just helping my dad with a brand new Lenovo laptop with Windows 11. It felt unbelievable slow and sluggish. Just opening file manager to create a new folder lagged so much it felt like this would have been a 15 years old computer.

I’d also recommend people try Arch. The install process has been made waaaay easier in the latest versions. Mostly select what you want et voila you’re good to go. I installed it on a mini pc I took with me over the holidays to game on and it was great. The only thing I’d seriously suggest against is installing a bunch of packages from the installer itself.

Doing so caused me headaches because it installed Gnome (again my fault for selecting a bunch of packages) alongside KDE and I didn’t realize it. Causing me a bunch of “issues” until I selected KDE as the desktop environment on login.

I’ll probably move to Arch on my primary workstation sometime in the next few weeks (from PopOS which has treated me well for the last five years but Cosmic has been frustrating). My biggest reason is Arch has much more up to date packages than what I’ve had access to via Pop and it’s what SteamOS is based on so imagine it’ll be easier to keep up to date (along with little tweaks that Valve incorporates). Not to mention the Arch docs are great, I’ve had them help me even on PopOS for years now.

Addendum: Gnome + Wayland has more or less jumped the shark for me, with its highly opinionated design. KDE has thus far been plenty acceptable. For folks wanting to try both it’s easy enough to just install, pretty much all login managers (screens) let you choose which one you want. My only regret about KDE is losing Kinto.sh for MacOS style keybindings but I lost those with the move to Wayland anyway (still trying alternatives but they’ve been slow or quirky by comparison).

Please don’t blame react for this, and not because I like react. The real problem is bad development caused by processes, procedures and most likely pressures to cut corners.

Microsoft code is bad. This is not a react issue, and is probably not caused by lead developers. But the problem is now that things have regressed to 98 era technology, it’s going to take a long time for the problem to get better.

If only people knew how much of Microsoft Windows has been secretly powered by HTML pages for 20 years…

In Windows 95, Microsoft let you set a HTML file as your wallpaper and let you set up “channels” that were web-based widgets. This was the beginning.

Windows 98 used webpages as core components for Explorer. Literally browsing your files involved J(ava)Script… in 1998.

Windows XP/2000 still had Internet Explorer as a core component. Web tech was involved every time you opened a folder.

Windows Shell using web tech is as on-brand Microsoft as it gets.

Non-technical home users in my circles are fed up with Windows 11's changes from Windows 10 without a suitable transition that eases them into the changes. They are nowhere near good candidates to migrate to any flavor of Linux, though. There are still plenty of sharp edges. So lots of cursing and griping at Windows 11 continues.

More interesting to me however, are the macOS technical friends in my circles. A trickle of them are switching to various Linux desktop distributions. This was inconceivable to me a mere 10 years ago. But I have to admit the quality of the Apple ecosystem has slid an astounding amount, which is driving the more advanced technical users into the arms of Linux. There are still plenty of Apple ecosystem-specific integration points and features that are still not available on Linux, like Apple Notes/iMessage/AirDrop/AirPlay/Handoff between macOS and iOS, system-wide kinetic/momentum scrolling, iCloud sync, system-comprehensive battery management that includes working sleep and suspend, advanced trackpad gestures, uneven Unicode support, uneven human interface guideline adherence, limited laptop LLM inference, etc. So I'm not expecting this trickle to turn into a flood soon, but the solid lock Apple used to have on developer mindshare is not as solid any longer.