wasi_master (u/wasi_master)

wasi_master commented on 13ft – A site similar to 12ft.io but self-hosted github.com/wasi-master/13... · Posted by u/darknavi

wasi_master · 2 years ago

Hello everyone, it's the author here. I initially created 13ft as a proof of concept, simply to test whether the idea would work. I never anticipated it would gain this much traction or become as popular as it has. I'm thrilled that so many of you have found it useful, and I'm truly grateful for all the support.

Regarding the limitations of this approach, I'm fully aware that it isn't perfect, and it was never intended to be. It was just a quick experiment to see if the concept was feasible—and it seems that, at least sometimes, it is. Thank you all for the continued support.

wasi_master commented on Textualize – A framework for building Text User Interface applications textualize.io/... · Posted by u/wey-gu

throwanem · 4 years ago

Yeah, that's fair. The perils of reading code on a busy Sunday, I suppose - I didn't get as far as noticing that Textual has basis in a much more heavily used and tested library, and that definitely changes my evaluation.

Thanks for the steer!

wasi_master · 4 years ago

No worries, cheers!

wasi_master commented on Textualize – A framework for building Text User Interface applications textualize.io/... · Posted by u/wey-gu

throwanem · 4 years ago

I feel like it's not been that long ago that I ran into trouble with "standard xterm escapes". As I recall, there are a lot of those, and many of the more interesting ones are at best very unevenly supported across terminals. The last such experience is in fact what led me to avoid doing anything more complicated in a terminal than basic colors and a few emoji.

That said, if your terminal support is as good as advertised, it probably shouldn't be hard to surface that on your site. (If you really want to sell me on it, let me try it out in a web-based terminal emulator like xterm.js! Then let me package up that test script for download, so I can easily run it locally in my terminal, as many of them as I like, and see for myself how well it works there.) Maybe also include feature coverage in your test suite and even CI, although that's definitely a trickier engineering problem.

As it is, I'd be very hesitant to use the library since doing so would risk incurring a dependency (on the user using a supported terminal) that wouldn't be easy to characterize more closely than "I tried this in xterm, y, and z and it worked, but if it breaks for you I'll have no immediate idea of why, and I'll have to choose between #wontfix and losing velocity on feature work."

wasi_master · 4 years ago

I have been using textual extensively inside Visual Studio Code which uses xterm.js behind the hood [1], so far everything except hyperlinks works flawlessly, and hyperlinks don't obstruct anything either, it just shows as plain text. All 256 tests pass on my machine and the coverage based on lines of code is 42%, but you have to keep in mind that this project is still in beta [2] so that number is going to change

Also since the project is based on rich from the same author, some of the terminal features are from rich and the test coverage on that is 99% [3].

[1]: https://xtermjs.org/#real-world-uses

[2]: https://github.com/Textualize/textual#textual:~:text=Current....

[3]: https://app.codecov.io/gh/Textualize/rich