A common pattern with ports and patches is that one person writes them, then life happens and they walk away. For a fork to succeed, there really needs to be more than one person willing to hop on the treadmill and keep doing the work to get it running.
For what it's worth, the rumbling about dropping Go on Plan 9 isn't so loud, but it's there. It could probably use some help, if people want to keep using Go on Plan 9. Quoth Willow Liquorice <[email protected]>: > I've been keeping an eye on Zig and noticed this recently-merged branch > from Andrew Kelley, removing support for Plan 9 executables in the > linker (https://github.com/ziglang/zig/pull/24803). > > "Not worth the maintenance burden." > > I suspect the feeling is mutual right now, given that Zig code rots very > quickly if it uses the stdlib. > > I read Ron Minnich was able to get Zig building through vmx acrobatics. > That process is unaffected by the merge as, IIUC, it targets a Linux VM. > This is a blow to self-hosting Zig on Plan 9, though. > > - Willow > > P.S. "The operating system is not that interesting" my foot! ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Ta74fdc99bf0151a0-M44fd6451a5984e7855ebe879 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
