What context? You should use the body of the post too, to explain in detail what you ask.

After 12 thousand years.

That’s interesting. But man, the project name is not very memorable.

It is not irrelevant to me and I made it multiple times clear. Its a suggestion by me, regardless of what terminology you use or the team uses. The desktop edit change is a big change which I suggest not to do for a year. Only bug fixes and small changes that enhance and improve usability. The desktop edit change is a huge change for the developers and for the end user, with lot of background changes to make it work correctly, with lot of fixes after it.

Something that complex is not a small change and is not irrelevant for the topic I brought up. I made it multiple times clear now, I don’t know why you are still act like this. It’s not a definition of a term we are trying to agree, I don’t care the term.

I don’t agree with you and explicitly listed it in my first reply as an example of what I consider a big change.

You misunderstand me. They can write new code and be ready when the bug hunting phase is over. The end user only gets bug fixes. Later they can backport any new feature after the phase.

https://wiki.archlinux.org/title/Installation_guide

I guess you meant this as a joke, but for clarification, I meant no big changes such as new desktop edit mode. I wish the team would just focus of bug fixes and enhancements without introducing new elements or changing things up in a big way like this.

deleted by creator

deleted by creator

I wish the team would just spent an entire year of bug fixing and refining user experience without adding new features or making big changes such as the new desktop edit mode. Don’t get me wrong, this is super exciting too, but for the complex nature of KDE it would be good if they keep a bit of focus after a major release.

It just came to my mind, that WINE not only stands for Wine Is Not an Emulator, but also could be interpreted as: WINdows Emulator.

The image does not doing a particularly good job in explaining whats wrong with X. It just shows how it functions and why a rewrite in Wayland is needed.

By that description, Ubuntu does the same, matching the release cycle of non LTS Ubunu versions; every 6 months with breaking changes (just like Fedora). The difference to Fedora is, that Ubuntu users do not need to upgrade to the next major version, while Fedora have to, because there is only one version.

Tiling: Add fallback path for the first Polonium tile. Commit. Fixes bug #488898

I’m a little bit surprised or confused here. Polonium is an external script. KDE/Kwin specifically addresses scripts? That’s actually wonderful, totally the opposite of what Gnome does (yes, I had to bring it up).

I stopped using Polonium, as it does not work perfectly fine for me. I’ll let them cook a bit more, its otherwise an excellent script/addon.

There is no single Bash standard to follow, only a few guidelines. One way you can check for some basic errors and formatting would be using an editor with support for Bash (in best case with a builtin LSP). At the end, you have to find your style and coding standards or adapt what others do if you want work with them or edit their files.

• Otherwise there is a well known tool for checking Bash files: https://www.shellcheck.net/ You can use it online and as a downloaded program on your local machine. After using shellcheck for a bit I got used to some of its conventions and recommendations, such as always wrapping variables like in ${variable} and some other things.
• Google has a coding style guide, but not everyone likes it: https://google.github.io/styleguide/shellguide.html
• Related is the Bash Reference Manual from GNU: https://www.gnu.org/software/bash/manual/bash.html Off course this is not a guide on how to style or program, but it helps in understanding how GNU does things.

BTW the mk-blog link is 404 for me.

https://www.laws-lois.justice.gc.ca/eng/acts/C-42/page-6.html#h-103344

Assuming this is the correct source for Canada’s law about copyright. In the section about backup copies 29.24 (1):

( c ) the person, in order to make the reproduction, did not circumvent, as defined in section 41, a technological protection measure, as defined in that section, or cause one to be circumvented; and

( d ) the person does not give any of the reproductions away.

So (d) means it is not allowed to distribute the backup copy. As far as I understand. This is standard in most countries in the world. Also I cited ( c ), because this is usually also standard law. Normally, you are only allowed to make backups, if you do not circumvent any protection. Well its up to the interpretation if the Switch has such protection measure that falls into this category. But still, for our topic, (d) is relevant and seems to not allow for distribution of backup copies.

Mind you, I am also not a lawyer. And not everything needs to go to court in order to have an understanding of the law. Off course, unless it is a bit of grey area like in the case of ROMs. But I think this is addressed in the above quote. I hope this is the correct source! So for the time being, I have to assume law regarding this is just the same as in most other countries, because there is nothing else for me to evaluate here.

Downloading Roms from others is basically taking their copy. Its not a copy of your individual cart. And that’s the thing. You have the right to make a copy of your cart and use it. But you are not allowed to distribute the copy. One could probably get away by using Roms from others, but that is open to interpretation of law for individual countries. However the distribution itself is not allowed, in any (normal) country. And I also don’t believe (believe is not knowledge, I have no knowledge of Canadas laws) distributing personal backup copies is allowed in Canada as well.

Using copies from libraries is something different BTW, as these are not personal backups and are meant to be used by many other people. But that can be complicated too, in example in case of Archive.org. It’s a library in the US, but not other countries in the world.

There are Switch owners who buy Switch games, dump (in other words backup copy) that on their PC as a ROM and then play it on the Switch Deck. Even this best case scenario is a grey area in some countries. And that is something most people won’t do.

You can if you own the Mario game…

Owning alone is not enough. You need to dump it yourself. Downloading others Roms, even if you own the game, is illegal. Because you are only allowed to play what you dumped yourself, not the backup copy of a different individual cartridge.