Someone told me that Teams is moving away from Electron to use the Edge web engine. This makes a lot of sense why they would be porting Edge to all the things, as they really want everyone using Teams to communicate. Which is also why it is being integrated straight into Windows 11...

Shame though that Teams is a dumpster fire of radioactive materials...

View this comment - View article - View full comments

I like the name, though I don't think it fits for what is essentially Steam on top of Arch. StarchOS. 😜

View this comment - View article - View full comments

I backed this one. Finally got around to playing it (via proton) the other day, and now the Linux version drops! I was just playing it to test out the red DualSense controller I have (which works great, though not terribly useful for this game, which is kind of odd with a controller).

The comedy is spot on for it, you end up just doing all options on each object just to hear all the jokes.

View this comment - View article - View full comments

Quoting: Nibelheim

Quoting: slaapliedje

Quoting: Nibelheim

Quoting: axredneck

Quoting: Nibelheim- It doesn't really support Debian, but Ubuntu and the author consider it "the same" (watch out for names and versions of dependencies which may not be the same between Debian and Ubuntu).

Even Debian has 3 different versions (4 with oldstable) with different versions of libraries. I wonder how these PKGBUILDs will manage this?
(Arch has 2 versions + Manjaro, but they differ very little)

Arch has 1 version since 2017, i686 support stoped. And before, the only difference was just 64 bits libs wasn't accessible to 32 bits Arch. Otherwise, everything was same (packages name etc...)

Manjaro is not Arch. Manjaro use his own repositories. Like Ubuntu is not Debian.

AUR has no Manjaro support. If something is not working on Manjaro, never ask about a fix to an AUR packager...

I thought Arch supported ARM now?

ArchARM exist but it's an independant project. You can't find any information about ArchARM on main arch website [External Link].

It's another distro based on Arch, maintained partially by the main Arch team.

And yes AUR packages usually works on ArchARM (I use it on PinePhone) but sometimes packages are x86_64 compatible only.

Somethings are simply written to only work on x86 or x86_64. Which is why most will end up having to rebuy their software for their Macs when they upgrade to arm ones.

View this comment - View article - View full comments

Quoting: Nibelheim

Quoting: axredneck

Quoting: Nibelheim- It doesn't really support Debian, but Ubuntu and the author consider it "the same" (watch out for names and versions of dependencies which may not be the same between Debian and Ubuntu).

Even Debian has 3 different versions (4 with oldstable) with different versions of libraries. I wonder how these PKGBUILDs will manage this?
(Arch has 2 versions + Manjaro, but they differ very little)

Arch has 1 version since 2017, i686 support stoped. And before, the only difference was just 64 bits libs wasn't accessible to 32 bits Arch. Otherwise, everything was same (packages name etc...)

Manjaro is not Arch. Manjaro use his own repositories. Like Ubuntu is not Debian.

AUR has no Manjaro support. If something is not working on Manjaro, never ask about a fix to an AUR packager...

I thought Arch supported ARM now?

View this comment - View article - View full comments

Quoting: axredneck

Quoting: Nibelheim- It doesn't really support Debian, but Ubuntu and the author consider it "the same" (watch out for names and versions of dependencies which may not be the same between Debian and Ubuntu).

Even Debian has 3 different versions (4 with oldstable) with different versions of libraries. I wonder how these PKGBUILDs will manage this?
(Arch has 2 versions + Manjaro, but they differ very little)

This is why I stick with backports (if I really want something stable) or just run testing.

I've ran Debian for decades at this point (even the same install on some systems and have just upgraded to the next stable release when it is ready). For desktop systems I just run testing, which the only time it gets semi-old is when they do a freeze in preparation for making the switch to it being the stable branch. This can last from 1 to 6 months sometimes, but when you look at the grander scale of things, that's not like it's ancient (libraries generally don't drop compatibility that often). Testing is basically Debian's rolling release.

Kind of sad that he just slapped the Debian name on there and considered them compatible. Ubuntu is a fork off of Debian Sid done every 6 months... Debian stable (if that is what he's targeting) has the potential of having 2 year old or more stuff in it.. Also one of the things that make PKGBUILDs easy to implement in Arch is that they don't differentiate -dev packages, and include the source with the binary.

View this comment - View article - View full comments

Quoting: ElectricPrismThe AUR is a great feature but mainly because the maintainers do such a good job curating content & keeping it up to date and fresh.

The philosophy behind Arch is also part of what makes the AUR great -- Keep It Simple Stupid.

I don't mind Debian stealing a page from Arch's book but I would really be encouraged to see everyone steal a page from Gentoo's book and essentially be able to install packages by compiling them from source with custom patches or installing bins.

I mean isn't that basically what AUR does? It just simplifies that with PKGBUILDs, but the PKGBUILDs pretty much do the 'git clone', patch, make, etc. Or if it's officially part of ARCH, it's a bin.

As far as releases go, ARCH has always seemed more stable to me than Gentoo.

View this comment - View article - View full comments

Quoting: sigmichMain reason I don't use Debian a while are outdated Nvidia drivers because I need stable branch for some specific software. Could DUR be used also for installing graphic drivers?

Backports has the latest stable drivers.

View this comment - View article - View full comments

Quoting: heidi.wenger

Quoting: axredneck

Quoting: Perkeleen_VittupääWhat about the security aspect as some instances are pushing these "convenient" ways to install stuff? The authors of these packages cannot automatically be trusted and confirmed, so on. The software pulled from this "Arch style repo" are not sandboxed like snaps and flatpaks can be :huh:

You can (and have to) manually read the PKGBUILD before installing.

huh a normal user certainly does not read nothing. at least those mentioned ways of snaps and flatpacks are in sandbox so the carelessness does not matter!

Normal users probably shouldn't run Arch (yeah, I know that is a gatekeeper atitude, but it goes for any rolling release distribution, also Fedora. 😜)
One of the biggest problems with AUR is that most packages end up becoming orphaned as the person building it stops using Arch, or other reasons. And then due to the rolling nature, you end up with old PKGBUILDs that will no longer compile.

On the flip side, maybe we can get Librewolf in Debian!

View this comment - View article - View full comments

Quoting: Nanobang

Quoting: slaapliedje

Quoting: NanobangLinux software for a hardware accessory? I mean, I'm aware it's done, but not enough for me not to sit up and take notice when something as sweet sounding as this Wooting keyboard comes along. Jeez, and I'd LOVE to get my hands on a full size British keyboard with it's spacious Enter key. (Apparently most Americans who are not me have no problem hitting that tiny Enter key on our keyboards).

I miss the spacious enter key! Also find it fun when trying to type on old computers, and figure out that Shift 2 is where the " is... Clearly the USA typers are more about the fat backspace key over having a fat Return key (that's right, I call it a Return key. I'm old, damnit!)

Lol, me too. The only reason I didn't write "(Carriage) Return" *DING* is I didn't want to lose the kids. And we have a big "Backspace" key because of all the mistakes we make trying to hit that tiny "Enter" key. XD

Real men use Control-H anyhow. 😜

View this comment - View article - View full comments