ofek
Joined 10 years ago
Joined 10 years ago
I was quite worried that my wheelchair would break in some way like I've experienced several times before but everything went quite smoothly! AI helped tremendously with planning, e.g. here's Claude: https://claude.ai/public/artifacts/6c977d23-1b7c-4a00-a7aa-d...
However, the TUI as shown in a post [0] by one of their engineers is quite beautiful. For a moment I thought it was written in Python because it looks similar to Textual [1] but I inspected the binary for my platform [2] and it seems to be written in Rust. I guess Ratatui is quite customizable!
The state of its Windows support is unclear to me. The Bash installer script [3] has a comment on top that says "Windows: run under Git for Windows / MSYS2 Bash (same curl | bash flow); WSL uses the Linux binary." I ran the binary normally in a Nushell session and didn't encounter any issue other than a start-up time that was slower than expected on the first run. Perhaps I would have seen issues had I gotten past the login step.
[0]: https://x.com/skcd42/status/2054993372662915183
[1]: https://github.com/Textualize/textual
[2]: https://storage.googleapis.com/grok-build-public-artifacts/c...
[0]: https://ofek.dev/words/guides/2025-05-13-distributing-comman...
[0]: https://github.com/DataDog/integrations-core/pull/12986
edit: I asked for explanation before the post was edited to expand on that. I disagree but am sympathetic to the weariness of reading content now that AI use is widespread.
I really appreciate the support for Windows as that platform is currently underserved [3] when it comes to such memory tooling.
[0]: https://github.com/jcrist/msgspec
[1]: https://github.com/ofek/coincurve
pip is simply difficult to maintain. Backward compatibility concerns surely contribute to that but also there are other factors, like an older project having to satisfy the needs of modern times.
For example, my employer (Datadog) allowed me and two other engineers to improve various aspects of Python packaging for nearly an entire quarter. One of the items was to satisfy a few long-standing pip feature requests. I discovered that the cross-platform resolution feature I considered most important is basically incompatible [1] with the current code base. Maintainers would have to decide which path they prefer.
My motivation took a big hit last year, in large part due to improper use of social media: I simply didn’t realize that continued mass evangelism is required nowadays. This led to some of our novel features being attributed to other tools when in fact Hatch was months ahead. I’m sorry to say that this greatly discouraged me and I let it affect maintenance. I tried to come back on several occasions but could only make incremental progress on the workspaces branch because I had to relearn the code each time. I’ve been having to make all recent releases from a branch based on an old commit because there were many prerequisite changes that were merged and couldn’t be released as is.
Development will be much more rapid now, even better than the way it used to be. We are very excited for upcoming features!