Also Ford’s CEO: kills sedans in the US several years ago.

https://fordauthority.com/2024/06/ford-ceo-jim-farley-says-company-lost-billions-on-sedans/

That worked out great for Apple, Microsoft, and others. Good luck, Amazon.

I don’t get it. They’re not already?

Wow. Hadn’t thought about it that way.

Similar history including gentoo and distcc to speed up openoffice and x11 compiles with a pile of old computers.

Put linux on a PC laptop and it just so happens the NVMe controller in conjunction with the kernel driver has some glitch that causes the hard drive to fall off the bus forever. No big deal…

It’s great seeing a bunch of nvme nvme0: I/O (number) (I/O Cmd) QID 10 timeout, aborting then reset controller then removing after probe annnd data loss. Didn’t have the patience to figure out the bug in the driver right now. Maybe someday.

Win10 gets Copilot as well. Pushed without consent. Likewise if you use a program like InControl to lock W11 to 22H2, you can keep copilot at bay. For a time.

Switching to any other platform is better though. Screw them.

Apple also has partnerships with Google, Meta, and others. Your data is being sold on that platform. It is just more formal and profitable for Apple.

Hah, my curse is calls always finding weird ways to drop. Then I moved to a place with no cell service, because I’m apparently a wireless masochist?

There’s some slight technical reason for it, but I think they swung a bit too far in the asshole direction with blocking too many.

The LTE rollout was completely botched from the start. LTE voice is technically supported on all LTE chipsets, but early on the voice spec changed. Early phones used LTE for data and 2G or 3G for voice.

Complicating matters further, AT&T and Verizon both have separate and slightly tweaked versions of the spec, as they didn’t want to wait for it to be finalized, and of course they’re both different in different ways. It’s also why T-Mobile allows so many devices. They just rode their very fast for the time HSPA+ network until LTE was finalized, got generic hardware on the network, and flipped the power switch.

To top it off, AT&T was sued at one point for 911 not working due to a handset bug and they got very controlling at that point to avoid future lawsuits.

VoLTE is ostensibly VoIP over cellular data at its core. All phones have to talk with the correct SIP signaling on VoLTE for voice calls to work. With 2G and 3G, the circuit-switched method of signaling was much more standardized (although not necessarily simpler, WCDMA at its end spanned literal volumes of books.) This made it so phones and networks were more easily compatible for basic things like voice, 911, etc.

Now, on top of Verizon and AT&T thinking that rolling their own flavors of LTE was a good idea, every phone maker also had their own idea about how the VoLTE SIP signaling was supposed to work. Due to flaws in the LTE spec, carriers going rogue, and companies interpreting things wrong, it has turned quite literally into a clusterfuck.

TL;DR: It took a long time for LTE to standardize enough across product lines, and there are a whole bunch of phone models that don’t talk the language quite right. So carriers chose to ban rather than make workarounds or work with the vendor to roll a software fix to the phone.

GPT is selectively useful. It’s also, as of the last few weeks dumb as a bag of bricks. Dumber than usual. 4 and 4o are messed up. 4 mini is an idiot. Not sure how they broke them, but it started roughly around the time of the assassination attempt. Not sure if it was a national security request or a mere coincidence, but just the same.

I’m even seeing 4o make comically dumb and stubborn programming mistakes lately, like:

GPT: “I totally escaped that character”

Me: “no, it’s the same as your previous response.”

GPT: “Oh, sorry, here is the corrected code.” replies with same code again.

I canceled my sub.

Thank you for the clarification. WHQL is such a pain to set up, I’m sure the AV vendors whined, “but, security! Do we have to test everything every time? That would slow an urgent 0day release!”

Not even that. Kernel drivers are supposed to be Microsoft WHQL certified through a thorough testing process (that would have caught it in 3 minutes) before Microsoft will cryptographically sign them.

…but apparently Microsoft allows AV vendors to skip WHQL certification testing.

Honestly, it wouldn’t have been a bad place to be if they hadn’t destroyed it from the inside. Windows on ARM is super stable. You can still build your own computer, or at least buy one with user-swappable parts. Linux has become much easier and wasn’t too bad to use even a decade ago, but it was nice being able to have a non-Apple computer running programs and getting work done that was just there to do the business. I’m speaking as one that attempted to use the kool-aid for a few years after Apple stopped using user-swappable batteries, memory, disk, their hardware upcharges are pure asshole insanity. I’m fully capable of using Linux, compiling my kernel, modifying driver source to work around problems, but, I don’t want to when I’m just trying to pay my bills. Streaming media services come and go with Linux support, hardware support is often lacking until the work is done to make the hardware work correctly. Windows, for all it’s … windowsness … worked. Until the last 8 months when they decided to put a molotov cocktail under the hood and see what happens.

Apple is headed this way too, now that they don’t have SJ to errantly blow up the current tech to try something new and random (although, had he survived his cancer, he’d have just gone Musky with age like a lot of that generation has, mmmm leaded gas!) Apple will hold on just a bit longer because iOS gave them one new platform reboot (ish) to live off of, while Microsoft is still kicking around technical debt until the end of time.

Oh, edit though, I’ve been migrating my machines to Linux one by one now. Not going to bother sticking around to see that Windows train wreck continue.

To point out that: even on the operating system/platform where the YouTube app comes from, it is pointless. Works fine in a browser.

There’s no reason to even use the YouTube app. One of the first things I uninstall on Android.

Having to do the meta-workaround of running another computer to make your computer usable is just…don’t get me wrong, I love running infrastructure, but that seems like it should be unnecessary just to use a computer.

Hahaha! I’ve been dabbling in live USB thumbdrive copies of various flavors of Linux to see which one I want to go to for a while. Did a few years back and thought, “you know, my time is worth something to me, maybe I’ll give Windows a go, 10 seems pretty stable.”

Booted up Debian Cinnamon, couldn’t get two-finger right click to work on the Synaptics config out of box, it had a few arbitrary prefs for whatever the devs decided people would probably use. Tried Debian Gnome. It had trackpad settings that were more in line with what I expected… Not giving up, but it did make me pause, because I know one can reconfigure the trackpad driver under the hood, but did I really want to jump down the rabbit hole of bespoke shellscripts again just so my audio driver correctly wakes from sleep (if it can even successfully sleep)?

Other funny to figure out, the computer has iGPU and dGPU, both were active and the battery life was maybe 2 hours. Another thing to figure out with bespoke configurations.

So it’s like, Windows and Linux (and lesser, MacOS) pain is definitely there, it is just kinda what kind of pain do you want to subscribe to? Linux pain will probably only occur during initial setup and maybe every few years when a major OS release comes out. MacOS pain is even more rare, unless a major OS release comes out with something you don’t like and you have to find where in the OS frameworks the feature is to disable it, if they have hooks in which to do. Windows pain is…every Tuesday.

“Oh here’s a new lock screen weather widget”

“Oh cool, I can get on board with that!”

Next week:

“Oh, here’s a new stocks and news widget to go along with the weather.”

“Hold on there buddy, I didn’t sign up for the first and you’ve pushed two more? Time to shut those two off. Oh, it’s all or nothing, thanks! Nothing it is.”

“Don’t worry, we’ll reinstall Dev Home next week and flag it a system app so you can’t uninstall it, and then we’ll force Copilot to be present, and then we’re going to screw with the start menu, and then we’re going to delete WordPad, and reinstall all those Office/cloud 365 shim apps and and and.” That was like, last month.

Granted it was a few months ago, but I seem to recall a command prompt keystroke and a command line command that allowed skipping online install during setup.

So you’ve obviously never had to use defaults write com.apple.stupidpreference.fix bool true

Apple has a lot less nonsense than Microsoft, but the amount of nonsense is greater than zero. What’s really annoying (on their mobile platform specifically) is when certain problems occur on iOS that would have been completely solvable on MacOS with a command line tool, but you have to erase the phone because Apple doesn’t give you access to the OS.

MacOS is already deprecating the Keychain access tool, which will obfuscate more of the OS security from the user and make it more iOS-like in trying to fix failures.

Apple is enshittifying in absence of Jobs, they’re just behind Microsoft by one or two decades.

Removed by mod