zlacker

[parent] [thread] 8 comments
1. fp64+(OP)[view] [source] 2025-06-06 12:02:49
This is hilarious, can totally understand the fork and will take a look
replies(1): >>firest+O1
2. firest+O1[view] [source] 2025-06-06 12:17:41
>>fp64+(OP)
Enrico seems like a prolific maintainer but also a frustrated one.
replies(2): >>const_+AW4 >>bmacho+Mgl
◧◩
3. const_+AW4[view] [source] [discussion] 2025-06-08 19:20:33
>>firest+O1
From what I've seen he hasn't actually addressed any bugs or features in xorg... ever. I'm not sure if that even grants the title of "maintainer". Shuffling code around is fun and easy, but not necessarily productive.
replies(1): >>firest+Wn6
◧◩◪
4. firest+Wn6[view] [source] [discussion] 2025-06-09 13:50:14
>>const_+AW4
He is regarded as “most active Xorg developer”

https://youtu.be/iwaaSatk0pI?si=imqGgETnkou_uZUz

replies(1): >>const_+BQ6
◧◩◪◨
5. const_+BQ6[view] [source] [discussion] 2025-06-09 16:42:58
>>firest+Wn6
Yeah dumping a bunch of commits that do nothing might be considered "active" by some people. I wouldn't consider it active.
replies(2): >>firest+DX6 >>bmacho+Vgl
◧◩◪◨⬒
6. firest+DX6[view] [source] [discussion] 2025-06-09 17:21:08
>>const_+BQ6
Better than current Xorg activity ;) (which is very low)
replies(1): >>const_+zl7
◧◩◪◨⬒⬓
7. const_+zl7[view] [source] [discussion] 2025-06-09 19:14:15
>>firest+DX6
Eh, I don't know. There's an argument to be made that no changes is preferable to breaking changes with little or no benefit.
◧◩
8. bmacho+Mgl[view] [source] [discussion] 2025-06-15 11:22:59
>>firest+O1
Literally everyone but one person are constantly shittalking and trying to gaslight him.
◧◩◪◨⬒
9. bmacho+Vgl[view] [source] [discussion] 2025-06-15 11:24:37
>>const_+BQ6
What are the options?

   a) noone looks at the code
   b) they make random user-facing changes
   c) random churn that makes the code better (preferably with as few user-facing modifications as possible)
IMO the best option is c). Guy is literally doing the single best thing possible.
[go to top]