Quoting: ArehandoroNot too keen in shitting my pants with scary games but this one does look cool... Maybe I get it once is released on GOG :)

WARNING: Must play while constipated! Or keep squeegee nearby.

View this comment - View article - View full comments

Quoting: CimerydLooks cool, and if it comes out I'll likely buy it, but I've been burned in Kickstarter before. Through the Woods also had a Mac and Linux version promised, even demos. Then Antagonist took the money and went to work making a Windows only game. That was sadly the last time I would trust an unmade game to be released for my platform.

I only trustrust those that have delivered before. Like inXile. Waiting on Bard's Tale 4! I should beat the first three, I suppose...

View this comment - View article - View full comments

Well, their announcement LITERALLY said ATI, not AMD. So yeah, it doesn't run on cards that are 10+ years old? :P

View this comment - View article - View full comments

Quoting: razing32

Quoting: slaapliedjeI just think instantly of Kickstarter on the atari 8-bit. Loved that game..

Give us a link :P

My bad, it's Kik-Start. https://www.youtube.com/watch?v=W1DoWRk50jQ

I wonder if anyone on this board is a fan of the Atari 8bits... I got mine with the full load of mods... and then ended up bricking the damn thing so now I'm waiting for my EPROM burner, which should arrive tomorrow.

View this comment - View article - View full comments

I just think instantly of Kickstarter on the atari 8-bit. Loved that game..

View this comment - View article - View full comments

Quoting: jens

Quoting: slaapliedjeSo... the whole docker/flatpak/snap thing... Isn't this in essence what .dmg files are on a Mac? The container itself has lots of files in it, but the user only sees the executable file

Remark: I have a lot of experience with Docker, have played a little bit with flatpack and no experience at all wit snap.

Well, you shouldn't compare containers with package formats. While they both serve a similar purpose, bringing software to your machine, the concepts are differently. It is not just about how packaging works, but mostly how it behaves. Isolation and layers are the keywords. Looking at Docker from a functional perspective you'll see more similarities with Virtual Machines, but without the guest OS overhead. Every container runs natively on the host machine, but has its own runtime, own file system and its own network adapter. You are able to run e.g. multiple mariadb/database server containers in different version on the same host with just a few commands (very useful for development when you need to simulate a bigger cluster on a single machine). I strongly advise to play a little bit with docker, it's very easy and once you got the difference between image and container the penny will drop. Flatpack is similar but with focus on UI applications. Same with docker, isolation makes the difference. You can run e.g. run Gnome-MPV on a Gnome 3.26 Runtime and Gnome Twitch on a Gnome 3.24 Runtime without any interference between the flatpaks.

All container solution seems overkill at the beginning, but once you got the gist they aren't. I certainly see the benefits, for both background processes via docker and UI applications via flatpaks.

See also: https://docs.docker.com/get-started/

I have used docker, the engineers love it at work. I agree it is great for development. But when moving to production where the hardware is there and you don't want multiple containers floating around, it is much better wothout them. Of course this all depends on how many different applications make your 'stack'. I set up FreeNAS with a bunch of jails and it was a pain getting all of the various IP addresses and services split up to talk to each other securely. I ended up ditching that and going with openmediavault, which supports docker as well, but it is easier for me to just throw it on the host system, since I don't need to separate them out.

View this comment - View article - View full comments

Quoting: Brisse

Quoting: slaapliedje

Quoting: jens

Quoting: slaapliedjeMy problems with Wayland are similar. That and there are unnecessary pushes to force people to use it when it clearly isn't ready. Debian a while back had changed the default session for gdm to start Gnome Shell with Wayland.

Are you sure Debian did this, I would not expect such move from them?
Fedora did the same a few releases back. The decision to switching default to Wayland is a tough one. At some point you need to release software and bring in into the field, otherwise it wont mature at all. For a distribution like Fedora, being bleeding edge everywhere, this seems a valid move. More stable distributions like Debian should indeed hold back for a while.

It was in Debian Sid, they'd never do it in Stable of course. From the gdm3 changelog

gdm3 (3.24.2-2) experimental; urgency=medium

  * Drop d/p/Hack-D-Bus-messages-from-Debian-8-libgdm-to-work-wit.patch now
    that debian Stretch has been released
  * Drop d/p/09_default_session.patch: Start the "gnome" session by default,
    "default" is always starting a X11 session but we want to start a Wayland
    one starting from now.
  * debian/patches/92_systemd_unit.patch: Uncomment the BusName= directive,
    gdm doesn't seem to be killed on reload anymore

 -- Laurent Bigonville <[email protected]>  Thu, 06 Jul 2017 01:30:35 +0200

Drop d/p/09_default_session.patch: Start the "gnome" session by default,
"default" is always starting a X11 session but we want to start a Wayland
one starting from now.

And what's the big deal? Why get upset? It's Debian Sid after all, which is aimed at tech savvy folks who want to participate in development. Upstream GNOME has been doing Wayland as default for ages. Fedora has been doing it for quite a while. Ubuntu 17.10 does it. Arch does it etc... Also, X.org is still provided out of the box and it's incredibly easy to switch back, but if Wayland is ever going to shape up it needs to be pushed by bleeding edge distros.

I wasn't upset. It was annoying, figured out pretty quickly why the copy/pastre buffer was broken. Problem being that I have some Qt apps which haven't added Wayland support. Sounds like the other guy was more upset about screenshots not working. Sadly on the one hand when it is breakage 'by design' (middlemouse click was broken for a while to paste) you end up switching back to what works instead of helping test things. For sure they need to break less things in the transition or no one will want to use it.

View this comment - View article - View full comments

So... the whole docker/flatpak/snap thing... Isn't this in essence what .dmg files are on a Mac? The container itself has lots of files in it, but the user only sees the executable file.

Yes this makes re-using system libraries annoying. But unless it's a gtk/qt based launcher, and the SDL libraries themselves, what all shared libraries are used? The OS should be handling input, etc.

The 'oh my god, it's hard to distribute/package software for Linux!' has been debunked years ago, there are automation tools around now that does pretty much all the work.

View this comment - View article - View full comments

Canceled my monthly subscription with the reason being "IGN ownership"

View this comment - View article - View full comments

Quoting: jens

Quoting: slaapliedjeMy problems with Wayland are similar. That and there are unnecessary pushes to force people to use it when it clearly isn't ready. Debian a while back had changed the default session for gdm to start Gnome Shell with Wayland.

Are you sure Debian did this, I would not expect such move from them?
Fedora did the same a few releases back. The decision to switching default to Wayland is a tough one. At some point you need to release software and bring in into the field, otherwise it wont mature at all. For a distribution like Fedora, being bleeding edge everywhere, this seems a valid move. More stable distributions like Debian should indeed hold back for a while.

It was in Debian Sid, they'd never do it in Stable of course. From the gdm3 changelog

gdm3 (3.24.2-2) experimental; urgency=medium

  * Drop d/p/Hack-D-Bus-messages-from-Debian-8-libgdm-to-work-wit.patch now
    that debian Stretch has been released
  * Drop d/p/09_default_session.patch: Start the "gnome" session by default,
    "default" is always starting a X11 session but we want to start a Wayland
    one starting from now.
  * debian/patches/92_systemd_unit.patch: Uncomment the BusName= directive,
    gdm doesn't seem to be killed on reload anymore

 -- Laurent Bigonville <[email protected]>  Thu, 06 Jul 2017 01:30:35 +0200

Drop d/p/09_default_session.patch: Start the "gnome" session by default,
"default" is always starting a X11 session but we want to start a Wayland
one starting from now.

View this comment - View article - View full comments