arisunz

couldn't tell you, never used either.

well, that's not entirely true. i self host Forgejo and Woodpecker, which i think (might be wrong here, especially because Forgejo does have its own CI/CD now) is what Codeberg offers. anyway, it's been OK for the automatic deployments of my little projects. pipeline configuration was flexible and straightforward enough to surprise me in a good way.

came here to say exactly this.

also y'all, consider donating to Codeberg if you have an account there, they've been getting hit nonstop the last week or so by chuds.

i liked his takes a lot, he didn't hesitate to call out fossbro bullshit.

dude needs a break though. no way around it.

"hmmmm in this kirby game..... we will have THREE puzzles where you have to hit SOME bombs but not ALL to get the bonus item..... ah yes excellent job team!"

~~pls dont kill me i love kirby games~~

no sorry, im here to incapacitate rogue deities, not to redefine how we name these fucking things

aughhhhhh here's your upvote. git out.

see, i could maybe agree with this if it weren't for the amazing work from R4L that already has been and continues to be done, despite subsystems maintainers putting their foot down and going "Not In My Back Yard, bucko!". how many more maintainers does R4L have to lose before Linus realizes he might need to take a stance as a project lead?

ah, fair enough. i guess that's kind of the thing with potential dogwhistles. if you know, you know.

i scrolled half a wiki page to link to... facts.

we don't live in the 80s though. we live in contemporary times where things have different now meanings to what they did 40 years ago. meanings that might be influenced by recent happenings. hope that helps!

why they feel it’s Linus’ responsibility to make Rust happen in the kernel

who does? are you talking about marcan? because as far as i can see, what they're asking for is for linus to make a stance and actually say whether R4L is a thing they want or not. because linus' attitude so far has been "let's wait and see" which hasn't been all that helpful, as said in the blog post.

knowing where "thin blue line" comes from, you don't see anything wrong with a maintainer randomly dropping it on the mailing list?