1. Soon to be
2. That’s me

Does one even have to actually write Python code, except for frontends? I’d assume you just load the model, weights and maybe training data into pytorch/tensorflow.

Then you need to ask yourself: Performance or memory efficiency? Is it worth the extra cycles and instructions to put 8 bools in one byte and & 0x bitmask the relevant one?

:3

alias yay=“yay -Pw; yay”

I’m three of those

And it takes away the ability to read issues and resolutions, which is probably 95% of what at least I have to do, from anyone and only grants it to the ones with a discord account

And, though I don’t know how good forge fed will be, if it supports writing issues, you may be able to only have a codeberg or gitlab account (or your own instance(s)), and write issues everywhere (except GitHub ofc).

And it also doesn’t publicly index. Is it at least possible to look at convos without an account?

> Create massive problem by using proprietary shit platform
> Try to solve problem by hacking around it

Not like source forges have whole integrated systems just for the purpose of filing, debugging and fixing issues. That are naturally indexed of course.

It would be lovely if “open source” projects just didn’t use discord.

Luckily, my Keyboard is so dirty that I need to pull off all keycaps anyway.

I love that every german says “Ich kann nicht so viel fressen wie ich kotzen will”

I hate them more than average because they e.g. abuse their patent “rights” to the max, more than other companies.

I despise all of those companies to the core. More than average.

Nein, es ist John Cena!

@Peter_Arbeitslos@feddit.org

I’m 19 and in the past, apparently.

I’m GenZ and Skibidi Rizzler Ohio

-S means sync, or to install/update a package
y means to update the local package db, so which packages are available and especially which version is newest
u means update the packages themselves

So -Sy would just get which newest packages are available, and then install eg. mesa version 6.9. However, mesa version 6.9 may depend on ligmalib 3.2. However, because you didn’t specify -u, ligmalib 3.1 is not updated to 3.2. And then you have a partial update.

Arch’s package system basically relies on all packages in all single points in time being compatible with each other. So if you look at the db now, all packages should have the correct versions of dependencies available. But if you mix different states, eg. update a few packages at 2:00 and some others at 17:00, that’s not given anymore

Yeah, only thought that halfway through lol

sudo pacman -Sy mesa vulkan-radeon (or smth like that)

Edit: Yeah, I know, Syu. I very rarely not do Syu. But /usr/bin/brain segfaulted while trying to be smart.