Timeline
Post
Remote status
Fetching context…
This post replies to something we haven't fetched yet. We'll try to pull in the missing thread context in the background.
@s8n the problem is in the last line:
> We don’t do this just because it’s the “right” thing to do, but also because it’s the smart thing to do.
what's smart about not merging 4x improvements, because you hope that you get more contributors that way? a very shaky assumption, too.
> We don’t do this just because it’s the “right” thing to do, but also because it’s the smart thing to do.
what's smart about not merging 4x improvements, because you hope that you get more contributors that way? a very shaky assumption, too.
Replies
5
@mischievoustomato @s8n they'll get all the great contributors, of course
@lain @s8n @mischievoustomato and those great contributora won't need to forsake the use of a novel, interesting tool because of the maintainers' zeal to quash that tool, meaning the same excellent contributors will be even more excellent in their work on the fork.
@lain @s8n a lot of these people are basically artniggers for software. they care less about objective stuff like "does it compile" and "does it run" and "what are the performance / efficiency characteristics" and more about the guy who wrote this or that line of code. they think a public project is like a digital CHAZ where we just need to get along and have fun, man.
@lain @s8n not a lot of people out there shiping zig and doing a type 1[1] gives them an audience to grand stand about.
that being said if i see the coding agent shitting directly to the repo i'm giving you the side eye
[1]: https://iceworks.cc/blog/uctd/
that being said if i see the coding agent shitting directly to the repo i'm giving you the side eye
[1]: https://iceworks.cc/blog/uctd/