cue VS tab-rs

I'm continuing to work on https://concise-encoding.org which is a new security-conscious ad-hoc encoding format to replace JSON/XML and friends. I've been at it for 3 years so far and am close to a release.

In a nutshell:

- Edit in text, transmit in binary. One can be seamlessly converted to the other, but binary is far more efficient for processing, storage and transmission, while text is better for humans to read and edit (which happens far less often than the other things).

- Secure by design: Everything is tightly specced and accounted for so that there aren't differences between implementations that can be exploited to compromise your system. https://github.com/kstenerud/concise-encoding/blob/master/ce...

- Real type support because coercing everything into strings sucks (and is another security risk and source of incompatibilities).

XML had a good run but was replaced by JSON which was a big improvement. JSON also had a good run but it's time for it to retire now that the landscape has changed even further: Security and efficiency are the desires of today, and JSON provides neither.

I've got the spec nailed down and can finally see the light at the end of the tunnel for the reference implementation in golang. I still need to come up with a system for schemas, but I'm hoping that https://cuelang.org will fit the bill.

Has anyone taken a look at Cue who can share any experiences?

https://cuelang.org/

It's mentioned on the site as an alternative to Yaml. Recently watched (~half of) this intro to it: https://youtu.be/fR_yApIf6jU

the most interesting summary explanation of cue lang and its differences is from a bug filing - https://github.com/cuelang/cue/issues/33

>CUE is a bit different from the languages used in linguistics and more tailored to the general configuration issue as we've seen it at Google. But under the hood it adheres strictly to the concepts and principles of these approaches and we have been careful not to make the same mistakes made in BCL (which then were copied in all its offshoots). It also means that CUE can benefit from 30 years of research on this topic. For instance, under the hood, CUE uses a first-order unification algorithm, allowing us to build template extractors based on anti-unification (see issue #7 and #15), something that is not very meaningful or even possible with languages like BCL and Jsonnet.

I agree with you. Personally, I think Cue is much better than either YAML, TOML or JSON because it adds the concept of types to the idea of describing configuration.

true, but the tooling and workflow remains the same.

Not sure of any tool that could abstract the details sufficiently to be widely adopted. There is just too much nuance in cloud config.

I'm exploring using CUE (https://cuelang.org) to define TF resources, exporting as JSON for TF. So far it's much nicer

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).