I don’t know about gnome, but on KDE you can disable touch support under settings>mouse & touchpad.

Unionize. Have companies pay you fairly for what you do.

The problem with that here I. The states are two fold. First of all if the companies could, at least here in the states, they wouldn’t allow unionization. They don’t want to pay fairly for what you do. All these companies want to do is make as much money as possible, while paying the workers as little as possible.

Most of the companies here would like us to work until we die on the lines, but pay us nothing to do the work so they could make it all. Companies don’t give a damn about workers rights, or being fair to us. A lot of non-union shops will fire you for trying to bring a union in. They would be extremely happy if the labor boards, OSHA etc would cease to exist.

It’s a KWin scrip called Autocompose. Does endeavour ship it by default?

Endeavour installs a mostly default DE when you make your choice of which one to use, so most of the DE’s come as packaged by the devs. If I’m not mistaken Autocompose is a default script included with KDE.

I say mostly, because some parts of the DE you use is incompatible with the Arch ecosystem and disabled by default. For example, Discover on KDE is pretty much unusable on arch/EndeavourOS because the repos aren’t adequately designed for such a setup.

So do snaps and flatpacks. And they are still consider containerized / sandboxed. Appimages are the predecessors to snap and flatpack. The only difference is unlike Appimages they got it right for the most part.

Generally speaking the Appimages integrate with KDE better than all the other DE’s. The codes for Appimages are still containerized from the OS in general as defined in my last post.

Unlike snaps and flatpaks, Appimages aren’t containerized or sandboxed at all. They are only used to bundle (some) dependencies, so you don’t need to rely on packages provided by your distro’s package manager.

You might want to look up what Appimages are as well as what containerization is. To help I have found the following.

AppImage aims to be an application deployment system for Linux with the following objectives: simplicity, binary compatibility, portability, distro agnosticism, no installation, no root permission, and keeping the underlying operating system untouched.

Source: https://en.m.wikipedia.org/wiki/AppImage#:~:text=AppImage%20is%20a%20format%20for,developers%2C%20also%20called%20upstream%20packaging.

As stated Appimages are containerized/sandboxed as it prevents needing to install any files on the OS.

Containerized applications are applications run in isolated packages of code called containers. Containers include all the dependencies that an application might need to run on any host operating system, such as libraries, binaries, configuration files, and frameworks, into a single lightweight executable.

Source: https://cloud.google.com/discover/what-are-containerized-applications

As you can see, once again, your info is incorrect as this is another example of what Appimages are.

The thing about snaps and app image is they are containerized. The idea behind that is to help keep the apps separate from the main file subsystem by sandboxing them from each other as well as not cluttering your hdd with different versions of the same libraries to make them work.

Because of the sandboxing, once you close the app it stops running in the background therefore there is nothing to get notifications from.

IMHO, this is why snap and app image programs are not advisable for programs you may need notifications from on a, generally, required/needed basis.

As for superconductivity, the only way around that problem is to download from source, compile it and let it run natively on your system in the background, or add it to you auto startup list so it is running at boot time.

Ubuntu wants you to use snap for all your app needs. I think their plan is to make repos only for os maintenance and installation and nothing else.

I have found over the years you can apply a lot of the directions to whatever distro you are using. You just have to do some minor tweaking to the commands. Primarily using the right package manager command for your distro or using distro specific software in place of arch software. I have also found you can use a lot of the AUR programs by searching for said app in your repos.

Or they can use EndeavourOS if vanilla Arch is too complicated. You’ll still have to install things like libreoffice, steam etc. but you don’t have half the learning curve you do with vanilla arch

And probably expensive as hell to boot. Although to be fair as an IDE it does work well. I can code just like I was in an IDE. It literally suits my needs when using python, rust or any other markup language. Even seems to do some autocomplete for me.

I honestly thought they were the same really.

The only stuff I miss is the way dreamweaver worked back in the day where you can see wysiwyg as well as the code. But that was yesteryear where adobe wasn’t as money hungry

it’s also a case of micros$ucks wants to completely dominate the market and remove any type of GNU/Linux OS competition. They don’t care about the users, they only care about $$$$$

I did forget to mention that. I don’t like flatpaks and avoid them if possible. Guess you could say I’m a Linux purist lmao

It is code, sorry for the miscommunication. My question on that though is what is the differences between the two? I don’t use micro$uck crap anymore. Haven’t for almost 15 years.

Visual studio is available on Linux as a native app from the AUR and some distros repos, I use VS on my endeavourOS with no problems, other than it has a slight tendency to be slow on launch, but that may be due to hardware age.

EndeavourOS with KDE

Same systems as vanilla arch for packaging such as pacman and AUR

Archwiki instruction work without modification

Great forum community without the incessant RTFM

Because there are distros, like fedora for one, that have flat packs installable by the likes of discovery on KDE that doesn’t require CLI useage for install or uninstall of flatpacks

Most do but not all. Unfortunately there are people that only visit one or the other. I’m not saying it’s an issue, but it will be if we reach a point of having 10 or more of the same communities.

I agree, currently the fediverse is a wild frontier and we have new communities showing up constantly. However, we also don’t want to overburden users with a plethora of ,basically, duplicate communities. For example to my knowledge there are 2 asklemmy’s and 2 Linux communities that do the same thing, they are just on different instances. For now I think programming at this point should work to cover the basic principals of all programming aspects, if it gets too cluttered, then like mentioned already, we can start separating out the different languages.

That’s awesome, sounds like hearted may have saved your drive useability.

Kinda depends on the software used to format the drive originally iirc