Live data from Hacker News

Zellij – A Terminal Workspace and Multiplexer

zellij.dev

101–110 of 248 posts

Re: Zellij – A Terminal Workspace and Multiplexer

#101
post #89
post #59

Earlier quoted context omitted.

I'm confused. Zellij uses wasmer and wasmer-wasi. Wasmer may use cranelift for compilation (dont know if Zellij does). "Fast & Safe. Wasmer runs WebAssembly at near-native speed in a fully sandboxed environment." ( https://github.com/wasmerio/wasmer ) But ... "Cranelift does not yet perform mitigations for Specter or related security issues, though it may do so in the future." ( https://github.com/bytecodealliance/wa…

I feel like in this case those kinds of things are up to Zellij. If you run wasmer within the same process and share memory with the main Zellij process then yes wasmer/cranelift/wasmtime/wasm doesn't protect you from various speculative execution attacks. However, Zellij could run plugins in separate processes and apply things like seccomp to get further protections provided at the operating system level. This is st…

WASM and Wasmer are not intrinsically anymore secure, except for simplicity, than any other editor plugin system. Vimscript and Emacs-lisp basically have the same security characteristics as using WASM for plugins. It's not a step in any direction, except for whatever environment Zellij exposes to the plugins by default.

Re: Zellij – A Terminal Workspace and Multiplexer

#102
post #68
post #43

Earlier quoted context omitted.

If you're already spending a lot of time in the browser looking at stuff (AWS Console, Stack Overflow, etc), I can see the convenience of just switching tabs to your terminal rather than pulling up a window. So far I've solved that problem with keyboard shortcuts or other macros to pull up a terminal when I need it.

Conceptually, I don't think the solution to "switching windows is too hard" ought to be "make the terminal part of the browser". Although it does seem like perhaps the least immediately painful way to solve the problem. Using Lynx in the terminal might be another way to do it.

Yeah, I tend to agree. But I know that there are some people who really, really, really like doing stuff in the browser.

Re: Zellij – A Terminal Workspace and Multiplexer

#103
post #94
post #75

Earlier quoted context omitted.

YAML sucks but so does TOML, especially when it comes to nested data structures like the layout.yaml shown on the front page. There are no good configuration languages in existence and there never will be. We have rejected Lisp/sexp so now we must suffer endlessly.

I would say that Dhall is fine, just from a parallel universe. JSON is close to sexps, but it sucks when comments are not allowed.

Which is why EDN is so much better for config.

Re: Zellij – A Terminal Workspace and Multiplexer

#104
Is there a good reason for a multiplexer to be a separate tool from a terminal? Or a window manager? Or is this just GNU/Unix philosophy (do one thing well and compose).

The reason I ask is that while I never used a multiplexer like tmux, I use the layout features of kiTTY every day and I can't quite see beyond that common use case (split this terminal into X windows with Y layouts).

Re: Zellij – A Terminal Workspace and Multiplexer

#105

The latest version from cargo does not build for me. edit: After running "rustup update" it does install. I am liking Zellij so far.

It's the typical Rust problem and my biggest gripe with the Rust ecosystem: many libraries are using unstable/nightly features, making development needlessly frustrating for people using the stable Rust release.

Rust devs, please don't. Not every Rust developer uses rustup or knows how to solve this issue, not everyone is willing or able to use the nightly build just so dependency 21/63 doesn't throw errors.

Re: Zellij – A Terminal Workspace and Multiplexer

#106

Is there a good reason for a multiplexer to be a separate tool from a terminal? Or a window manager? Or is this just GNU/Unix philosophy (do one thing well and compose). The reason I ask is that while I never used a multiplexer like tmux, I use the layout features of kiTTY every day and I can't quite see beyond that common use case (split this terminal into X windows with Y layouts).

persistence and the ability to run it on a remote machine are the big draws. I can set up a tmux session on a remote box, have multiple connections to it, and close my terminal without losing my work.

Re: Zellij – A Terminal Workspace and Multiplexer

#107

Earlier quoted context omitted.

The "no"/"norwegian" thing is emblematic of very sloppy thinking in YAML's design, and it's far from the only example. It's possible to avoid these pitfalls - like people do with PHP - but why burden users with that in a new project when better options have been available for years? They obviously like Rust, why not just follow their lead with TOML?

That "feature" regarding "no" hasn't even been present in the YAML spec since 2009.

Thanks for being clear about this and repeating it. I didn’t know. I think I will only use YAML 1.2 as configuration language.

Re: Zellij – A Terminal Workspace and Multiplexer

#109
post #13

Earlier quoted context omitted.

Not having to touch the mouse. I can't do it myself, but I've watched ops folks using tmux in a productive way that I think would be difficult to reproduce if you involved a window manager.

You don't have to use the mouse with tiling window managers... /s heavy tmux user that left it for xmonad.

Can you select and copy some text from your terminal emulator without using tmux? Copy-mode is one of the killer features of tmux for me.

The only terminal emulator that supports selection with keyboard afaik is rxvt with plugins. I would be interested to know if there are other terminals that support this. Please don't say emacs XD

Re: Zellij – A Terminal Workspace and Multiplexer

#110

You have a problem and you need a configuration language, so you pick YAML. Now you have two problems. Take a leaf out of Rust's book and use something simple and sane like TOML, YAML is a mess. See: https://github.com/cblp/yaml-sucks Otherwise this looks like a great project, please don't ruin it with YAML.

same comment, different config format, year after year after year...
Post reply on HN