justJanne

joined 1 year ago
[–] [email protected] 0 points 9 months ago (3 children)

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.

[–] [email protected] 4 points 9 months ago (5 children)

Good ears? the question is when, not where, and the answer is half a lifetime ago.

[–] [email protected] 18 points 9 months ago* (last edited 9 months ago) (2 children)

It's just like those shitty recipe sites that tell you their grandma's life story for hours before giving the recipe. Get to the point, who cares about the anecdotes of some writer?

I don't want to connect with everyone always everywhere. It's just like small talk, which may be acceptable or even essential in some cultures, while considering rude and wasteful where I'm from.

[–] [email protected] 1 points 9 months ago

Not really. Avatar 1 revolutionised motion capture, which actually allowed Marvel's entire MCU to exist the way it did.

Avatar 2 improved that yet again, which we'll likely see in future superhero and scifi movies.

[–] [email protected] 4 points 9 months ago* (last edited 9 months ago)

4 different "buy nitro" "try new animated stickers" "have you bought a new profile background yet?" popups at the same time are also ads.

[–] [email protected] 9 points 9 months ago (4 children)

Fast? Clean? The new app is a stuttery, cluttered mess with more ad popups than a 2010 video streaming site and more framedrops than crysis. Until a few days ago I still used the oooold app and it was much better.

[–] [email protected] 0 points 10 months 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.

[–] [email protected] 13 points 10 months ago (2 children)

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.

[–] [email protected] 14 points 10 months ago* (last edited 10 months ago) (2 children)

Considering that reading source code can take a long time

You'll get faster over time, until reading code is faster than reading documentation, as code will always represent what's truly happening, while docs are frequently outdated.

In a language the user isn't familiar with

If you're not that familiar with the language, it's likely you won't be contributing to the project. Open source projects usually to have quite limited resources, so they tend to optimize docs and dev UX for people who are likely to contribute.

[–] [email protected] 17 points 10 months ago (10 children)

Also note that even a dual boot system is leaky. A kernel level anticheat has enough power to do firmware upgrades on peripherals or the UEFI, so a badly behaving kernel level anticheat could easily take over your entire system in a way that can never be gotten rid of.

[–] [email protected] 1 points 10 months ago (1 children)

So how do you juggle having to see dozens of windows at the same time then?

[–] [email protected] 5 points 10 months ago (3 children)

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.

view more: ‹ prev next ›