1nv1n

Yeah, I understand their direction/scope. While web-dev is easy; the underlying tech and all the edge cases for web browsers is a huge undertaking.

I really liked the interactive app demo on the website. App looks good (features + polish) I have it downloaded, will check it out later tonight!

What would you say was the one (or multiple) killer feature(s) that took you away from herdr/warp/tmux/etc. and towards tty7?

Appreciate the time you took to point this out. Yes, the docs as they are now are LLM written. It might help a bit more if you can point out to a particular section or file that stands out. If not, no worries, I will plan on doing a manual sweep across all .mds for better (clearer) readability.

I had been thinking about that & wrote a blog post last week: https://godot-pty.github.io/gpty/docs/overview/story/

It sort of goes over the "why?"/"why now?"; but TLDR; Wanted to use Godot & Rust in personal project(s) (no pressing need for it) I saw Cate & wondered whether I could use this tech. stack to replicate, instead of web tech. So that's where it all started. I know that if you want to live in the terminal, there's tmux and herdr, and I'm not (also can't) compete with them. But I can surface a terminal that then lets TUI folks stay in their preferred apps. The residual why/why now are largely shaped by what I want (feature-wise) to put into the tool.

And the next big feature I want is a personal knowledge management. Maybe it looks like a complex beast; but the core idea driving my features are what I want on a daily basis without switching context as much. Sorry, I know it's not a great answer, bit rambly.

Agree on Chrome being top-dog in this space. Electron would've been the easy (pragmatic?) choice. But the design decision was to use Godot and not create yet-another-Chrome-Electron app. It's certainly not pretty to look at in its current state.

This is something I'm mainly working on it on my free time so figured why not see how far I could push things.

Thank you for your kind words, that's generally how I see other's projects too.

I haven't performance or load tested, it's on the backlog; so I'd be curious on whether this works for your use-case. And if not, feel free to log an issue!

Thanks, wasn't familiar with these, I'll look into them though the project direction is unlikely to change to swap Godot out. As of now, the binaries are in the 60-80 MB range; so not tiny - but not something I'd consider massive for what it is.

Usage has been relatively snappy (could be better, I suppose, I need more time). Definitely not sluggish.

A concern is that RAM usage is on the higher side (this is something I'll look at on the next release).

Thanks for your honest response. It's okay. At its core, it's a fun hobby/side project, not my day job. And I like it. But I'm realizing maybe this wasn't the platform to post on.

The browser is probably a non-issue, more a passing thought now. I definitely do not want to bundle or bring in Chromium. If it was a deal-breaker, I would've just gone the Electron route. Appreciate you sharing your WebView extension though, looks neat!

The concepts/reg-ex redirect is how I was imagining the autonomous agent automation. It does need to be fleshed out a bit more, but essentially, it was an easy way to let a process to know what's happening in another process so it could react appropriately. The e2e tests are a good use-case, but not something I've looked into yet (in theory, the framework should hold up for it)

Original intent was just a hobby/side project. As it grew, I thought maybe posting about it would be alright in case people find the idea interesting.

Yeah, the README doesn't have screenshots; but the docs site does - https://godot-pty.github.io/gpty/ - 1 for now, but each release's blog entry gets the main app page + one for any salient features.

I'll add that in; maybe defaulted to folded on the README, a gallery of app screens or snippets. I need to spend some time on the UX, but yeah, screenshots (and possibly some sort of an intro video that explains features) is something I should've also added to the README.