Linux & Tech news šŸ“°

True shame they are doing it only for a Docker install. I for one avoid Docker like the plague.

At the risk of opening a Pandora’s box, may I ask why?

Why am I going to use a container if I don’t have to.

Well, I guess it depends on your use-case, but I can think of MANY reasons why I’d want to spin up a container. For one, when I’m done with it, removal is as easy as just deleting the container, image, volume, etc - and the base system isn’t touched at all.

2 Likes

In some people’s minds lately it’s been ā€œWhy would I put it on bare metal if I don’t have to.ā€ :upside_down_face:

I mean, some things I want on ā€œbare metalā€ but some things I want to isolate from the rest of my system. A good example, I recently wanted to play around with whisperX to process some audio I have into a diarized speech-to-text transcript. Implementing it locally with Python libraries, etc, even in a venv was a BIG PAIN IN THE BUTT. However, there are a few container images that have everything already configured, and you basically just run it like a locally installed application, but instead, it runs completely within the container, and just saves the txt file in a mapped path that’s outside the container.

1 Like
3 Likes

:skull:

6 Likes

I think this is the only thing that’s made me tempted to use Chrome in the last decade or so :rofl:

1 Like

There is another one called Microslop Replacer.

6 Likes

JPEG-XL image support is back in the very latest Google Chrome/Chromium codebase. Back in December they merged jxl-rs as a pure Rust-based JPEG-XL image decoder from the official libjxl organization. At the end of December they did more JPEG-XL plumbing with the enums and build flags for the support.

Now as of yesterday they wired up the JXL decoder!

A new report from browser security platform LayerX indicates that the campaign is still ongoing despite being exposed, and the following 17 extensions are part of it…

:rofl:

12 Likes
10 Likes
5 Likes
3 Likes

Although I like the approach itself, I’ve never really warmed up to tiling window managers. But this Kwin script for Plasma 6 is a really good alternative.

EDIT:
@SGS

Ā© Logo Protector

:scream: :rofl: :victory_hand:

5 Likes

2 posts were merged into an existing topic: Off Topic Chit Chat - (Silliness factor 5)

A post was merged into an existing topic: Off Topic Chit Chat - (Silliness factor 5)

I can relate. Every once in a while I use Garuda with Cosmic instead of Gnome, and since a couple of weeks (perhaps since the 1.0 release) its tiling implementation seems to be more predictable (thus more convenient). So much so, that I currently prefer to use Cosmic over Gnome. Every once in a while I’m still surprised about the tiling behavior, but it’s getting there.

1 Like

I’m just a mouse pusher, as we call it in German. I installed the Kwin script, tried it out for a few hours, and then turned it off again. You have your habits, your workflow, and even with lots of open windows, I can cope just fine.

3 Likes

Have you tried the PaperWM extension? I find it great because I appreciate the concept of tiling but not the coding aspect of tiling WMs. Call it laziness, but I would much rather have the graphical settings. Maybe because I remember every single thing I change when I do it that way. When I code I remember nothing :woozy_face::brain:

1 Like