ponyc VS tab-rs

For example, the actor's model is not used by a lot of languages, Pony (https://www.ponylang.io/) and Elixir are the only ones that I know, but they address the concurrency problem quite well, while it's a pain to deal with in other languages at large scale.

And that last point is critical. If the language flatly can't represent some concepts it uses, they have to be implemented somewhere else. I had a similar discussion with a proponent for Pony once- the language itself is 100% safe, and fully dependent on C for its runtime and data structures. One of Rust's core strengths is being able to express unsafe concepts, meaning the unsafe code can expose a safe interface that accurately describes its requirements rather than an opaque C ABI. Vale doesn't seem to do that.

"Exterior iteration. Iteration used to be by stack / non-escaping coroutines, which we also called "interior" iteration, as opposed to "exterior" iteration by pointer-like things that live in variables you advance. Such coroutines are now finally supported by LLVM (they weren't at the time) and are actually a fairly old and reliable mechanism for a linking-friendly, not-having-to-inline-tons-of-library-code abstraction for iteration. They're in, like, BLISS and Modula-2 and such. Really normal thing to have, early Rust had them, and they got ripped out for a bunch of reasons that, again, mostly just form "an argument I lost" rather than anything I disagree with today. I wish Rust still had them. Maybe someday it will!"

I remember that one. The change was shortly after I started fooling with Rust and was major. Major as in it broke all the code that I'd written to that point.

"Async/await. I wanted a standard green-thread runtime with growable stacks -- essentially just "coroutines that escape, when you need them too"."

I remember that one, too; it was one of the things that drew me to the language---I was imagining something more like Pony (https://www.ponylang.io/).

"The Rust I Wanted probably had no future, or at least not one anywhere near as good as The Rust We Got."

Almost certainly true. But The Rust We Got is A Better C++, which was never appealing to me because I never liked C++ anyway.

Pony or bust.

If you have a value in mutable storage, and want to treat it as an immutable parameter without copying it first, you will need to provide some way to guarantee that it won't be mutated while being treated as immutable! There doesn't seem to be a definitive best way to do that (although the likes of Pony make a try at it).

The love child of Erlang and Rust exists already: Pony.

https://www.ponylang.io

It really is the best of both languages... unfortunately, the main supporter of Pony seems to have stopped using it in favour of Rust though :D.

But if that's really what you want, Pony is your language. It definitely deserves more love.

You can actually try to have a magic language which "does not ignore decades of PL research" but you are likely to get either something broken or a project that is likely not going to release in our lifetime.

Never a bad time to plug Pony lang[1] - a safety-oriented actor-model language. In addition to the numerous safety guarantees, you also get a beautiful syntax and automatic memory management. Really a great language that often gets overshadowed by Rust's hype-turfing.

[1]: https://www.ponylang.io/

If you want to read some code, my project is tab-rs.

I myself use the many (alacritty) terminals + tiling WM solution at the moment (switching between i3wm and LeftWM) but it doesn't feel optimal. I always though tmux looked too involved to learn so I've been on the lookout for alternatives such as Wezterm (a terminal with built-in multiplexing), tab (a command line controlled multiplexer) and now zellij.

Plus a lot of cleanup in the tab-pty-process crate. It now exposes an interface similar to portable-pty, but with non-blocking file handles.

I ended up writing a terminal multiplexer because screen and tmux were too complicated to use. It has a built in fuzzy finder, stateless navigation, and YAML configs for persistent sessions: https://github.com/austinjones/tab-rs/

The way I typically unify messages is define an enum, and map/merge channel receivers. tokio-stream would probably work with these examples. Here's an example from a fuzzy-finder implementation: https://github.com/austinjones/tab-rs/blob/main/tab-command/src/service/terminal/fuzzy.rs#L332

Really nice cheat-sheet write up on screen & tmux & byobu.

Also worth checking out tabs-rs[1] which seems very well reviewed & recent.

Personally, I am a huge fan of dtach[2][3], which isn't a multiplexer, just a detachable proxier of terminal sessions. This let's me run a persistent vim session that I can reconnect to, and vim has however many terminals I need open in it. Vim does my multiplexing, dtach just allows me to make vim persistent. Very glad to have re-discovered dtach, to enable this workflow.

Notably dtach is very lightweight. Unlike tmux, it is not a virtual terminal. Upon reconnect to my vim session, I issue a control-l to refresh the screen. Dtach hasn't retained the screen state, isn't translating between terminfos. The one thing that can go wrong here is connecting from different terminals- few programs have a way to update the TERM setting once the program has launched.

[1] https://github.com/austinjones/tab-rs

[2] https://github.com/crigler/dtach

[3] https://wiki.archlinux.org/index.php/Dtach

The nice thing about that is that many other tools can work too. Someone using direnv can set properties that would be available in the hurl script. Likewise, someone using tab could have environment variables defined for their active tab that could be used. If you invent your own notion of an environment, you lose interop with a lot of other tools that target the standard environment.

Are you running v0.5.3? I just released a fix for a Kakoune issue that was caused by add-highlighter global/ number-lines -relative in kakrc. It sounds similar to what you described.

There are also some crazy ANSI sequences that cause the terminal emulator to write stdin - so applications can query the terminal state. Crazy stuff can happen when those sequences are copied from the scrollback buffer (which is why tab now filters them out).