This is a regular occurrence and honestly we need to stop recommending dual boot. Use separate drives if you need to, but sharing the same drive is destined to brick something

for sure, I thought the hire was weird in the first place. Did just mean that it doesn’t look like GNOME fired her lol.

She did do some good stuff but GNOME really did get what they asked for

Rarely, but I’ve contributed to a couple that I use.

Also, just a note that writing big reports is a valid contribution! It can really help both the regular maintainers finding and fixing bugs, but also gives new devs more potential work to pick up for first contributions.

In theory they (or someone else) could just bundle an open source copy of the assets no different to having a different texture pack in a game.

There’s some decent forks currently so I wouldn’t worry about the technology, but yeah the organisation is probably going to implode and reorg soon

Yeah I didn’t realise they were rar formats from how they show up on disk - Usually people name.their.torrents.like.this so it fucks up typical file name conventions.

I’ll keep that in mind too, thanks! Not using qbitmanage yet though I’ll have to look into that 👀

EDIT: There’s a fix. https://unpackerr.zip Automatically unzips these rar containers into coherent files for importing via sonarr/radarr. I suppose you can do this manually with tar if you’re brave.

TLDR you might be interested in the rust-based scheduler one of the Canonical Devs released as a PoC. Seemed to be designed similar to your needs of keeping the system (particularly games) responsive even whilst running heavy tasks like kernel compilations. You can swap out schedulers at run time on Linux iirc?

https://www.phoronix.com/news/Rust-Linux-Scheduler-Experiment

don’t.

wonder what awful shit they’re about to be outed for doing to have randomly added this clause

Tim refuses to stop shooting himself in the foot against Valve. More news at 11

I think a lot of new indie Devs, having little knowledge of the actual state of the industry, see a publisher offering them big money to make video games (their dream!) and ignore (or lack resources to properly interrogate) the fine print. There are countless examples of publishers simply destroying indie Devs on a whim like this.

Not if you call it GNU/Linux 🤓☝️

amateur. I just manifest the correct IP address for my desired resource and fetch it with curl

that $0.01 pay rise could’ve kept someone off the streets!

I didn’t say you have to know everything, just like I don’t know everything in my house and how it works, but I do know how to do basic repairs so I don’t pay loads of money for a guy to come and unclog a drain. I know how to reset my circuit breakers, how to change a fuse, how to change a lightbulb.

That’s what the terminal is. No one here is telling you to write a bootloader in assembly or meticulously study kernel environment parameters. No one advocating for basic knowledge of a terminal likely has knowledge on subnet masks, compilers, or other low level systems that a modern Linux abstracts for you.

But! I know how to update my packages from a terminal. I know how to install a package outside of a repository, or one that’s not listed on my graphical package manager. I know how to export an environment variable to get my software to work how it should.

That’s what “knowing the terminal” gives you. It’s a basic skill that unlocks you from being a mere “user” of a system to an owner of a system. I don’t think everyone will ever need the terminal, but there are people who are replying to me that seem to have a genuine fear that people have knowledge of their computers in a meaningful way.

Knowledge is autonomy for whatever you do, and there’s a reason why the most profitable of systems are the very systems that are locked down abstracted and “user friendly” in all ways that harm a user’s rights and freedoms.

I don’t think it’s a theory rather than an objective fact. A lot of “traditional” computer skills have almost totally gone extinct because consumer devices are designed to hide as many system features from you as possible.

The saving grace is that even being raised without it, you end up needing these skills to become a developer of any decent calibre. That gives at least some route for these skills to transfer to new generations.

If you want to use Linux without the terminal nowadays it’s pretty easy. But also I think the fear of the terminal is part of the culture that consumer electronics have cultivated where people don’t know (or want to know) how their systems work.

If you take the time to use it, not only can you save yourself time, but also learn a lot more about how you can fix things when they go wrong! That kind of knowledge gives you so much more ownership of your system, because you don’t have to rely on your manufacturer to solve problems for you.

Same for Mac and Windows too, the terminal is something that shouldn’t be necessary, but when it is it helps to know what you’re doing. :)

I installed mint and zorin on virtual machines (theyre easy to set up in windows with virtualbox) and then just put them fullscreen and used em like my actual computer for a bit. Very useful for learning stuff without the commitment of a proper install.

The trick to writing a JavaScript web app is that first you consider literally any other technology to solve your problem and only then consider using javascript.