code witch - she/they
- 10 Posts
- 191 Comments
are these purists who have never heard of Proton here in the room with us, OP?
3·30 天前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 their takes a lot, they didn’t hesitate to call out fossbro bullshit.
they need a break though. no way around it.
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?
fuck gatekeepers. the linux kernel doesn’t deserve new, talented people bringing fresh, useful and modern approaches to the project; their time and effort is only wasted there. i know it’s not right, but part of me wishes linux rots and something better takes its place.
bitterness aside, i hope marcan gets the rest he needs. i wish him the best.
ikr, it makes the horrors just a little more bearable ✨
oof this is brutal. but a good analysis.
at the end of the day it, no matter what good uses people might have for this tech, it’s hard to reconcile the fact that it’s also being used by the worst possible people, with the worst possible intentions, in the worst possible ways.
this matches my experience too. good IDEs or editors with LSP support allll the way.
also wanna add that it’s weird to me that we turn to LLMs to generate mountains of boilerplate instead of… y’know, fixing our damn tools in the first place (or using them correctly, or to their fullest) so that said boilerplate is unnecessary. abstractions have always been a thing. it seems so inefficient.
ragebait used to be believable 🚬