cyclohexane

Hi all,

I use a wayland Gentoo system, but I want to run Lutris for gaming. I would like to do this with at least some degree of filesystem isolation, as Lutris seems to install dependencies on its own and it pollutes the system in ways I cannot track.

What is the best way to do this? is it possible to do in a chroot? or mount namespaces? will it give me a lot of trouble?

It seems that merely installing things in a chroot and running it is not enough.

Most music videos, especially modern ones, are pretty boring.

I mean, sure, that's probably heavily influenced by the need for bundling for the frontend.

But it isn't done blindly. Bundlers reduce the overall size of the code, either due to minification or tree-shaking (removing unused modules). It also removes the filesystem overhead of resolving and opening other modules.

Would bundling be useful in other interpreted languages?

I suppose you may count JVM's compilation to bytecode as being very similar.

What projects are out there seeking to innovate in the terminal and command line space, and improve or revolutionize the terminal environment?

• NuShell is one such example, a shell that uses structured data in its pipelines. Many other experimental shells out there innovating in different spaces.
• An even more daring example is DomTerm. It's a terminal emulator with more rich rendering. Supports rich text, images, etc while maintaining xterm compatibility.

Please do not shy from answering projects that are very experimental, early stage, break a lot of backwards compatibility or radically change the current way of doing things.

Most applications provide you configuration files that are data / text based. Whether it is toml, JSON, yaml or some other format, you are usually defining values for pre-determined keys and that's all.

This makes sense for many applications, but involved applications have explored configurations that make use of scripting. For example, vim uses VimScript, neovim uses Lua, but vscode uses json (as far as I remember), and Helix (vim inspired editor) argues editor configurations must be data, not scripting, and uses toml.

many tiling window managers use various programming languages (Qtile uses python, xmonad uses Haskell, Awesome uses Lua) while others stick to data configuration (i3).

Do you think that scriptable configuration is over-engineered and brings weaknesses, or is it warranted and grants the user power in these big applications? What are the benefits of scriptable configurations?

So apparently there are two editors inspired by vim, but built from the ground up (as opposed to neovim, a vim fork that seeks to improve on top of vim).

I've heard of Helix several times prior, but it never quite attracted me. Seemed like vim, but different key bindings and much worse plugin system. It also has different visual and normal modes than vim, but it didn't quite click with me. I do like it's multi-cursor ability though.

Then it turns out that Helix was also inspired by not just vim, but also kakoune. Kakoune also has different keybindings, and different modes, but its different modes make sense to me. It fuses visual and normal mode into one. Your normal mode is for both navigation and selection.

Kakoune promotes the idea that you should visually see the text you're operating on before running the command. You know how in vim, "dd" deletes a line, "dw" deletes a word, and "d$" deletes to the end of the line? In vim, you don't see what you're deleting before its gone (which is fine and works for many). In kakoune, the selection happens first before the action. So you select the word or the line, and then you delete.

But what I found to be Kakoune's killer feature was its shell integration. Kakoune seemlessly integrates into the unix shell, allowing you to offload many tasks to it. For example, instead of it having a built-in sort command, you use the unix sort command to sort your lines.

I'm surprised kakoune isn't more popular. Yes, it is still in a much earlier phase than vim, and the ecosystem is far less mature, but I am surprised to see Helix gaining more traction.

I'm still very new to kakoune and exploring it. But I like it a lot so far.

Hi all,

I am looking for recommendations on resources to learn Linux networking. I am primarily hoping for text resources such as books, guides, blog series, articles, etc. I have trouble focusing on videos.

I am mainly targeting linux networking topics, such as how the linux networking stack works, and things like iptables, network namespaces, network interfaces, sockets, NAT, firewalls, internal IP-addressing, subnetting, routing, proxying, internal DNS, and anything that I may not know exists but is related to these concepts and linux networking in general.

Any recommendations?

Yes, I know so much of Alpine's lightweightness comes from not using glibc.

But still, the other options I see are far from being slimmed down. Debian, Ubuntu server, CentOS... They all could use some cuts.

What's the most slimmed down non-desktop distro that still has a glibc base? I honestly don't care if it has its own package manager (build tool handles this for me). Just wanna use it in containers for running server apps.

Yes, I know so much of Alpine's lightweightness comes from not using glibc.

But still, the other options I see are far from being slimmed down. Debian, Ubuntu server, CentOS... They all could use some cuts.

What's the most slimmed down non-desktop distro that still has a glibc base? I honestly don't care if it has its own package manager (build tool handles this for me). Just wanna use it in containers for running server apps.

Some backend libraries let you write SQL queries as they are and deliver them to the database. They still handle making the connection, pooling, etc.

ORMs introduce a different API for making SQL queries, with the aim to make it easier. But I find them always subpar to SQL, and often times they miss advanced features (and sometimes not even those advanced).

It also means every time I use a ORM, I have to learn this ORM's API.

SQL is already a high level language abstracting inner workings of the database. So I find the promise of ease of use not to beat SQL. And I don't like abstracting an already high level abstraction.

Alright, I admit, there are a few advantages:

• if I don't know SQL and don't plan on learning it, it is easier to learn a ORM
• if I want better out of the box syntax highlighting (as SQL queries may be interpreted as pure strings)
• if I want to use structures similar to my programming language (classes, functions, etc).

But ultimately I find these benefits far outweighed by the benefits of pure sql.

Podman is a lot like Docker: a tool for running OCI containers. While it maintains backwards compatibility with Dockerfile and docker-compose syntax, it offers a lot of other benefits:

• daemonless: it can run containers without a daemon process running in the background.
• Rootless: can run containers without root privileges
• pods: can group containers into secluded pods, which share resources and network namespace

Podman has other features I haven't explored yet, like compatibility with Kubernetes yaml file, and being able to run containers as systemd units.

Have you used podman before? What are your thoughts on it?

There was a time where this debate was bigger. It seems the world has shifted towards architectures and tooling that does not allow dynamic linking or makes it harder. This compromise makes it easier for the maintainers of the tools / languages, but does take away choice from the user / developer. But maybe that's not important? What are your thoughts?