As it specifies the version number, I assume it was not compatible with version 2.9 of Winamp skins maybe? I mean there was this classic Winamp skin system and the modern one later. I don’t use or keep track of the changelog for Audacious, so this is me more asking and shooting with guns while being blind.

What is the longest time Brachefs users can use? I mean the Linux LTS version with Bcachefs included that is the longest supported. Or are there distributions which are known to include a patched Linux kernel with support for Bcachefs?

Yes, they are reverting back. Fedora users always live on the edge. They are basically (but not quite right) “always” the first accepting a new technology. Not even Archlinux does that. Arch users obviously live on the edge too, but for other reasons. :D

But wasn’t Fedora not going to discontinue X11 support only for GNOME version? I thought other spins are still allowed to support it, but doesn’t matter anymore, because they reverting this idea back. I think. But why didn’t you switch to another distribution, instead buying new hardware, if that was the only problem?

A dash is a bit problematic from practical point of view. In example I allow single numbers without a colon like just 6 which would be interpreted as 6:6. And each element is optional as well, which would make -6 either be a negative number, an commandline option or a range? Some languages also use dots .. instead. If I want ever support negative numbers, then the hypen, dash or minus character would be in the way.

I mean I could just do a duck typing like stuff, where I accept “any” non digit character (maybe except the minus and plus characters) with regex. Hell even a space could be used… But I think in general a standardized character is the better option for something like this. Because from practical point of view, there is no real benefit for the end user using a different character in my opinion. Initially I even thought about what format to use and a colon is pretty much set in stone for me.

Fedora even switched to Wayland by default in 2016 (at least for the GNOME release). I don’t know what they were thinking. 8 to 9 years before they were already using Wayland… and it still have some “problems”. Can’t imagine what you were going through. :D

But compared to Fedora, Ubuntu only did change temporarily to Wayland right? I mean it was not an LTS version. I installed LTS 18.04 and don’t remember anything like that by default.

Those who don’t care, don’t have anything to say and should not the deciding factor. Why count voices who don’t care?

Who “promoted” it as superior to X11? Pretty much everyone I watch and read said that Wayland had their problems and they are working on it, but it is the future. There are ideas and concepts that are superior to X11, but it does not mean its fleshed out. I don’t think anyone said that Wayland is superior to X11 in every aspect. Not even the most die hard fan say it. :D

It doesn’t need to be. The goal is not to recreate and be compatible with X11, otherwise it would defeat the idea to create something new. Wayland is here, because it needs to do things differently. It’s the same as Linux operating systems will never be ready for every Microsoft user. And that’s okay.

Nothing changes much, its just the elements are all from top to down now and wider. I liked the old one more, where I had to less scroll. This new layout is more smartphone focused with vertical layout, while I use my big pc screen with horizontal layout. It’s just not good. The only positive side is, it looks less cluttered and it is straightforward.

I believe it, if I see it with my own eyes.

I think that I’m going with these approaches. For the ‘0’, I’m now accepting it as the 0 element. Which is not 0 based index, but it really means before the first element. So any slice with an END of 0 is always nothing. Anything that starts at 0 will basically give you as many elements as END points to.

• 0: is equivalent to : and 1: (meaning everything)
• 0 is equivalent to 0:0 and :0 (meaning empty)
• 1:0 still empty, because it starts after it ended, which reads like “start by 1, give me 0 elements”
• 1:1 gives one element, the first, which reads like “start by 1, give me 1 element”

I feel confident about this solution. And thanks for everyone here, this was really what I needed. After trying it out in the test data I have, I personally like this model. This isn’t anything surprising, right?

Now that you ask, I don’t have any example of this. I know program head has negative numbers to access from the last element backwards ls -1 | head -n -1, but it does not start by 0. So yeah, the 0 as last element might be not as common as I thought to be.

No, that’s not an option here. This is a commandline program, something like grep in example. And this slice is just one of the many features the user could use to refine the output.

But contrary to that, often ‘0’ is also used as the last element or points to “the entire match” in example. Whatever that is. I feel like outside of programming languages, for the end user, its not that clear of an answer. Why I created this topic.

I’ll read the linked article and rethink this topic. Maybe introducing another option to make the index 0 based (or the other way 1 based).

First, thanks for the answer. As for the user base, its actually gaming oriented and they typically do not interact with 0 base. So I guess that makes for an obvious choice. And at the moment its also “inclusive”. To get one element user needs to 2:2. If user gives only one element, such as 2, then I could convert it into 2:2, to get one element. Sounds logical, right? Sorry for having so many follow up questions, my head is currently spinning.

Do you think this interferes somehow with the logic of a “missing” slice element, which would default to “the rest of the list”. In example 2: would then get the second element and until rest. This is the default behavior in Rust.

If I have a 1 based index, how would you interpret the 0? Currently program panics at Argument interpretation phase.

Your final score: 9/26

There were more nuances and surprised than anticipated. But it should be expected, because its on this website. :D But any language with duck typing and lot of magic and interpretation, and a long history of changes and additions, used in a huge variety of environments, is bound to be surprising. I am not surprised that JavaScript and Python are surprising.

I’m skeptical, because of the huge fps differences they claim. I mean OBS dropping from 30 to 7, compared to stay at 30 for GSR sounds like either the hardware or drivers are not fully supported on OBS and its dependencies, or maybe a misconfiguration. Maybe OBS + Nvidia does not support Wayland fully yet (or at the time of writing the statement from him/her) and that caused issues? At this point, who knows, without more information we can only guess.

I have the same doubts as you and wondered the same when reading those paragraphs about performance claims. I will most likely do my own comparisons, but I have AMD hardware here. The claims talk about Nvidia, so maybe its not applicable to me. I’ll do my comparisons in the next few days, because currently working on something else.

From my research, I found an old gamingonlinux article, with a quote explaining this on a high level: https://www.gamingonlinux.com/2022/04/a-developer-made-a-shadowplay-like-high-performance-recording-tool-for-linux/

OBS only uses the gpu for video encoding, but the window image that is encoded is sent from the GPU to the CPU and then back to the GPU. These operations are very slow and causes all of the fps drops when using OBS. OBS only uses the GPU efficiently on Windows 10 and Nvidia. This gpu-screen-recorder keeps the window image on the GPU and sends it directly to the video encoding unit on the GPU by using CUDA. This means that CPU usage remains at around 0% when using this screen recorder.

Have in mind, these claims maybe not true anymore, because OBS improved over the last 3 years too. Always take claims like these with grain of salt (that is healthy).

Inspired is a bit an understatementf :D I don’t see this as a bad thing, because people used to like it on Windows now get a similar GUI. However you should know that there are two different user interfaces. The Nvidia like one is in experimental phase and you have to opt into it. It looks very familiar:

The only little thing that bugs me in the moment is, that I don’t get a tray icon to show if its recording or not. The icon appears with the old GTK gui, but not when using the Nvidia like gui. Do you have any such issues? If that is an issue at all or is this a design choice?