gyptazy

@gyptazy@gyptazy.ch

Believer in the power of open-source & community-driven innovation.

Former AS20621 NetOp that loves FreeBSD & illumos. Currently mostly in DevOps & developing (Python, Rust). Contributes to & . Evaluating and production usage of hardware/software.

Projects:
* BoxyBSD.com - A free VM hosting service to provide some value back to the community.
* manpageblog.org - A static blog generator in manpage design.
* QualvoSec - A security patch management tool.
Bloghttps://gyptazy.ch
GitHubhttps://github.com/gyptazy
Xhttps://twitter.com/gyptazy
0 ★ 0 ↺
in reply to »

gyptazy »
@gyptazy@gyptazy.ch

@zygoon@fosstodon.org yes and no... Regarding the subset, it's still possible to also package the missing subset (which we frequently did in the past) and also most of them moved upstream - so everyone benefited from this approach. But yeah, you can't use bleeding edge features but this also applies more or less everywhere - even when you're depending somewhere on a specific go version etc.

That's more a topic regarding the software lifetime cycle and feature set.

History