They are pushing hard on the developer experience because greenfield projects aren’t being built using Windows centric tooling anymore. If it’s server it’s Linux, and if it’s client it’s either electron or a web app. What will kill Windows is when there is no reason to buy Windows. MS recognizes this fact and has been pivoting to service offerings for that reason. They want users to make an MS account so they can herd people into their ecosystem.

DDG has had cost issues with some of the more complex queries. Exclusions (-) for example are very expensive, as Bing recently raised their prices. I think this is why search has gotten worse with DDG recently.

I firmly maintain that if Microsoft gave a shit about ARM, they would be defaulting every one of their compilers to produce fat x86/aarch64 binaries. The reality is, however, that they don’t care about the hardware so long as it is good enough.

Nobody will buy the hardware if they can’t commit to supporting the software. In a previous role, I was responsible for advising purchasing decisions for my company’s laptop fleet. The Surface X (Arm edition) looked cool, but we weren’t willing to take the risk, because at the time Microsoft had far worse transitional support than they do now. It’s gotten better, but no one in their right mind is going to make the kind of volume purchases that actually drive adoption until they demonstrate they are in it for the long haul. It’s a chicken and egg problem, and Microsoft doesn’t care what hardware you are using, so long as it is running Windows or using (expensive) Windows services.

They probably fear that the failed Windows mobile lineup tainted the brand name for the product’s target demographic.

OMG is it bad. We used a couple WD drives for a surveillance camera array and they didn’t last a year. Two drives failed 9 months apart. Ended up going on Blackblaze and picking what looked best for our XFS Raid 10 having learned that lesson the hard way.

This 1000%. Since basically High School I’ve been on Ubuntu for the machines I need to work, because at the end of the day it usually does. Some of the people I meet see that I use a Chromebook with the containers enabled and have similar reactions. “How can you use that it’s not even real Linux?”, as if it isn’t literally a Linux kernel. The Steam Deck is popular because you don’t need to know Linux to use it, and Ubuntu is popular because you don’t need to know a lot of Linux to use it.

I have a lot of love for OpenSuse. Back in my teenage years, I used it and Ubuntu a lot. zypper is the best package manager, and YaST made configuration easier since I didn’t know config files yet.

I gave it a Google and saw what changes they have made, and it definitely explains the new feel. Frame timing is waaay better and the frame rate is more stable. They moved from a OpenGL implementation to a Vulkan one, from my understanding. I had to adjust my mouse sensitivity too, so they made some changes there as well.

32-bit programs can’t use as much memory as 64-bit programs. Being able to use more memory means less loading from the disk. 64-bit also tends to be more optimized these days as most systems have moved to it already. In this case, I had no idea TF2 was still 32-bit.

Call me out if I’m wrong, but my Deck is noticeably snappier after this update. TF2 is also smoother, which is weird considering the game hasn’t changed visually at all. Not even an update notice of anything major.

The problem is they keep breaking in-home streaming to/from the Deck. My Mac has a significantly more GPU oomph so there are some games I’d like to play streamed, but streaming hasn’t worked in either direction since last year.

Japan too. The U.S. Congress threatened Japan with a trade war if they didn’t shutter their TRON project to create a domestic Unix. Nowadays it’s almost entirely Windows, and Japan has stagnated in terms of technology. They might have another chance at it with the world searching for an alternative to Taiwan for semiconductors and the potential legal status of AI training in Japan.

I don’t care whose indexes they use so long as the results are good. The problem isn’t the index, it’s how the contents get prioritized and presented. Kagi happens to do so well for me.

He offered to start a conversation about the blog post and give his perspective. The only thing I see here is the author refusing to stand on their post.

Having done my time as an Army medic, this is incorrect. It takes more force than that, but less than you might think. A good 25 kilos with some velocity behind it will easily sever a phalange. Up it to 50 or 80 kilos and you can claim an arm or shin. Mass is the real killer. I’ve seen a vehicle at comically slow speed absolutely yeet someone because it had several tons of momentum behind it.

At an old company I joined they had rolled them out to all employees. Six months before me getting onboard they had already given up, but we still had to support the ones out in the field. Fun fact about Surfaces, despite it being MS hardware running an MS operating system, the Windows 10 and 11 base system does not have drivers for the keyboard or mouse. You have to use a special image for the Surface devices. That meant maintaining two custom WIM images for deployment and keeping them in sync. We scrapped the remaining Surfaces and gave people the choice of Macs or ThinkPads instead. You can guess which was more popular among the office folk.

I used to have a black XBox sitting beneath the TV gathering dust. I think it is a One by the shape. As for the new ones I have no idea off the top of my head which is the best. I’ve seen some on sale in places, but the impulse buy isn’t there because I have no idea what I would be getting. I don’t own a PlayStation, but if I wanted one I know that 5 is the newest, and you can get the small slim one or the big Pro one.

Don’t give them ideas 😂

If Canonical and RedHat weren’t backing different horses (Snap vs Flatpak), I could see the app containerization system coming under systemD as well fairly soon. The Cosmic DE project uses functionality from systemD to overlay changes onto the system that are reversible, so that alpha versions of Cosmic can be tested without permanently changing the base system. Imagine apps shipping on whatever container runtime, and dynamically overlaying system-level changes as needed for things that tap into the host system via systemd-sysext.

A lot (and I mean a lot) of criticism can be leveled at systemD. One of the upsides of it becoming popular is the standardization of much of things from the developers’ perspective. It’s easier to target multiple distros when you can rely on systemD’s single implementation of the feature. Over the next decade, I forsee systemD eating more and more of the userspace, until you are only left with managing the differences between DEs and which display server they are using. We’re already headed towards immutable base systems with apps shipping with their own dependencies, which we reduce the differences between distros even further.