Quoting: slaapliedje

Quoting: Arcadius-8606Anyone have the beamdog client installed properly? Thought I would give this some support and it's a no good install for POP OS 21.04.

Harfbuzz version too old error.

Yeah, this is one of the issues with how people package things. It makes more sense to have a build server set up. Create a repo for the current distributions at time for release, then add a new repo as they come out, and have some post install stuff for upgrades.

This way a new package automatically gets built with the correct dependencies. Problem is getting the build server to handle the main distributions.

Building games can take hours. If you want to do a separate build for all major distributions, that's a massive waiting time...

I'd rather package once on Debian Stable and then just test if the built package installs on other distros.
In addition, I'd do what Unity does, and link a lot of libraries statically. Not all, of course, only those where it makes sense from an upgrade- and security-standpoint. For applications packaged by the distributor static linkage is not a good idea, but for standalone programs packaged by someone outside the distribution I think the advantages (being independent of system library versions, no need to integrate with the package manager,...) outweigh the disadvantages (higher RAM usage, higher HDD usage, responsibility for security updates,...).

View this comment - View article - View full comments

I consider catering to users who intentionally ignore critical warnings a step in the wrong direction.

I'm not trying to be elitist, but seriously, if there's a very clearly worded meessage telling the user that they are going to break their system, it's the user's fault if they type in "do as I say"...

View this comment - View article - View full comments

Quoting: rustybroomhandleAgain, sorry for being a broken record, but devs just do not realize the amount of heavy lifting done for them by Valve/partners/community and probably don't appreciate it nearly enough.

This.
There is a steamworks forum about Steam Deck for game devs, and if you look in there, you get a glimpse of how much they actually do. There's also a lot of work going on beyond "just" being compatible to Windows APIs.

View this comment - View article - View full comments

Quoting: elmapul"- SteamOS will have a read-only immutable main filesystem by default. Updates will be distributed as a whole image and so it will replace it. There will also be a developer mode to let you modify the filesystem."

that is the part i dont get...
how they plan to allow people to install stuff then?
i mean, either you will have to rely on stuff that dont mess with the filesystem (eg: flatpaks, app images) stuff that dont install, update or remove dependences.
or you have to use developer mode to install anything that is not on steam.

Yeah, it pretty much reads like they don't expect people to install stuff anywhere except for their Steam Library folder...
I guess the argument here is that the Steam Deck is mostly meant as a gaming device. That standpoint is understandable imho, as without external peripherals the device is not usable for much else.

If I were to use the Steam Deck in Desktop Mode, I honestly would nuke SteamOS in favour of a less gaming-centered Linux distro though.
(Okay, we all know I'm going to do that anyhow, because maintaining a Gentoo install is my favourite game, and the Gentoo team keeps releasing new levels for it. :grin:)

View this comment - View article - View full comments

Quoting: scaine

Quoting: soulsourceI just remember that I was annoyed enough to replace Ubuntu by Debian due to this, and to never look back...

You say that, but isn't that a Gentoo logo next to your avatar?? :grin:

Yes, but that came much later and not for any work-related stuff (if I could use Linux for work nowadays, I'd still be running Debian on those machines - the same for servers, btw.). Also, Gentoo isn't Ubuntu, is it? :wink:

View this comment - View article - View full comments

Quoting: scaine

Quoting: soulsource

Quoting: drmothCanonical's Unity, once the bugs were fixed, was actually really good.

Canonical's Unity was basically the Gnome desktop environment with Compiz as Window Manager (and some hacks to GTK). It only worked as long as you didn't dare to even think about opening CompizConfig. Once you even remotely considered changing any Compiz setting away from the GodCanonical-given default, your desktop was messed up beyond repair and your only option to get it working again was to nuke your compiz config files from orbit.

As unhappy as I am with recent Gnome, Unity was imho even worse...

As someone who frequently messed about with ccsm while using Unity, I do have to wonder what on earth you were changing to cause desktop instability!

Of course I exaggerated.
However by adding new features for Unity, some other features of Compiz got broken, and it seems I was just unlucky that those were settings I really wanted to use...
My memory is not that fresh any more, so I can't point my finger on which settings exactly caused Compiz to crash on launch, though... I think it was about focus following mouse or window snapping, but yeah, I'm not certain any more. In any case, it was nothing super-exotic, just stuff that I had been using with older Compiz versions before that.
I just remember that I was annoyed enough to replace Ubuntu by Debian due to this, and to never look back...
(Funny enough, with the switch to Debian I also ditched Compiz in favor of Xfwm, because I regularly hit swapping-hell on my office PC back then, and I found out that disabling compositing freed about 200 MB of RAM.)

View this comment - View article - View full comments

Quoting: drmothCanonical's Unity, once the bugs were fixed, was actually really good.

Canonical's Unity was basically the Gnome desktop environment with Compiz as Window Manager (and some hacks to GTK). It only worked as long as you didn't dare to even think about opening CompizConfig. Once you even remotely considered changing any Compiz setting away from the GodCanonical-given default, your desktop was messed up beyond repair and your only option to get it working again was to nuke your compiz config files from orbit.

As unhappy as I am with recent Gnome, Unity was imho even worse...

View this comment - View article - View full comments

Wow, that marketspeak is so bad, reading it causes physical pain... That doesn't make me optimistic about the chip's performance.

View this comment - View article - View full comments

Quoting: grumpytoad

Quoting: GuestThat looks great. Has Stellaris become fun yet? Or does it still take forever to get something going just to have nothing to do for the longest time and then start experiencing excessive amounts of micromanaging and insufferable lag?

I gave it another go recently using the starnet mod, which seems to fix the AI, and requires you to get something rolling pretty quick or you'll get steamrolled. Didn't see any lag, but then only played small maps.

Is Starnet fair? I mean, does it give the AI basically free ships and resources like the default AI does, or is it smart enough to actually build and rely on a working economy?

View this comment - View article - View full comments

Quoting: ShabbyX

Quoting: jordicomaWhat? A functionality coming from windows world that its good?

It's not necessarily good. If windows has feature X, games will depend on it. Now it may have been better if games did Y instead, but that doesn't exist and they are stuck with X.

Just because Linux now needs a way to implement X doesn't mean that X was the best option, just that because of windows we are now stuck with it.

This.
Usually the problem of having to wait on multiple events can be solved by building cleaner (more readable, better maintainable) software architecture. I'm writing "usually" on purpose here, as there definitely are problems where going for a cleaner solution is not worth the effort, or where indeed waiting on multiple events is the most readable implementation (to be honest, right now I can't think of a problem where the latter would be the case, but that's probably just lack of experience on my side).
However, synchronization by waiting on multiple events is nearly always the easiest (quickest, cheapest in the short-term) solution to implement. If there's a deadline coming up, it's almost certainly the solution that's going to be picked, even though in the long-term it might cost more due to it being inherently more difficult to read and debug.

Generally speaking, if an API offers certain functionality, it will be used sooner or later. If one wants to be compatible, that functionality has to be there, and has to be about as performant as the original implementation (at least have the same asymptotic scaling behaviour).

View this comment - View article - View full comments