Recommendation would be to use a Thunderbolt Ethernet adapter so it can directly connect via PCI Express. These USB Ethernet dongles are often crappy.

USB-C is fairly open, and USB4 can do most things Thunderbolt 3/4 can do, but there are exceptions like daisy-chaining. Thunderbolt 5 is also out now, and it has no open counterpart. And Thunderbolt is very much proprietary, requiring licensing and certification from Intel.

To be fair, USB-C, especially with Thunderbolt, is much more universal. There are adapters for pretty much every “legacy” port out there so if you really need FireWire you can have it, but it’s clear why FireWire isn’t built into the laptop itself anymore.

The top MacBook Pro is also the 2016+ pre Apple Silicon chassis (that was also used with M chips, but sort of as a leftover), while the newer MacBook Pro chassis at least brought back HDMI and an SD card reader (and MagSafe as a dedicated charging port, although USB-C still works fine for that).

Considering modern “docking” solutions only need a single USB-C/Thunderbolt cable for everything, these additional ports only matter when on the go. HDMI comes in handy for presentations for example.

I’d love to see at least a single USB-A port on the MacBook Pro, but that’s likely never coming back. USB-C to A adapters exist though, so it’s not a huge deal. Ethernet can be handy as well, but most use cases for that are docked anyway.

I like the Framework concept the most, also “only” 4 ports (on the 13" at least, plus a built-in combo jack), but using adapter cards you can configure it to whatever you need at that point in time and the cards slide into the chassis instead of sticking out like dongles would. I usually go for one USB-C/Thunderbolt on either side (so charging works on either side), a single USB-A and video out in the form of DisplayPort or HDMI. Sometimes I swap the video out (that also works via USB-C obviously) for Ethernet, even though the Ethernet card sticks out. For a (retro) LAN party, I used 1 USB-C, USB-A (with a 4-port hub for wired peripherals), DisplayPort and Ethernet.

They will run Linux, but you might fry them if your fans don’t work properly.

The EFI will control the fans just fine.

SMS, iMessage and now RCS have been working well for me and I’ve been (primarily) using iPhones for the past 8 years now.

The Messages app shows what type of message (iMessage/SMS/RCS) you’re about to send in the text field and displays which (sent or received) messages are what as well.

One thing I could see going wrong is that a given phone number is registered with iMessage and it hasn’t been disabled after switching to an Android phone for example.

Another (imo more likely) thing is that if it’s using RCS, some carriers don’t seem to work too well with it as of now. iOS seems to have implemented the base standard, while Google added proprietary extensions to said “standard” in Android, like end-to-end encryption. I never had issues sending or receiving RCS messages from/to Android devices, but there might be some hiccups for some people as RCS - even though it’s called a “standard” - isn’t really standardized.

Not sure what’s so insane from Apple’s side about any of that.

Your company should provide you with an Apple ID (or “Apple Account” as it’s apparently called now), no…? If they didn’t but one is required, ask them.

https://mapgenie.io/

Or what do you mean?

At 8 months old it should be well within warranty. Just get it fixed.

deleted by creator

The 7950X3D or 9800X3D are both faster (besides the 7800X3D you mentioned).

GPU-wise this is obvious the best AMD has to offer, but an RTX 4090 is obviously faster still. With the typical caveats for NVIDIA on Linux.

I have several components in my network that are at least 6 years old. Is that a problem…?

full mirrors of YT

Yeah…not going to happen.

Sounds cool, I just fail to understand how this takes Cinnamon “out to the real world”.

What’s Ullr?

Sounds about right. There are some valid and good use cases for “AI”, but the majority is just buzzword marketing.

The main thing (by far) degrading a battery is charging cycles. After 7 years with say 1,500 cycles most batteries will have degraded far beyond “80%” (which is always just an estimate from the electronics anyway). Yes, you can help it a bit by limiting charging rate, heat and limit the min/max %, but it’s not going to be a night and day difference. After 7 years with daily use, you’re going to want to swap the battery, if not for capacity reduction then for safety issues.

I think I have a simple function in my .zshrc file that updates flatpaks and runs dnf or zypper depending on what the system uses. This file is synced between machines as part of my dotfiles sync so I don’t have to install anything separate. The interface of most package managers is stable, so I didn’t have to touch the function.

This way I don’t have to deal with a package that’s on a different version in different software repositories (depending on distribution) or manually install and update it.

But that’s just me, I tend to keep it as simple as possible for maximum portability. I also avoid having too many abstraction layers.

That’s mostly down to Teams though (being the bloated web app that it is), and not the underlying operating system.

Technically, wired charging degrades the battery less than wireless charging, mainly because of the excessive heat generated by the latter. The same way slower wired charging generates less heat. Lower and upper charging limits also help (the tighter the better).

But I personally don’t bother with it. In my experience, battery degradation and longevity mostly comes down to the “battery lottery”, comparable to the “silicon lottery” where some CPUs overclock/undervolt better than others. I’ve had phone batteries mostly charged with a slow wired charger degrade earlier and more compared to almost exclusively wireless charging others. No battery is an exact verbatim copy of another one. Heck, I had a 2 month old battery die on me after just ~20 cycles once. It happens.

Sure, on average you might get a bit more life out of your batteries, but in my opinion it’s not worth it.

The way I see it with charging limits is that sure, your battery might degrade 5% more over the span of 2 years when always charging it to 100% (all numbers here are just wild estimates and, again, depend on your individual battery). But when you limit charging to 80% for example, you get 20% less capacity from the get go. Unless of course you know exactly on what days you need 100% charge and plan your charging ahead of time that way.

Something I personally could never be bothered with. I want to use my device without having to think about it. If that means having to swap out the battery one year earlier, then so be it.

When talking about the kernel, Windows actually skipped 3 major versions iirc from the top of my head. Windows 8 was Windows (NT) 6.2, and Windows 10 skipped that version number to, well, 10.