Nope

Resolution alone isn’t the only factor. It’s a larger display, requiring more power, which is either a PC/PD issue, or a battery issue. The point is that the power draw has to come from somewhere, and nothing this is the same platform as an iPhone (essentially), there’s going to be a trade-off somewhere.

As you noted they’ve reduced the refresh rate, which makes a big impact, but I don’t think it stops there.

The original platform has apps that are optimized for that platform, and now you’re throwing a different OS at it which has more expansive use of resources: CPU, memory, GPU, and power.

We’ll have to see how they have made paths through MacOS to account the platform specifically, but I’m betting there are several drawbacks. This was the main complaint of how they dealt with those insanely expensive Mac Pro with M-class chips when they first came out, but in the inverse. High power draw, heat issues…etc.

Mobile chip power is insane AT THAT SCALE though. That’s the key differentiation here. So if you’re running a larger format display with a higher resolution, cut that by quite a bit. Also cut it if you’re running desktop apps that aren’t optimized for mobile, and if this is intended to run MacOS instead of iOS, the mobile optimistic memory scheduling is out the window. I’ll have to see it to say for sure, but I’m guessing the performance for average desktop apps is going to be pretty, but that’s kind of the price point.

This is Apple’s scoop up of the ChromeOS segment.

Repair friendly means CHEAP components repair, which Apple just does not do.

As an example, in a machine like this if your WiFi module tanks…that’s a full logic board replacement. Might as well buy a new one.

According to this, Apple is basically making an insurance vertical as part of their business, and they are pricing repairs to be exactly 1/3 the retail cost of the machine for pretty much everything except screens.

This is pretty scam my when you consider their past of quoting customers for repairs that are above and beyond the scope of the actual hardware failures, and what maximizes profits for their AppleCare and RMA process. There are dozens of breakdowns in this, so I won’t write a novel, but it’s very obvious they’ve baked in the costs to make it more cost-effective to just keep buying new units as a replacement in the face of simple hardware failures.

The failure rates of these will be the determining factor. The components inside are cheap, all soldered on, and will not be repairable at all (waiting on the iFixIt score).

Its pretty much just their phone platform with a big screen and keyboard, so maybe it’ll be okay. It’s not built like a phone though, so I’m expecting some interesting testing outcomes. It’s either going to be cheap enough that they have a new planned obsolescence hit on their hands, or people are going to be pissed at it sucking so hard.

Did your account get hacked, buddy?

Fedora or Debian, but it depends on what you’re going to be using it for.

Maybe you want a NAS OS instead? Maybe a media system like Open Filevault? If just runnings VMs and Containers, maybe something geared towards that.

Fedora does have some nice preconfigured stuff like Cockpit and several helper automations by default. Yes, they can be installed on Debian, but it’s extra steps.

Your hardware is really the defining factor at the lower levels, but then whether you have encrypted partitions is the barrier at the OS level.

Understanding where your problem lies needs to be known, so more symptoms or logs would be helpful.

Detected means the system sees them. Mounted means the partitions in those drives have been mapped to a local area on your filesystem where you can access them.

Depending on your desktop and settings, this is usually an automatic thing for well known filesystems like NTFS or FAT, but not so with encrypted volumes because there are extra steps to mounting them during boot (like a passphrase).

If they you had Bitlocker enabled in Windows, then they will not automount. So if in Gnome open up the ‘Disks’ app, or ‘Partition Manager’ in KDE, see if your dicks show up there, then click on the partition you want to mount and it should ask for your disk password to mount it.

Not that I’ve heard of this. This isn’t a compressed package in the same way a zip is, it’s an application package.

I assume you mean they aren’t mounted and readily showing up for access. Are they encrypted?

Open whatever disk manager you like and see if there drives are detected, but just not mounted. Usually the case if they are encrypted.

Good soundtrack, at least in the first one.

That zip file contains an rpm package that has the PPD files. You’ll need to be on an RPM-based distro to install it as-is, or use a tool to unpack it.

What distro are you running?

Nope.

Hate to keep litigating this around here, but the shift alone is enough. Explaining to people WTF an immutable filesystem is, is a sure way to frustrate them into giving up, despite whatever comms finesse you might THINK you have.

Counterpoint: STOP SUGGESTING IMMUTABLE DISTROS TO NEW USERS

For people who just want a functional OS, they don’t want to have to think about new rules. They need a quick off-ramp from Windows that acts as they expect.

Package management is already enough of a mindfuck for people switching, then you’re throwing in containers, permissions, flatpak vs native packages, what sandboxing is, why your browser likely can’t just upload a simple fucking file, and why your camera doesn’t work on Zoom, because you have a meeting in 10 minutes.

Unless you are handing people something akin to a mobile OS with everything all inclusive and configured so EVERYTHING works off the bat, you’re doing such a huge disservice to people switching over to an immutable distro, and there is ZERO benefit, but all kinds of added frustration.

You need to stop, and I yield my time.

Meta never acquired my VR Mansion. It was super cool.

Dafuq

Never go to a second location, let a third.

You in trouble.

It will TECHNICALLY still work at whatever version Nvidia cuts off support at, which is pretty soon for GTX cards (they’ve already cut off the mobile counterparts). So you’ll stop getting updates, but it should still work as long as that driver is made available still in some form that whatever distro you are using can install it, or you compile it from scratch. I would not trust Nvidia’s installer to still be working by then in it’s current form because it’s a MESS.

Rooting means you’re disabling or bypassing the hardware encryption signing for modules that are built for the device you’re on. If things aren’t signed, and something checks to ensure that they ARE signed, you’ll run into problems.

Same way you made it work on Deck, again. SteamInput will map controllers to input devices detected by Dolphin, and you map to whatever you need to map to in whatever way you want.

Same as it is on Deck. It’s just a Deck in a different form factor from the user standpoint. Everything will operate the same.