I predict that in 5 years time 95% of terminal sessions will be on libghostty using their extended command set. Microsoft will decry this monoculture and try to get people to use their terminal emulator. IBM will buy libghostty and start charging enterprise licence fees for using those extended commands.
Wow this is a major milestone, congrats! What is Zig used for in the library? For something so stable is the choice of Zig going to lead to friction when the language will have incompatible changes again?
The stability layer exists at the C ABI level: any churn on the Zig side is completely opaque becuase it's all abstracted away behind the C layer which is what consumers will actually use.
Yes of course the C API hides Zig, but the library itself will require some specific version of the Zig language to build, since Zig is not stable. I guess this will put some constraints on packagers if nothing else
Student | an hour ago
I predict that in 5 years time 95% of terminal sessions will be on libghostty using their extended command set. Microsoft will decry this monoculture and try to get people to use their terminal emulator. IBM will buy libghostty and start charging enterprise licence fees for using those extended commands.
conartist6 | 57 minutes ago
You seeing any adoption of CSTML-based terminals in that crystal ball?
gignico | 10 hours ago
Wow this is a major milestone, congrats! What is Zig used for in the library? For something so stable is the choice of Zig going to lead to friction when the language will have incompatible changes again?
lalitm | 10 hours ago
The stability layer exists at the C ABI level: any churn on the Zig side is completely opaque becuase it's all abstracted away behind the C layer which is what consumers will actually use.
gignico | 10 hours ago
Yes of course the C API hides Zig, but the library itself will require some specific version of the Zig language to build, since Zig is not stable. I guess this will put some constraints on packagers if nothing else