It’s incredibly fast, has the features you would want like tabs/splits, maintains comprehensive compatibility, and is written cleanly in Zig. What’s not to like?
Most terminal emulators are in fact slow and they can be a huge bottleneck if you run complex TUIs or workloads that print a lot of output.
Ever written a program that was extremely slow only for it to run instantly after removing your debug print statements? That’s because your terminal is slow.
Fast terminal emulators already exist, but they notably refused to add tabs/splits and overall tended to be quite janky. Ghostty merging these features may not be the most groundbreaking innovation, but a high quality piece of software that can drop-in replace something you use daily with some cool improvements is something to be excited about to me. :-)
I agree that many small businesses jump to Kube too early. If your entire app is a monolith and maybe a few supplementary services, then Kube is massive overkill.
But many people also tend to overlook all of the other benefits that suddenly become very easy to add when you already have Kube, such as a common way to collect logs and metrics, injecting instrumentation, autoscaling, automated certificate handling, automated DNS management, encrypting internal network traffic, deployment tools that practically works out of the box, and of course immutable declarative deployments.
Of course you can build all of this yourself, when you need it, but once you have the foundation up and running, it becomes quite easy to just add a helm chart and suddenly have a new capability.
In my opinion, when the company it big enough to need a dedicated ops team, then it’s big enough to benefit from Kube.
Something like heroku is better for out of the box stuff like logging and autoscaling. Some companies like banks have to have their own data center. But they should write their own “tools”.
Must be fun looking at 10 pods and pretending to be in control of Google search by proxy. Autists have a peculiar way of day dreaming, as they’re extremely limited in imagination. They always seek artificial complications to cover up the fact that what they’re doing is actually not far from trivial, and without gatekeeping a school kid would be capable of doing.
I must be removed. People are excited about a terminal emulator. Why?
It’s incredibly fast, has the features you would want like tabs/splits, maintains comprehensive compatibility, and is written cleanly in Zig. What’s not to like?
I’ve never seen a slow terminal emulator. Most terminals have tabs and splits. Never experienced compatibility issues. Don’t care about Zig at all.
Are these all the reasons? Another toy software written out of boredom.
Most terminal emulators are in fact slow and they can be a huge bottleneck if you run complex TUIs or workloads that print a lot of output.
Ever written a program that was extremely slow only for it to run instantly after removing your debug print statements? That’s because your terminal is slow.
Fast terminal emulators already exist, but they notably refused to add tabs/splits and overall tended to be quite janky. Ghostty merging these features may not be the most groundbreaking innovation, but a high quality piece of software that can drop-in replace something you use daily with some cool improvements is something to be excited about to me. :-)
Thanks, this clears things up. I didn’t know what exactly was making print IO slow.
I don’t use any complex TUIs. Pretty much everything is CLI or GUI. Which TUIs did you have in mind that were slow?
I’d like to test this soon. I’ll look for a modern TUI framework.
On slow terminals k9s can be rather sluggish when scrolling through the lists
Fair. I hate kube though. Most companies run just 10 pods because they cargo cult google. The complexity of it is completely unjustified
The right tool for the right job.
I agree that many small businesses jump to Kube too early. If your entire app is a monolith and maybe a few supplementary services, then Kube is massive overkill.
But many people also tend to overlook all of the other benefits that suddenly become very easy to add when you already have Kube, such as a common way to collect logs and metrics, injecting instrumentation, autoscaling, automated certificate handling, automated DNS management, encrypting internal network traffic, deployment tools that practically works out of the box, and of course immutable declarative deployments.
Of course you can build all of this yourself, when you need it, but once you have the foundation up and running, it becomes quite easy to just add a helm chart and suddenly have a new capability.
In my opinion, when the company it big enough to need a dedicated ops team, then it’s big enough to benefit from Kube.
Something like heroku is better for out of the box stuff like logging and autoscaling. Some companies like banks have to have their own data center. But they should write their own “tools”.
Must be fun looking at 10 pods and pretending to be in control of Google search by proxy. Autists have a peculiar way of day dreaming, as they’re extremely limited in imagination. They always seek artificial complications to cover up the fact that what they’re doing is actually not far from trivial, and without gatekeeping a school kid would be capable of doing.
https://feddit.uk/comment/14184961
Most for wayland have no tabs.
Why is it so funny to see issues with a terminal running in 4k? It never crossed my mind that some folks do that.
Konsole has no tabs?
Beats me.
Konsole has all the KDE dependencies.
So? You’re limited by disk space?
Yeah, I couldn’t care less what language its written in
People gets excited to see something written in their favourite niche language.
I actually like Zig. I wish something like CUDA was available in it.