ponyc
tab-rs

ponyc | tab-rs | |
---|---|---|
66 | 13 | |
5,782 | 660 | |
0.6% | - | |
9.1 | 0.0 | |
4 days ago | almost 2 years ago | |
C | Rust | |
BSD 2-clause "Simplified" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ponyc
-
Can We Get the Benefits of Transitive Dependencies Without Undermining Security?
> Capabilities taken literally are more of a network thing (it's how you prove you have access to a computer that doesn't trust you). On a language, you don't need the capabilities themselves.
You may be thinking of the term in a different context. In this context, they are a general security concept and definitely apply to more than the network, including languages:
https://en.wikipedia.org/wiki/Capability-based_security
http://habitatchronicles.com/2017/05/what-are-capabilities/
https://www.ponylang.io/
etc...
-
Thinking in Actors – Part 3 – Using the Actor Model to Track Aircraft
Actors immediately made me think of Pony. https://www.ponylang.io
- Pony (Programming Language)
- Firewalling Your Code
-
Multitasking, parallel processing, and concurrency in Swift
Or give up and erase all the type information by saying `throws Exception` or `throws Throwable`.
Genericizing throws in particular was tried in Midori [2] and worked out really well (by report). In addition, several less-than-completely-obscure languages are starting to experiment with the algebra of effects in general (as opposed to error handling in particular). Pony (https://www.ponylang.io/), OCaml (https://ocaml.org/manual/5.2/effects.html) and others are experimenting with bringing what Koka (among others; https://koka-lang.github.io/koka/doc/index.html) to the masses.
[1]: https://www.artima.com/articles/the-trouble-with-checked-exc...
- Old Version
-
The problem with general purpose programming languages
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.
-
Found a language in development called Vale which claims to be the safest AOT compiled language in the World (Claims to beSafer than Rust)
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.
-
The Rust I wanted had no future
"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.
-
How long until Rust becomes mandatory, and use of any other language opens the developer up to Reckless Endangerment charges
Pony or bust.
tab-rs
-
Another terminal multiplexer for team leads.
If you want to read some code, my project is tab-rs.
- Zellij – A Terminal Workspace and Multiplexer Written in Rust
-
Zellij: a Rusty terminal multiplexer releases a beta
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.
-
What's everyone working on this week (9/2021)?
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.
-
My take on byobu, an easy to use terminal multiplexer
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/
-
Actors with Tokio
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
-
Terminal Multiplexers
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
-
Hurl 1.0.0, a command line tool to run and test HTTP requests
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.
-
I wrote a terminal multiplexer called tab. It's designed to be intuitive, and config-driven.
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.
-
How To Write A Terminal Multiplexer With Rust
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).
What are some alternatives?
gleam - ⭐️ A friendly language for building type-safe, scalable systems!
.tmux - Oh my tmux! My self-contained, pretty & versatile tmux configuration made with 💛🩷💙🖤❤️🤍
Halide - a language for fast, portable data-parallel computation
pueue - :stars: Manage your shell commands.
Phoenix - wxPython's Project Phoenix. A new implementation of wxPython, better, stronger, faster than he was before.
rustfuif - Performance & correctness oriented beursfuif implementation in rust
Celluloid - Actor-based concurrent object framework for Ruby
zellij - A terminal workspace with batteries included
gentoo-overlay - Gentoo overlay
uom - Units of measurement -- type-safe zero-cost dimensional analysis
prolog-to-minizinc - A Prolog-to-MiniZinc translator
zoxide - A smarter cd command. Supports all major shells.
