Quoting: hardpenguin

Quoting: CatKillerIt's generally quite straightforward: they aren't very good at game development.

The, "oh, but the sales," or, "oh, but the fragmentation," or, "oh, the graphics drivers," are just flimsy excuses because they don't want to admit to themselves that they kinda suck at their job.

No. And saying things like this only proves you have no idea not only about game development but also project management.

Making a game multiplatform from the start lets you make your game better cheaper, faster, and easier even if you never make a single sale on another platform. When you're looking for bugs to squash you want to throw your code at everything you can find. Different compilers, different environments. Bugs in your code might be elusive (but still present) in one environment, but be able to be replicated every time in a different one, which lets you find it and fix it. Making something work on Linux gets you a whole bunch of different compilers and environments for free, which helps you debug your code that you might also be using on Windows, PlayStation, Xbox, Switch, wherever. And, hey, now that your application is nicely modular and spec-compliant, with separation of tasks, and survives all sorts of changes in environment, you've got handy entry points should you want DLC, or to help with modding through Steam Workshop if you want.

But please, tell us more about how sloppy coding practices aren't a sign of sloppy coding practices.

View this comment - View article - View full comments

Quoting: hardpenguinBooo.

I am pretty sure they had good reasons but it is a pity they did not care enough to share them with us.

It's generally quite straightforward: they aren't very good at game development.

The, "oh, but the sales," or, "oh, but the fragmentation," or, "oh, the graphics drivers," are just flimsy excuses because they don't want to admit to themselves that they kinda suck at their job.

View this comment - View article - View full comments

With a bit of luck, this might be the kick up the bum that Unity needs to sort out the video decoding in their client. Do you have contacts you can suggest it to, Liam?

View this comment - View article - View full comments

Quoting: randylThis is a great development for System 76 users in my opinion. It doesn't solve the Gnome control freak issue for anyone else, but it's good for S76.

It does somewhat. By making it its own thing, with its own name, it makes it easier to be picked up by others if they want it, rather than "that set of patches that Pop has." Much like, say, Cinnamon or Mate did.

View this comment - View article - View full comments

Quoting: slaapliedjeMy understanding also is that Xorg is not 100% dead, it's just resting. They've nailed it to the perch, so to speak. Beautiful plumage.

They are maintaining it, there were some modules updated like a month or so ago.

What changes there have been are to make XWayland work, which is being spun out into its own thing so that it will actually be released. Pining for the fjords.

View this comment - View article - View full comments

Quoting: Purple Library GuyRather, in real life there seem to have been many efforts to give X upgrades and overhauls to deal with various issues, and the developers finally hit a wall where they didn't see any way forward except to start fresh. I'm not a techie, but on a non-techie level I've been following all this for many years, and it seems the problem is that how applications, graphics cards and their drivers and so on want to interact with screens has changed a lot since X was first written; the whole paradigm just doesn't apply any more and getting it to pretend gradually became kludge upon kludge upon kludge.

Yep, pretty much.

X was state of the art in 1984. For comparison, the GPU as we understand it now was invented some 15 years later.

The biggest change is how multiple windows are combined - composited - to create something that's drawn on a screen. That's an extension for X rather than part of the main thing - support for bitmapped fonts and being able to draw dashed lines are part of the main thing - but it's where all the actual work is done. And the other parts of the functionality of X have changed, too: input handling is completely different now, and throwing bitmaps over the network is not really terribly efficient.

So Wayland makes the compositor the central part, uses more relevant input and output handing, and gets rid of the network stuff entirely.

There are aspects of Wayland's design, implementation, and history that, in my view, have hampered its adoption and desirability. But it's what we've got, since Mir didn't take off and X is no longer fit for purpose, so we have to make the best of it.

View this comment - View article - View full comments

Quoting: Purple Library Guy

Quoting: CatKiller

Quoting: redneckdrowIs there any reason to use Wayland other than the perception of security for the end user?

X is entirely and completely unmaintained. Its known flaws will never be fixed; flaws discovered in the future will never be fixed. The people that used to work on it don't want to any more, and only work on Wayland now. Xorg 1.21 hasn't been released because there's no one interested enough to do so. It's kicked the bucket, shuffled off its mortal coil, run down the curtain, and joined the choir invisible.

This . . . is an ex-X!

"X.parrot Server" occurred to me after I'd hit the Post button.

View this comment - View article - View full comments

Quoting: redneckdrowIs there any reason to use Wayland other than the perception of security for the end user?

X is entirely and completely unmaintained. Its known flaws will never be fixed; flaws discovered in the future will never be fixed. The people that used to work on it don't want to any more, and only work on Wayland now. Xorg 1.21 hasn't been released because there's no one interested enough to do so. It's kicked the bucket, shuffled off its mortal coil, run down the curtain, and joined the choir invisible.

View this comment - View article - View full comments

Quoting: scaineBut instead, he's just back and that's it? Okay then. As I say, FSF can get in the bin alongside him. Some will support this move - fine. I just don't. It hurts free software, it drives women away in particular and I don't want to be associated with any of it.

There's a reason the labs at MIT are full of plants.

The FSF have rendered themselves completely irrelevant by their continued association with rms. The Free Software movement will continue to be championed by, say,

3NSoft
Aaru Data Preservation Suite
Calyx Institute
Ceccun
CH Open
CommitChange
Creative Commons
Cusy
Data + Feminism Lab, MIT
DataMade
Dot HQ
Echap
Espen Gottschal (Norway)
Exercism
Exherbo Linux
Exodus Privacy
EZPZSoftware
Ferrous Systems GmbH
Fivnex
Framasoft
Freedom of the Press Foundation
GlobaLeaks
Globenet
GNOME Foundation
GNU Mailman
GNU Radio
Great Scott Gadgets
Innatical
Kludge Cyber Systems
LineageOS
May First Movement Technology
Metaform
MidnightBSD Project
MousePaw Media
Mozilla
OBS Project
Open Life Science
Open Observatory of Network Interference (OONI)
Open Source Collective
Open Source Diversity
OpenTelemetry
Organization for Ethical Source
Outreachy
Palante Technology Cooperative
Progressive Technology Project
Public Laboratory for Open Technology and Science
RACTF
Radial Source
Riseup Networks
Sanctuary Computer
Solidaires Informatique
SumoStack
SUSE
TEN7
The FreeDOS Project
The HardenedBSD Foundation / The HardenedBSD Project
The Linux Experiment
Tor Project
Velvetyne – Libre and Open Source Foundry
wiquaya.org
X.org Foundation
April
Document Foundation
EFF
Fedora Council
FSFE
KDE
May First Movement Technology
Mixxx
OpenUK
Organization for Ethical Source
OSI
Outreachy
OW2
Public Laboratory for Open Technology and Science
Red Hat
Software Freedom Conservancy
Solidaires Informatique

and the rest of us will try to minimise the harm done by the FSF.

View this comment - View article - View full comments

Quoting: PopeRigbyWhy is the percentage of Linux sales so huge?

It's higher than you might naively expect by the market share on Steam because they actually did marketing amongst the Linux crowd, rather than simply pressing the "build for Linux" button and throwing it over the wall unannounced (and untested) like a distressing number of devs do.

It's high percentage-wise on Humble because they had a sale on Humble at the same time as they announced the release of the Linux version.

View this comment - View article - View full comments