#fossinaction — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fossinaction, aggregated by home.social.
-
"A. Pollock" (debian.org), had an idea for a very useful feature (thx, btw! 🌻️) for molly-guard: Prevent accidential shutdown of distributed and virtual #GNU #Linux PCs by #FQDN.
"F. Marier" (debian.org), confirmed merging it back upstream.
Meaning: **From /then on/ that use-case is solved. for all IT.**
For good. #NoNeedToUpdate ☮️ 🗿> I'd love to see stories and best-practices like that at schools and unis.
> Real people, no bullshit. -
"A. Pollock" (debian.org), had an idea for a very useful feature (thx, btw! 🌻️) for molly-guard: Prevent accidential shutdown of distributed and virtual #GNU #Linux PCs by #FQDN.
"F. Marier" (debian.org), confirmed merging it back upstream.
Meaning: **From /then on/ that use-case is solved. for all IT.**
For good. #NoNeedToUpdate ☮️ 🗿> I'd love to see stories and best-practices like that at schools and unis.
> Real people, no bullshit. -
"A. Pollock" (debian.org), had an idea for a very useful feature (thx, btw! 🌻️) for molly-guard: Prevent accidential shutdown of distributed and virtual #GNU #Linux PCs by #FQDN.
"F. Marier" (debian.org), confirmed merging it back upstream.
Meaning: **From /then on/ that use-case is solved. for all IT.**
For good. #NoNeedToUpdate ☮️ 🗿> I'd love to see stories and best-practices like that at schools and unis.
> Real people, no bullshit. -
An analysis of Audacity forks in 2024.
The main contributors to Audacity are Paul (5k), and James (2k, but stopped contributing after Muse Group).
The main contributor to Tenacity is 'generic-pers0n', and this account has apparently only begun commits after the fork. A daunting task!
My analysis is that Tenacity is "alive" but not "well". Since no Audacity contributors are active, this fork has an uphill battle!
#foss #FossInAction #fosstodon #programming #github #audacity #tenacity #cpp
-
An analysis of Audacity forks in 2024.
The main contributors to Audacity are Paul (5k), and James (2k, but stopped contributing after Muse Group).
The main contributor to Tenacity is 'generic-pers0n', and this account has apparently only begun commits after the fork. A daunting task!
My analysis is that Tenacity is "alive" but not "well". Since no Audacity contributors are active, this fork has an uphill battle!
#foss #FossInAction #fosstodon #programming #github #audacity #tenacity #cpp
-
An analysis of Audacity forks in 2024.
The main contributors to Audacity are Paul (5k), and James (2k, but stopped contributing after Muse Group).
The main contributor to Tenacity is 'generic-pers0n', and this account has apparently only begun commits after the fork. A daunting task!
My analysis is that Tenacity is "alive" but not "well". Since no Audacity contributors are active, this fork has an uphill battle!
#foss #FossInAction #fosstodon #programming #github #audacity #tenacity #cpp
-
An analysis of Audacity forks in 2024.
The main contributors to Audacity are Paul (5k), and James (2k, but stopped contributing after Muse Group).
The main contributor to Tenacity is 'generic-pers0n', and this account has apparently only begun commits after the fork. A daunting task!
My analysis is that Tenacity is "alive" but not "well". Since no Audacity contributors are active, this fork has an uphill battle!
#foss #FossInAction #fosstodon #programming #github #audacity #tenacity #cpp
-
An analysis of Audacity forks in 2024.
The main contributors to Audacity are Paul (5k), and James (2k, but stopped contributing after Muse Group).
The main contributor to Tenacity is 'generic-pers0n', and this account has apparently only begun commits after the fork. A daunting task!
My analysis is that Tenacity is "alive" but not "well". Since no Audacity contributors are active, this fork has an uphill battle!
#foss #FossInAction #fosstodon #programming #github #audacity #tenacity #cpp
-
@reduz has written a technically robust response to @SamPruden: https://gist.github.com/reduz/cb05fe96079e46785f08a79ec3b0ef21
Respectful and interesting follow-up conversation in the comments.
TLDR: Sams article focused by chance on a "pathological" example. Also, despite Sams original conclusion, large-scale performance upgrades are definitely possible, *without* dropping GDScript, and without rewriting the engine :)
-
@reduz has written a technically robust response to @SamPruden: https://gist.github.com/reduz/cb05fe96079e46785f08a79ec3b0ef21
Respectful and interesting follow-up conversation in the comments.
TLDR: Sams article focused by chance on a "pathological" example. Also, despite Sams original conclusion, large-scale performance upgrades are definitely possible, *without* dropping GDScript, and without rewriting the engine :)
-
@reduz has written a technically robust response to @SamPruden: https://gist.github.com/reduz/cb05fe96079e46785f08a79ec3b0ef21
Respectful and interesting follow-up conversation in the comments.
TLDR: Sams article focused by chance on a "pathological" example. Also, despite Sams original conclusion, large-scale performance upgrades are definitely possible, *without* dropping GDScript, and without rewriting the engine :)
-
@reduz has written a technically robust response to @SamPruden: https://gist.github.com/reduz/cb05fe96079e46785f08a79ec3b0ef21
Respectful and interesting follow-up conversation in the comments.
TLDR: Sams article focused by chance on a "pathological" example. Also, despite Sams original conclusion, large-scale performance upgrades are definitely possible, *without* dropping GDScript, and without rewriting the engine :)
-
@reduz has written a technically robust response to @SamPruden: https://gist.github.com/reduz/cb05fe96079e46785f08a79ec3b0ef21
Respectful and interesting follow-up conversation in the comments.
TLDR: Sams article focused by chance on a "pathological" example. Also, despite Sams original conclusion, large-scale performance upgrades are definitely possible, *without* dropping GDScript, and without rewriting the engine :)