sudotstar

I haven't adopted this kind of setup, mainly because Proton just does such a good job I have almost zero need for Windows, but my plan for eventually doing something like this was to also maintain a passthrough Linux VM for any GPU-intensive work on that side.

When I realized that the practical end-state of my system would mean I'd just be running things from within the Linux VM 98% of the time (games that can run on Linux) I kind of dropped the idea.

For me it's always been after I tried to resize a partition.

I recommend using whatever is the "least hands-on" option for your boot drive, a.k.a your distro default (ext4 for Debian). In my admittedly incompetent experience, the most likely cause for filesystem corruption is trying to mess with things, like resizing partitions. If you use your distro installer to set up your boot drive and then don't mess with it, I think you'll be fine with whatever the default is. You should still take backups through whatever medium(s) and format(s) make sense for your use case, as random mishaps are still a thing no matter what filesystem you use.

Are you planning on dualbooting Windows for games? I use https://github.com/maharmstone/btrfs to mount a shared BTRFS drive that contains my Proton-based Steam library in case I need to run one of those games on Windows for whatever reason. I've personally experienced BTRFS corruption a few times due to the aforementioned incompetence, but I try to avoid keeping anything important on my games drive to limit the fallout when that does occur. Additionally if you're looking to keep non-game content on the storage drive (likely if you're doing 3D modeling work) this may not be as safe.

I think moving the folder under ~/.local before splitting the cache folders out is a bad idea. Many people will have specific backup or sync solutions in place that want to include config, recreate data, and exclude cache, so the XDG spec has separate locations for them.

Windows's dedicated Saved Gamed folder is within the same user-specific directories that Documents and AppData are in, and would still allow for game saves to be user-specific.

I have played the original, and will be playing the remaster, though not on Switch, I already own the Japanese version on Steam which will be patched with the localization upon release in the West.

It's quite a fun, fast-paced game, as Falcom action RPGs tend to be. Being a PSP title originally, I think the game format works well for shorter, pick-up-and-play sessions, making it ideal on devices like the Switch and Steam Deck. No context or experience with the wider Trails series necessary, all connections to the mainline series are just simple references and the game has a standalone story (unless you're deep in the rabbit hole of lore crack theories).

Being incredibly car-centric is probably our biggest issue in my opinion. If you're expecting to be able to use public transit or even walk to basic necessities, and are looking to purchase a house, you'd likely be looking at areas outside of your price range, generally within highly urbanized city centers. Owning a car is very much the norm here, even within those urban environments.

Sure, modding the device will always have a niche interest, and people doing it just because they can, but if the price point of such a device is comparable to a Switch (easily hackable) or even a Steam Deck (outright open for you to do whatever with no barriers in place), would this device have any practical benefit for that kind of stuff over the alternatives?

I think it will continue to have some niche benefit, especially if modding the device still retains its presumably "first party, easy" path to streaming games from a local PlayStation, and for people who would want to keep the presumably better-quality and 1080p display over what's found in the Switch and Steam Deck, but I think someone looking to get something to primarily use with Steam Link or other such services have better (incl. first-party) options for that use case.

I was referring to the niche-but-growing segment of handheld game devices primarily designed for cloud/streaming services, like the Logitech G Cloud or more "traditional" handheld gaming devices like the Switch or Steam Deck, not necessarily all generic-tablet Android devices.

We still don't know the price of the device. I think this device has to really target a low, potentially subsidized, price point in order to be worth it over existing handheld devices capable of streaming (or even running games locally), and if that's the case, it may suffer from the Amazon Fire problem of being incredibly locked down and not seeing as large a development community as would be necessary to achieve a "no restrictions" Android setup. If Sony is subsidizing the device, they would really prefer it if consumers stay within their media ecosystem rather than having the ability to go out and use and/or pay for services that don't allow Sony to recuperate their losses.

It is also possible that the device seen here is just running Android for testing purposes, and the final device will ship with something more locked-down. This seems unlikely due to being far more effort than just using common tablet hardware and shipping Android, but Sony may prefer to do that to achieve more control over the device.

This is why I'm intentionally staying away from high-refresh-rate displays until I can feasibly upgrade everything I use to that standard (phone, TV+consoles, desktop monitors, etc). I don't know exactly what I'm missing out on and ignorance here is bliss.

Unless LOS or a different custom ROM can re-enable the "old" work profile behavior, having access to the latest version of Android might be a detriment compared to an older version that still at least receives security updates (as I assume the Pixel mentioned here does).

I run LineageOS myself, and while I don't think this change is enough of a dealbreaker to prevent me from ever updating past LOS20 if this change isn't addressed somehow in either AOSP or LOS, it will make me less enthusiastic about immediately jumping to LOS21 the moment it's made available to my device.