Kit would benefit one hardware manufacturer (nvidia) and only on big picture mode which runs like shit on nvidia
Aidk just to make it feel like steamdeck on bazzite-nvidia
Kno demand for one
Abpm only would run awfully if u have it on fullscreen
Twhich is the default and what it's intended for
Aidk i just prefer easy to change presets overlay as like plugin
Knot likely to happen through gamescope/bpm until nvidia fixes their drivers
Klike I said, zero demand
Kiirc those don't save (?)
VNvidia currently in a drag race with NVK to get gamescope support
Knvidia promised gamescope over a year ago and sat on their fat leather-clad ass
Kif NVK gets it first it's karma
VI hope NVK gets it first
VIt'd be funnier
Tit probably will
Ait would be funny as hell fr
Tnvidia is the 3rd most valuable property in the united states market rn
Tcrazy
Tthey have surpassed google and amazon
VThey'll crash and burn one of these days
VI hope
Ai watching the battle nvidia vs nvk to see who will get gamescope support first
Abut nvk already suprassed nvidia at able to run game under gamescope LOL
K6 or 7 iirc
ASo, what are the ramifications of layering? If I install an RPM for vscode or sublime text, what happens when I upgrade? I don't have any real experience with flatpaks yet.
AAlso, can I hate on Xwayland being a blurry mess with vscode on a hidpi screen? Or am I missing some env vars to fix that? 
Aoh shit, that's slick.
Asorry, I'm coming from an old school debian background, so the ostree stuff is new to me. 
A...ok, what's a copr? Is that like an AUR package that works with rpm ostree?
Hone thing that can happen if you have layered something that gets added in the base image in an update, the update will complain and you will just have to remove the layer before trying to update again
Kcopr is Fedora's version of the AUR
Kthink of it like AUR, but instead of building stuff yourself, RedHat pays to build an RPM for you
AShit I need to learn this stuff. I'm assuming I can list the layers and interact with them.
Kthe elite's dont want you to know this but the build time is free, I have 14317519 failed copr builds in my repos
Halso layering will slow down updates since the layers have to be reapplied to the image after the base image is updated, so use layering as a last resort
FI'd also suggest installing dev tools in a container, anyway. Keeps the base image cleaner.
Kyep, distrobox is always better when possible
ELooking at this, does it look like it would be compatible with Bazzite do you think? https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux?tab=readme-ov-file&fbclid=IwAR0zXOTBxi2KM8vQBThZIzLq9wMVUW2CvqEy-VLU6P1LR5UjE6DLQBFzYFk
GitHub
This is a project, where I give you a way to use Autodesk Fusion 360 on Linux! - cryinkfly/Autodesk-Fusion-360-for-Linux
AI'm looking into that, as well as toolbox. Kinda cool that I could create a distrobox from docker.io/library/ruby:3.3.0.
KDistrobox I prefer to toolbox because of distrobox-export
K
Mthe real abbreviation is so much sillier, “cool other package repo” lmao
AI'm so new, I have no opinion on either, so happy to use distrobox.
ASo, does anyone here run gui apps out of distrobox containers?
FEvery day. VSCode, a dedicated Twitch app, Looking Glass for my Windows VM, etc.
P
Hevery day here too
Hall my development happens in distrobox, i use vscode flatpak to interact with it
AThat's the pattern I'm seeing. Ok, just don't want to swim against the current here.
