Rikj000

Wayland might be the future,
but today we’re still living in the present…

I was a fan, and tried Wayland,
but it took less then 24hrs before I switched back to X.

Just too many random bugs remain in Wayland rn…

E.g:

• Grayed out screen under HDR
• LookingGlass unable to boot in fullscreen
• Some program icons replaced with Wayland icon when running
• …

Wikiless?
The original project was taken down by Wikipedia, but this appears to be an active fork of it:
https://github.com/Metastem/wikiless

I went with Manjaro due to the way they do their package releases.

Arch is bleeding edge,
a double edged sword if you ask me,
all the latest versions,
and all the bugs that come along with them.

I’m looking for stability in my daily driver though.

Manjaro keeps releases a few weeks back on their stable branch.
And tests the releases first on their unstable and testing branches.
Resulting in near bleeding edge with enhanced stability on the stable branch.

For me the experience has been:

• Stable
• Easy to use
• Enjoyed all the Arch niceness in the meantime.

Which imo makes it a good distro,
idiots would not make a good distro…

Sure the people behind it made some doubtful decisions in the past, but that doesn’t change the fact that using it has been a bliss.

Additionally, it’s all open source,
so if they would ever turn anti-consumer,
it can be forked into another distro.

As I mentioned earlier, stop the distro hate.
I’m not throwing acquisitions against other distros, instead I let people enjoy whatever flavor of Linux they desire…

By now I helped a fair amount of Arch and other distro users through Lemmy / AUR / Issues, and I also learned a fair amount of Arch / Manjaro and other distro users.

Linux is not the enemy here,
not a single flavor…

Why?

It has been my main distro for years now,
and I have only enjoyed the experience.

2 points you’ll likely mention which do not make it a bad distro:

• The certificate of their website expired twice
• If you use AUR packages,
  sometimes you need to wait with an update since they hold back official repo packages for a few weeks to ensure stability, which AUR packages might depend on.

Stop the distro hate,
it divides the Linux community…
Instead we should unify against M$/iFruit,
and let people use whatever distro they like.

Your comment is my reasoning why I use Manjaro :P

All the Arch niceness,
with fewer bugs / breakage
and easier to use.

Sure you might get an issue from outdated dependencies from AUR packages from time to time, but the chance / impact of those is usually rather small.

Update your system frequently,
that minimizes the chance of things breaking in my experience.

I am confident in not giving a damn about Winpoop or iFruit and will stick to Linux instead!

Legacy software still requires maintenance.
Legacy dependencies still require to be used in new projects.
Dual booting multiple times a day is not feasible.

For those reasons none of my co-workers can fully switch to Linux.

I write PHP on the daily and don’t understand the hate it gets :/

At least I can work on Linux at home while my co-workers are stuck on Windows with their C#

WASM projects can be open source,
just like Android apps can be.

However in both instances the compiled versions of it are not easily readable.

Also you can validate binaries against a shasum to ensure no tampering has happened with them.

WASM = WebAssembly,
this has nothing to do with Java,
but with JS (JavaScript).

JS works with JIT (Just In Time) compilation, meaning every user that requests a web page, will request the JS and your browser will compile that JS on the fly as you request it.

WASM on the other hand is pre-compiled once, by the developer, when he/she is making the code. So when a user requests a WASM binary, they don’t have to wait for JIT compilation, since it was already pre-compiled by the developer.

They only have to wait for a tiny piece of JS,
which is still JIT compiled,
a tiny piece of JS to load in the WASM binary.

This saves the user from waiting on JIT compilation and thus speeds up requesting web pages.

WASM also increases security,
since binaries are harder to reverse engineer then plain text JS.

Due to those reasons,
I believe WASM will be the future for Web development.

No clue why people are hating on WASM,
but I guess they just don’t grasp all of the above yet.

Flatpak:
To limit shady proprietary software from accessing your full storage / hardware.
You can manage the sandbox access through tools like FlatSeal.

Snap:
To ruin your day / user experience.

Both where introduced as a universal way to distribute packages on various distros.

Enuf with the Arch hate already…

Fedora and Debian are cool,
but Arch is too,
their Wiki is amazing and so is the AUR.

And no I don’t use Arch btw,
I use Manjaro,
which has suited me fine for years now.

You can try rolling back to a previous version though.

By checking the log section in the AUR,
you can see all the commits (changes) done to the build files.
https://aur.archlinux.org/cgit/aur.git/log/?h=util-linux-selinux

Clicking on a commit message shows you the diff.

Start by the last commit,
undo the changes (green lines),
re-apply the removals (red lines),
then attempt to re-build.

If that did not work out,
do the same for the commit before that until you rolled back up to the latest working version.

If working with the AUR,
you can alter the PKGBUILD and other build files on your own behalf.

To either fix what’s wrong,
or to roll back to a previous version of the package.

I’ve did both a few times already,
however I’m on Manjaro.
Pamac, their graphical installer,
prompts me if I’d like to edit the build files before starting the build/install process, unsure how to do it in Arch, but the ArchWiki should be able to tell you.

Also, if you’d fix what’s wrong,
please post your diff on the AUR package thread, that can save the maintainer some work / help with rolling an updated package out to the other users faster.

It automatically happened,
I believe with every install of an updated Flatpak, which is rather often.

Been a while though, since lately I’ve been happily using AMD for quite some time.

But I do recall Nvidia driver updates slowing down my update process by a lot,
while I have none of that with AMD.

You can try to convince the Discord server moderators to bridge their servers to Matrix with something like T2Bot:
https://t2bot.io/discord/

That’s what I did when I was running a Discord server,
worked nicely in both directions.

Even not the “issue” that basically every time you update something, you have to wait a long time to download proprietary nvidia drivers?

That’s what annoyed me the most back in the day with the Nvidia drivers,
so many hours wasted on updating the drivers.

With AMD, this is not the case.

And haven’t even talked about my issues with Optimus (Intel on-board graphics + Nvidia GPU) yet, which was a true nightmare, took me weeks of research to finally make it work correctly.

In my experience,
AMD is a bliss on Linux,
while Nvidia is a headache.

Also, AMD has ROCM,
it’s their equivalent of Nvidia’s CUDA.