i find it ironic when people who finally realised systemd is flawed because it puts everything in a single bunched up place are now pushing for projects to use a "modern" development workflow, which is done by moving the project's code to a platform which serves as contribution tracker, bug tracker, code reviews, automated testing, wiki, release platform, and feature planner, and probably even more i don't know about.

like. im no genius but that's going the same direction

and no, something like forgefed isn't a solution to this

adding a component has never decreased complexity and never will

@SRAZKVT so what else do you propose?

Stick with #SysVinit?

@kkarhan @SRAZKVT There isn't just SysVinit and systemd in this world
Now we have OpenRC, dinit, runit, s6, finit...

@stilic oh that guy responded ? he's suspended on tech.lgbt so i didn't see lmao

but while i use runit right now, i wouldn't recommend it, and would instead recommend something like openrc or s6 (the devs of both are really really nice people and that's something we need in these trying times)

@SRAZKVT what about nitro?

@stilic it fits in the same niche as runit, while actually being maintained, and while it would probably be better than runit for desktop usecase, i still think s6 and openrc would be preferable

nitro is 100% what i'd go for for embedded devices or containers though, if i ever need either of those

@SRAZKVT Personally I think OpenRC is fine but S6 is kinda complex to use AFAIK
I really like Runit/S6 cuz they have a clever interface that looks unixy
@stilic also that guy COMPLETELY missed the point of my post ??? what did any of it have to do with operating system init systems ?? it was about git forges being monolithic messes, and how adding complexity to them, shockingly, doesn't make the whole better, because, well, it's now more complex and likely less reliable

@stilic @SRAZKVT yeah, but either of these basically implement either the same or a subset of #SystemD or #SysVinit.

But that's because essentially doing either manual (SysVinit) or hierachical-automated (SystemD) dependency resolution is the only way to make it any #Linux or #Unix'esque system work…

  • Including #macOS which uses #LaunchD aka. the inspiration for SystemD that doesn't get hated by #BSD fans…
Stilic 🇫🇷 (@[email protected])

@[email protected] @[email protected] There isn't just SysVinit and systemd in this world Now we have OpenRC, dinit, runit, s6, finit...

Piaille

@stilic @SRAZKVT and no, I'm not "suspended" cuz that would've meant that I could neither follow or be followed from said instance.

  • Which isn't the case…

But you do you, feel free to fight imaginary enemies so you are too preoccupied to tackle the real ones (or maybe that's just too hard/easy for you? IDK, there's a shitton of issues more important…)

  • Wishing you sincerely only the best and that you soon find some time to go #TouchGrass…

#thxbye #EOD #muted

sarah tonin :wlfBlep: (@[email protected])

@[email protected] oh that guy responded ? he's suspended on tech.lgbt so i didn't see lmao but while i use runit right now, i wouldn't recommend it, and would instead recommend something like openrc or s6 (the devs of both are really really nice people and that's something we need in these trying times)

LGBTQIA+ and Tech
@SRAZKVT i can't wait for federation issues leading to inconsistent PR states across forgejo instances

broken threads on a social media website isn't enough, we gotta have broken patch sets too

(i am forever going to be salty about this, mailing list have always been *right there*, just make a better UI for it ffs)
@navi yes yes but you see email is old and archaic and therefore MUST be destroyed /s
@[email protected] @SRAZKVT sourcehut was making great strides in that regard but development has slowed to a crawl so yeah...
@[email protected] @SRAZKVT that and drew's famous inflexibility regarding his own projects
@andrago @navi i think sourcehut is great as a proof of concept but we can do better