Also I just tried Ghostty for the first time. With iTerm2 and the Zsh/Powerlevel10k theme, there's an extremely brief but perceptible lag from running a command and the render. In ghostty it feels actually instant.
"How much content is in this window"
and
"Where am I in that content"
I still use it daily but it means I have to switch tools for certain things, and reading log files or log output is one of the more common reasons I switch.
I should probably look into trying to get the scrollback info into my statusline, No idea how easy or hard that is - so if someone has done it, feel free to shoot me pointers.
I always was on the camp of "tail -f file.log" but since discovering this app, I saw the light.
My terminal history is normally huge, and the log output would be some unknown percentage of the total scrollable history.
Or do you mean when you inevitably forget? Well then yeah you're at the mercy of your terminal but as others mentioned ghostty has a hack to help as well as some other terminals. But this should also help reinforce why you should pipe more often and write to files (or tee). It sucks but not making the same mistakes in the future and learning better habits will help you write better code and use better practices.
But that's the age old problem of "you can't analyze the data you didn't record" and that's a footgun you'll experience in every programming language, every experiment, and across many parts of life. Better to record and throw it away than not record and regret it.
It IS recorded. It's right there in scrollback (Literally the default buffer to record). It's easily accessible with most tooling, including nice scrolling, mouse support, find/search, etc...
Except in Ghostty, it's not so accessible. No find, no scrollbars.
I end up having to dump it into another tool, which at least they make pretty easy (ex: https://ghostty.org/docs/config/keybind/reference#write_scro...).
Although deciding when to do that would be easier if I had a better indicator for just how much scrollback content exists. Ex - if it's 3 pages... I'll just scroll through it. If it's 3000 pages... time to dump to file.
So no - by default I use a pager... just about never. Why would I when I have absolutely everything in scrollback by default 99.9% of the time?
---
Don't confuse your preferences with "correct" :P
I'm doing just fine with code and best practices, I'm simply stating that this is a rough edge on an otherwise lovely tool.
> Don't confuse your preferences with "correct" :P
Don't overlook the point by fixating on a technicality > I'm doing just fine with code and best practices
Yet, you aren't following best practices > So no - by default I use a pager... just about never. Why would I when I have absolutely everything in scrollback by default 99.9% of the time?
Fewer capabilities. But those were already explained and not just by me. There really should be no need for such huge scrollbacks, you have history > I'm simply stating that this is a rough edge on an otherwise lovely tool.
No one has disagreed with this point. I think everyone even agreesPlus, they're very open about what they're doing and prioritizing. As another commenter said, it's coming soon. For the rest, open feature requests, you might have needs that others didn't think of or even realize they needed
If you don't know, you can send the log to a file, and open that file to look through it. More powerful than just a search next, as you can have instance counts, search with regexp and all the bells and whistles and it virtually stops the logging.
At first I thought the same as you, now I've become quite partial to this concept. I hope they don't remove this.
Pop the whole scrollback in helix, where I can search, select, jump around, paste stuff into a scratch buffer. It’s slick. It’s got a normal search too. But yeah I haven’t used a built in emulator search in a while I guess!
Finding mechanistic (& programmatic) sympathy counts for so so much! Shapes the arch of software so much! But it's such invisible unknown work to most people, not so overtly clear & obvious but something that constantly builds day after day, person after person, incremental 0.2% gains compounded by lack of friction.
As well as just promoting good practioners, it feels like discourse about software architecture has really fallen off. We are deep inside rabbit holes specific to this framework or that, and there's only occasional popping out to free air to bring back some observations from the burrows. Ideally we'd have many more volumes of Architecture of Open Source Applications (2011), for example, to really dive into what is, to give us some common referents to learn from and talk about. https://aosabook.org/en/
This is all so core, so worth getting deep on & looking how things are assembled, what the interfaces and modules and shapes look like, what the tradeoffs were. But it remains chiefly an arcane art, one that most developers much less most businesses haven't developed a refinement or taste for.
My observations of 20+ years in tech is that tech, collectively, chases the easiest thing to do, then complains it doesn't work without the self-reflection to realize that the very pursuit of doing/understanding as little as possible dooms the result from the beginning.
They spend years of often-needless/excessive effort to avoid weeks of studying that would move them forward.
The software world really needs people like him to drive things forward.
The previous commentor is hoping he'll move on because maintaining isn't as fun as starting? Why do you think he can't decide that for himself?
There's an old Knuth quote:
> In fact what I would like to see is thousands of computer scientists let loose to do whatever they want. That's what really advances the field.
And I think we're seeing more and more that these projects made with love are successful. That without the hyper fixation on money we can build good projects that make big changes in a world.In some sense I'm a bit envious of Mitchell but truthfully these types of things make me more question how we've constructed our society and economy. It shouldn't require one to start with wealth to be able to build things that have such an impact. What needs to be changed where we can live up to what Knuth proclaimed. I'm sure all of us have had experiences where were we given the time (and usually not much) we could make things so much better. But we make many sacrifices when we rush. Which leads to more good advice by Knuth
> If you optimize everything, you will always be unhappy.
At what point do we push back? We see that the people we really look up to did things so differently. Knuth himself expressed how detail obsessed he was, and such a claim is common among the grey breads.
Of course, things change, but are we creating a world with no wizards? Are we creating a world where we reward people for solving problems and making our lives easier? Or are we just maximizing some score of a pointless game?I'd love to live in a world with a thousand more Mitchells, following their passions without the burden of needing to justify decisions to a board who has no interest in quality. How do we create that world?
Like you said, what a legend. But, how do we make more legends?
One thing I've been envisioning is something like a "certified B corporation" style qualification that companies can get that indicates they contribute financially back to open source commensurate to the amount of it they consume to run their core business. If everything you do runs through open source software, in a moral sense, one can make the argument that you owe something back to it.
But the same general problem exists in industry. Our fear of doing things non-optimally only results in a less optimal solution. It's a risky move to take no risks.
In both academia and industry you see the same people doing the same things in the same way. It's no wonder things don't change. You can't have a paradigm shift by following the paradigm (playing it safe). I feel like this is a big shame in both tech and academia as the histories of these have always been made by those who rocked the boat. At some point we just have to admit we're not very good at predicting the future and instead of trying to predict what will be the most successful we should fund passion. I'm sure charlatans will get funded too, but its not like we're doing a good job at preventing that from happening now anyways...
I walked away thinking that no matter what they did, they'd probably be successful. I was extremely happy to find Ghostty and have been using it ever since.
I also like that I can have my config in a little plaintext file and just drop it onto a new computer and get the same keybindings. I am using the terminator keybindings for creating and navigating between split panes.
However their financials are... LOL
Revenue US$583 million (2024)
Operating income US$−254 million (2024)
50% loss margin :-)))
Actually, that's the question (or rather the feeling) I had even before seeing these numbers. Just by reading the docs and looking at everything they built (and how they built it) made me wonder if they spend more than they make. That's a really funny feeling I never had before. Like, surely economies can't be that forgiving when it comes to polishing things. Is that what's happening to the company? Mere overspending?
I cannot imagine what he went through.
Hero.
From the author himself: "My company had an exit, I did well financially. This is not a secret. I'm extremely privileged and thankful for it.".
Honestly, good for him [for doing well financially] and for admitting that he is privileged, and above all, being thankful for it.