Even half an hour next to the PA without special ear plugs is enough to permanently harm your hearing.
Even half an hour next to the PA without special ear plugs is enough to permanently harm your hearing.
What you’re describing used to be right under X11, but under Wayland the compositor handles all rendering itself. For Gnome that’s mutter, which is also maintained by the gnome project.
Seriously, stop being an asshole. Coil whine is a well-documented behaviour that creates a loud, high pitched noise.
As coil whine is at the very limit of what human hearing can accomplish, it doesn’t take much until you’re unable to hear it. So you’re likely too old or went to too many concerts to be able to hear it.
Good ears? the question is when, not where, and the answer is half a lifetime ago.
Don’t SteamVR tools work on linux as well? Not that it’d help in your situation, where you’re stuck with proprietary GPU drivers and proprietary VR tools.
Why so? AMD supports Wayland just fine, while having good enough performance. As a VR dev, AMD still including a USB C port on GPUs should actually be even more convenient for you.
So how do you juggle having to see dozens of windows at the same time then?
I’m a software dev as well.
But I often layer multiple windows in the same tile of the screen. e.g. I may have the IDE with the software I’m working on in one tile, the IDE with the library source code I’m working with in the second tile, and a live build of the app in the third tile. But I’ve also got documentation, as a website, in the same tile as the IDE with the lib’s source.
Now when I switch between the IDE with the lib’s source, and the browser with the lib’s documentation, I only want that tile to change. No problem, with KDEs taskbar and window switcher I can quickly do that.
But when using the applications menu on Gnome I get a disrupting UI across all screens that immediately rips me out of whatever I was doing.
Why’d you have to use TC? KDEs dolphin can do all that natively.
Personally, configuring KDE was much simpler and more robust compared to the dozen addons I needed for Gnome, which also broke every now and then after updates.
I tried that, but IMO it’s much simpler and more robust to just configure KDE than to install a dozen Gnome extensions that end up broken after updates anyway.
Unless you’re writing ruby on rails on a 13" macbook, you’ll run into Gnome’s limitations when working.
Gnome is in many ways so focused that it makes a lot of productivity use impossible. You always have to open the menu to launch software, you’ve got no system tray, and worst of all, Gnome apps are so simplified that you constantly run into the limitations when using it productively.
When working with dozens of windows open at the same time across multiple monitors, I’m a fan of KDE. And KDE apps tend to also have all the extra features I need to handle weird situations, files, and edge cases.
The 50€ Patreon tier perks include “everything ad-free”. And there’s no repo or source available anywhere.
WTF
Just go ahead with the tutorial. Kotlin is basically identical to Java with only tiny changes, and you can just look those up whenever you see something new.
“just works” if you’ve got the fps set to 60 on an M1/M2 macbook and update the OS, you’ve bricked it.
Better laptops tend to put the wifi antenna in the display, so it’s far away from the USB ports when in use. Obviously that’s not compatible with ultra thin laptops.
Badly shielded USB3 causes RF leaks at 2.4GHz. use 5Ghz WiFi or better shielded devices.
I still hope it’s just a driver or configuration issue, for now I just dual boot for resolve, but that’s obviously not a long term solution.
Sadly even Resolve Studio doesn’t support h264 all-intra as used in Sony’s XAVC-I and XAVC-S-I on Linux, which sucks.
With XAVC-I CineEI Slog footage the metadata is enough that Resolve treats it as Raw (in fact, it’s more flexible than braw). So losing this functionality really hurts.
It would be, if you use macOS on an intel CPU with an AMD GPU.
But porting it to an entirely different CPU and GPU architecture with entirely different graphics API (Metal) makes no sense whatsoever.
That’s definitely wrong. You should follow danielle’s mastodon, she’s working on elementary all the time.