It also has nothing to do with TUI vs. GUI, since my comment addressed both (anecdotally).
If anything, your mentioning of their performance work is exactly my point.
1,334 karma · joined November 6, 2013
It also has nothing to do with TUI vs. GUI, since my comment addressed both (anecdotally).
If anything, your mentioning of their performance work is exactly my point.
Even if I wanted not to code it I couldn't. LLMs are still incapable of creating code up to any decent standard.
Also, while I do the get the joy of programming, we sometimes forget to focus on the user. You being happy to have typed the whole thing once, and have it run everywhere via the magic of browsers may not be the best strategy if this means your user's lap will be overheating.
In the end as much as I like coding I would prefer my users' experience to be the best it can be. LLM assisted code delivers this better and faster than hand-typing it all (which in turn is better than completely vibecoding it)
Migrating my screenwriting software[0] from OpenTUI to Roc thought me what were once rough edges that take a lot of time are now just a prompt away from a solution.
It now uses 10x less RAM, bundle is half the size, and my initial implementation is 700-800 fps for scrolling and 200 fps for writing.
Granted, a TUI is less complex than a full-blown GUI, but I built a Roc Iced platform just as easily that abstracted Iced flux away
The language itself is as welcoming. Even LLMs are less cranky and output nicer code, not having to deal with React.
[1]: https://nestful.app/
IIRC, the Flutter team mentioned how using just width/height constraints is enough to represent all relevant layouts. This sounds very nice, being so much simpler than Flexbox and miles ahead of CSS Grid ergonomics.
Did it live up to the promise or did they expand the model with Flex/Grid/etc?
I have migrated all my code to Gleam, FE and BE, Bun, browser, and BEAM.
Claude knows much less about Gleam than it does about Javascript or React. However the constraints of Gleam and its Elm inspired framework Lustre are so strong, Claude gives me much better results.
The only difference is I need to adjust my initial guidance.
Please consider using Trolley to package this for non-technical users:
1. They marry view hierarchy to state hierarchy
2. They make it very ergonomic to put state in components
I've been through this endless times. There are significant ways to reduce this friction, but in the end there's a tight ceiling.
This is why this kind of work feels like chasing a moving target. You always end up ruining something inherent to the framework in a pursuit to avoid the tons of footguns it's susceptible to.
It's also why I moved to Gleam and Lustre (elm architecture) and bid those PITAs farewell
Could I use OpenTUI Core with this?
I'd like to replace the hero at https://blisswriter.app with the actual app
This was written for my own screenwriting software, which is now in private alpha. It works quite nicely for an alpha
It really is quite an amazing piece of software. I just wrapped it in a useful GUI and a bundle/package CLI and it just works. Even on Windows. Kudos to the Ghostty developers.
Not sure where that fear comes from. Cloud challenges can be as or more complex than bare metal ones.
Feel free to open issues in the repo, I'll find a way to get a Windows machine if there's interest.
You can also email me at `trolley [at] wands [dot] is`
So here we are
Didn't catch on, though. Setting up events turned out to be too prohibitive. If this interests anyone feel free to contact me at contact [at] eventful [dot] is
It was so easy to get the terminal functionality going with `libghostty`. Most time was spent building the functionality around it.
Thanks for making it.
Can someone confirm/refute that?