Live data from Hacker News

Libghostty is coming

mitchellh.com

261–270 of 275 posts

Re: Libghostty is coming

#261
post #126

Earlier quoted context omitted.

To add... The missing scrollbars feel painful to me. I don't even want them for scrolling, really. I want the visual reference for: "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…

Suggestion to use Klogg ( https://github.com/variar/klogg ) for reading log files. I always was on the camp of " tail -f file.log " but since discovering this app, I saw the light.

Centralized logging, a la Splunk is the gold (with what they charge, probably platinum) standard here. Watching someone who knows what they're doing at a Splunk console for a distributed system they understand is a thing of beauty. It's just a shame they charge so much.

Re: Libghostty is coming

#262
post #208

Earlier quoted context omitted.

Ghostty is his hobby project: why would he do that?

Because maintaining is not as fun as starting? Because other people can maintain a well structured project but not as many people can start something from scratch? Because his skills can be better used elsewhere?

Hmm I found the opposite to be true. Maintaining a well structured project is a much harder skill then starting green field.

Re: Libghostty is coming

#263
Several years ago I was crazy frustrated with how slow 'less' is for some things (regex search and handling long lines) and was slowing down my day to day operations work. I very briefly entertained an idea to write my own pager to fix those problems but it would have been way too complex to do in my spare time. If libghostty existed then it might have been a different story. If libghostty is done well I think it could be an enabler for many types of terminal applications. I'm excited to see where it goes.

Re: Libghostty is coming

#264

This is super cool, it will be so nice to have a truly omni-platform terminal emulator that can even conceivably extend to iOS and Android. Aside: I didn't realize Ghostty was written in Zig, wow. The first Zig-thing I'm aware of using on a regular basis. It's amusing the repository structure looks exactly like a Golang layout, haha. https://github.com/ghostty-org/ghostty

Not omni-platform if you have macOS Hopefully libghostty will be much more permissive. No dependencies (not even libC) is a good sign that will be true.

(written on a 2018 macbook pro running macOS 10.14.6, which still works great in every way)

Re: Libghostty is coming

#265
post #264

This is super cool, it will be so nice to have a truly omni-platform terminal emulator that can even conceivably extend to iOS and Android. Aside: I didn't realize Ghostty was written in Zig, wow. The first Zig-thing I'm aware of using on a regular basis. It's amusing the repository structure looks exactly like a Golang layout, haha. https://github.com/ghostty-org/ghostty

Not omni-platform if you have macOS Hopefully libghostty will be much more permissive. No dependencies (not even libC) is a good sign that will be true. (written on a 2018 macbook pro running macOS 10.14.6, which still works great in every way)

I would pay money to never have users like you, even if my software incidentally worked on your intentionally terribly out-dated system.

Re: Libghostty is coming

#266
post #264

Earlier quoted context omitted.

Not omni-platform if you have macOS Hopefully libghostty will be much more permissive. No dependencies (not even libC) is a good sign that will be true. (written on a 2018 macbook pro running macOS 10.14.6, which still works great in every way)

I would pay money to never have users like you, even if my software incidentally worked on your intentionally terribly out-dated system.

What an odd sentiment from someone who supposedly values explicit, declarative, total control over their OS configuration, and not just the rolling-latest-and-greatest.

and p.s., way to take a neutrally stated, perfectly reasonable preference of system usage and make it personal. The perfect example of the type of person I'd pay money never to encounter.

Re: Libghostty is coming

#267
post #139

I can’t figure out how to get the visidata frequency analysis histograms to render properly. Some render as blocks as expected but others are those diamond-question marks. I know it’s a silly hang up but it’s what’s keeping me on iterm. It’s seemingly impossible to search for (or at least I haven’t figured out the right keywords) to troubleshoot too.

Try asking on https://github.com/saulpw/visidata the community there can help.

I am seeing this issue on a Mac with ghostty but not with wezterm, from the same binary. Ghostty shows some correct characters and some diamond-question marks, and a line usually contains one or the other. The ghostty inspector shows the diamonds are not the blocks.

Re: Libghostty is coming

#268
post #222

Earlier quoted context omitted.

I truly don’t understand nor follow what you mean? What makes MIT/BAD bad for software infra?

>> I truly don’t understand nor follow what you mean? What makes MIT/BAD bad for software infra? You should have access to the source for your infra as a user of it. MIT/BSD allow people to deploy without offering source, so they can do whatever they want with it and then you get to use it. TiVoisation is more than possible among many other user-hostile options. "But you can always get the source!" is not a valid res…

That is a valid POV I hadn’t fully considered.

But I would hesitate to blame this on the original OSS author’s license choice - the vendor can always provide source even without the force of GPL. Heck, rather making it GPL means almost no hosting company will provide it.

Re: Libghostty is coming

#269
post #208

Earlier quoted context omitted.

Because maintaining is not as fun as starting? Because other people can maintain a well structured project but not as many people can start something from scratch? Because his skills can be better used elsewhere?

That sounds like the Google philosophy though, where smart people come up with ideas and write the initial implementation (then get promoted) and other less smart people take over, and you end up with a mess that had great potential like Bazel?

This could also end up like Fabrice Bellard's projects: yes he is no longer maintaining tinycc, but as a result we are now getting ffmpeg, qemu, and more.

Re: Libghostty is coming

#270
post #266

Earlier quoted context omitted.

I would pay money to never have users like you, even if my software incidentally worked on your intentionally terribly out-dated system.

What an odd sentiment from someone who supposedly values explicit, declarative, total control over their OS configuration, and not just the rolling-latest-and-greatest. and p.s., way to take a neutrally stated, perfectly reasonable preference of system usage and make it personal. The perfect example of the type of person I 'd pay money never to encounter.

It's not an odd sentiment at all, you would be ridiculed widely for running an unsupported, out of date Linux distribution too.

You can do whatever you want, I left my true thoughts out, and kept it as impersonal as possible. As someone who ships and supports products and has to deal with curmudgeons like you, I would literally pay to not have you as a customer or user. People like you are a constant drain on attention, time, and focus. You know, like you basically expecting folks to bend over backwards, in this very thread, to support you, when there's a perfectly viable supported solution.

> perfectly reasonable preference

Whatever you say, friend.

Post reply on HN