Most of my Steam library is shit I have no intention of ever playing. I’ve bought a TON of bundles that contain one game I actually want that justifies the entire purchase; one or two that look like they have some potential, so I’ll bookmark them for a rainy day; and like 15 digital turds that I now have the key to, so… why not, might as well activate.
Fanatical, or whatever they used to be called had rediculous bundles and is the reason why have have almost 1000 games on my account. There were times that I would be interested in one game, and it was cheaper to buy the bundle from them than the one game on it’s own from Steam.
That sounds right. I used to buy a ton even before the rebranding. Looking now, they have a bundle that has Dragon’s Dogma: Dark Arisen (currently $30 on Steam) for $20 with 32 other games, most notably Devil May Cry 4, which is still more expensive on Steam than the bundle. Crazy.
There’s so many games that I picked up that I’d played through/completed in my childhood, but they’ll likely forever show as unplayed in my Steam library. I’ve been slowly going back through my Steam library chronologically though, to try to at least reduce my unplayed games amount, and also to at least check out games I might’ve missed. I’m not forcing my self to actually finish the games, just play them for at least a few minutes, maybe mark it for follow-up later, but the point is to reduce my unplayed games list so I don’t feel as bad about it.
Yeah, the math for mine would definitely be off, just because I used to be a console gamer. A lot of the games in my Steam library I played on Xbox or PlayStation before, and picked up for PC when they were on sale after I switched over.
I haven’t played quite a few games I’ve paid for but a large part of that goes to small indie devs. I may not play their game but I support them and the work that they do.
I apparently have over $500 of unplayed games. However, looking at my library there’s a lot that I’ve played through that it shows zero hours, whether I used a script loader because of mods or for some reason it just doesn’t show that I’ve played the game (Bioshock series for some reason. I’ve played them all through).
I’ve also never payed full price for a game. Patient gamers unite! Just not right away.
A lot, probably most, of my hours on steam are from before they tracked it. I had 3,000 hours in CS:S and it shows 0 because I stopped playing long ago. Steams been around for a long time, much longer than its ability to track games, so I imagine there’s a lot of people with “unplayed” games that they’ve played, plus people like you that don’t show their hours for whatever reason.
Should all be in place. Even nvidia driver support. It’s one of the rare cases where I actually support nvidia on a technical level, that is, having explicit sync is good. I can also understand that they didn’t feel like implementing proper implicit sync (hence all the tearing etc) when it’s a technically inferior solution.
OTOH, they shouldn’t have bloody waited until now to get this through. Had they not ignored wayland for a literal decade this all could’ve been resolved before it became an issue for end-users.
No feelings either way, I started using X since the last millennium and have been on Wayland without problems (Gnome or sway, never anything more than integrated graphics card) for about four years now.
But I really wish there was an fvwm for Wayland. And Window Maker.
Yes, I spent a while reading the documentation on how to pin workspaces to certain monitors only for hyprland to tell me that it is deprecated.
Also an issue I noticed is that you can’t move floating windows between displays with the move left/right commands, move left/right moves the floating window to the left or right of the display and no more, meaning that the window gets stuck at the border of the display and doesn’t move more.
Also I couldn’t figure out how to make hyperland run several commands in a row with one keybind, or how to filter windows with expressions, something that I do a lot on my i3config .
And my biggest issue, and this one seems to be with wayland in general is that it seems that it is impossible to set my displays to extended more, that is turn the 3 displays that I have into a single display which I use with some games.
i3 isn’t perfect either, I actually had to fork it and apply a patch that fixes and issue that I have that hasn’t been merged yet either.
I will list all my issues with sway anyway, hopefully somebody out there notices it and fixes them:
I have workspaces pinned to monitors in Hyprland and have none of the problems you mentioned. I use odd numbers for left screen and even numbers for right.
Edit: just took a look and can’t find mention of the depreciation; where did you read that?
That’s just the way you write the rules being deprecated, not the functionality.
There is move left/right within a workspace, move to specific workspace and then move to next/previous workspace (from memory using e+1 as the workspace name in the command but might be misremembering). Admittedly this isn’t exactly the same as what you want; I replied from my mobile and checked when I went back to my desk. I usually use meta/shift/[num] to send to a specific workspace though as I make heavy use of them.
That’s just the way you write the rules being deprecated, not the functionality.
I didn’t say that it is impossible to do it, just that after I read the documentation it told me that.
Something that I couldn’t even find in the documentation was how to do several actions with one keybind, on i3 each action is separated by a comma and you can assign variables to them, for example:
In english that is move the focused window to workspace 1, focus workspace 1 and send a notification of the current workspace (the last one is for some visual feedback).
<span style="color:#323232;">### Multiple binds to one key [](https://wiki.hyprland.org/Configuring/Binds/#multiple-binds-to-one-key)
</span><span style="color:#323232;">
</span><span style="color:#323232;">You can trigger multiple actions with one keybind by assigning multiple binds to one combination, e.g.:
</span><span style="color:#323232;">
</span><span style="color:#323232;"># to switch between windows in a floating workspace
</span><span style="color:#323232;">bind = SUPER,Tab,cyclenext, # change focus to another window
</span><span style="color:#323232;">bind = SUPER,Tab,bringactivetotop, # bring it to the top
</span><span style="color:#323232;">
</span><span style="color:#323232;">The keybinds will be executed in the order they were created. (top to bottom)
</span>
X Windowing System is used in XWayland still. X11 Xorg is no longer needed. RIP X11 Xorg, you served us well.
Edit: Thanks to the note in the comments. I obvously meant Xorg is no longer needed, which is the widely used implementation of X11 protocol. This always confuses the hell out of me.
Wayland is still incomplete, but that is besides the point I was making. X is still not dead, even living within XWayland, within Wayland. X11 is just one implementation of the X Protocol and XWayland is a new implementation.
Wayland itself is functional and working, just not 100% compatible to X11. The same could be said about X11, it would be nice if they could get some basic functionality working right; but they can’t, and that is why we need to replace it with something more modern and better. I think Wayland is working on a solution for restoring window position and size.
When X was created, there was no compatibility needed. Wayland on the other hand is in a different position, where it needs to innovate, make it more secure and keep as much as possible compatibility to X11, DEs and window managers. It’s just unfair to just say Wayland would not have basic functionality working. It also depends on the desktop environments and GNOME is often to blame for.
It will never be compatible with X because they are different designs. X relies on a central program (server) that accepts commands from programs. It is also a mess as it was built during the 80s for 80s hardware. It was expanded over time but you can only stretch the arch so far.
Wayland doesn’t have a server. You desktop talks to the hardware and then the desktop accepts connections from apps.
That does not seem to be a stray and yes there’s definitely reasons to take potshots at Gnome. They still don’t support server-side decorations. Everyone is absolutely fine with them not wanting to use them in their own apps, have them draw window decorations themselves, and every other DE lets gnome apps do exactly that, but Gnome is steadfastly and pointlessly refusing to draw decorations for apps which don’t want to draw their own decorations. It’d be like a hundred straight-forward lines of code for them.
And that’s just the tip of the iceberg when it comes to breakage you have to expect when running Gnome.
No screen readers for one thing since they can’t access other windows. You’ll find that most accessibility features require access to other windows in some manner.
There’s a new accessibility framework being started by a Gnome developer very recently.
Which means, best case scenario where it’s perfect and other desktops buy in, it will roll out to traditional desktop users in half a decade at the earliest.
Am I to understand correctly that if you are running Gtk+ apps in the Gnome compositor, you get this working, but if you are running non-Gnome compositor with Gtk+ apps, it will not work? Or is it independent of the compositor?
I mean they can be made but it’s going to require reinventing a lot of wheels. You need access to other windows to make this (and lots of other stuff) work, period. Wayland has simply moved the burden of exposing that information to other layers. By the time this is accomplished 100% the information is going to be exposed just as much as on X11, just in a different way.
Because that’s like. the main feature about Wayland.
Is it? It has always seemed like a solution looking for a problem to me. When’s the last time you heard about anybody having a problem with this under X11?
In theory it can be used to do bad things. In practice it’s like wearing a helmet 24/7. It sounds like a good idea and it could help in case you’re in a car crash or a flower pot falls on your head… but the inconvenience makes you not seriously consider it.
My main problem with it is that they simply tossed the dead cat over the wall. You can’t simply say “fuck you deal with it” and call it a day, then expect all the rest of the stack to spend a decade solving the problem you created, while you get to look shiny for solving an “issue” that nobody cared about.
My other problem is that it should have been a toggle. Let people who really need to tighten security turn this feature on and let everybody else get on with their lives. Every other isolation feature on Linux (firewalls, AppArmor, containers etc.) is fully configurable. How would it be if your firewall was non-optional and set to DENY ALL all the time? It would be crazy unusable. Yet Wayland made that “the main feature”? Ridiculous.
Making screenshots does, too, which is why that functionality gets implemented at the compositor level. And so will screenreaders. In fact looking at my settings panel KDE does have support for Orca. Dunno how well it’s working but it’s not like the issue is being ignored.
just another reason to use tiling window managers ;) at least mine opens my windows in the same workspace on the same output every time, if i configure it to
Programs can’t set position or size of windows, period, at most they can ask and then hope they don’t get ignored and it’s good that way. Window management is responsibility of the compositor, not of applications.
lol, Wayland can’t even start a desktop session on my machine, whereas X11 has worked without issues since 2009 (the last time I ever had to edit xorg.conf).
Sure sounds like X11 is the one who’s “dead” around here!
We even disagree on what “dead development” means. :D ( Edit: To add a bit substance to my reply, minimal maintenance is not actively developed in my books. )
And almost all (if not all of it) is done by redhat engineers which will drop it when rhel 8 or 9 (whichever one still supports xorg) goes end of life.
Yep that’d be Wayland devs maintaining XWayland, which is part of the x.org codebase. There are no “X11 devs”, they’re the ones who started Wayland to get rid of that bowl of spaghetti!
It’s not dead there either, although I’d make the argument that X11 as a project is “mature” or “finalized”, it doesn’t really need hyperactive development like the tiktok children are used to.
(There are very good arguments that a new software stack was needed, but I’d expect the result to at least do something; ATM Wayland is little more than literally a “everyone else do my work for me” project)
I argue that X11 would have hyperactive development, if we did not have Wayland (or Mir, before it turned into a Wayland compositor). There are at least two major fields that do not work perfectly and cannot be changed by simple updates, it needs rewrite from ground up: a) advanced multi-monitor handling of different kind of monitors at the same time, b) security issues related to keyloggers, as apps are not isolated. Nobody want to touch the X11 code for more than simple maintenance, no one wants to rewrite major portions or add new features.
We just need Wayland, as you already noted there are very good arguments. A complete new base with modern code and people developing for modern times and hardware just makes sense. Think about it, do you really want to have X11 going forward the next decades? It’s like holding to hard drives and saying its okay, there are no problems, and writing off SSDs.
Think about it, do you really want to have X11 going forward the next decades?
If the alternative is a new system that literally does nothing? Sure!
Want to present a menu for windows? Wayland: “lol, do it yourself”.
Want to position a window? Wayland: “lol, do it yourself”.
Want to remember that a window has a position? Wayland: “lol, do it yourself”.
Want to add a global keyboard shortcut? Wayland: “AAAAHAHAHAHAHAHAHHAHAHAHAHAHAHA!”
X11 may be old and whatever you want, but it works and it’s battle-tested. Wayland can’t even launch a full desktop session in my machine, which is even less than the failure Pulseaudio was back in its day and that’s saying something. And even if it did somehow launch, I probably would not be able to use anything serious like a media player or multiple workspaces on it.
If the alternative is a new system that literally does nothing? Sure!
You should read about Wayland. Doing nothing is absolutely wrong.
X11 may be old and whatever you want, but it works and it’s battle-tested.
It doesn’t work. There are parts of X11 which are broken. And you reply to a reply where I already listed 2 huge points, which are not even the only ones. And you ignore that X11/Xorg code is totally spaghetti, huge and has lot of old code that not everyone understands, because it has ton of workarounds to make it somehow half baked working on modern times. Nobody wants to work on the code, doing more than basic maintenance. And you should think about the future too, not just about yesterday and today on your personal computer. Think bigger. X11 is just not enough anymore going forward, for the next coming decades.
Wayland can’t even launch a full desktop session in my machine, which is even less than the failure Pulseaudio was back in its day and that’s saying something.
Are you on Gnome? Did you install Wayland on top of a running X11 system and did not configure it correctly? X11 doesn’t work on my machine too, because everything is Wayland configured. So whats your point? Off course one is not a 100% replacement. There will be changes, and both are incomplete and are not working 100% perfectly. The point of Wayland is not being 100% compatible with the setup you have for Xorg/X11. There are things like reading from keyboard on any application that is running is a security risk in X11. Wayland prevents that. Which in turn means that some programs (even important ones) won’t work. And they are working on a solution.
I switched to Wayland just end of last year and one of the reasons is that X11 does not handle multiple monitors well, if they have different sizes and refreshrates, especially if you add G-Sync and probably FreeSync on the other monitor. X11 is broken at that front.
I argue that X11 would have hyperactive development, if we did not have Wayland
Wayland was started by the X developers because they were sick and tired of hysterical raisins. Noone else volunteered to take over X, either, wayland devs are thus still stuck with maintaining XWayland themselves. I’m sure that at least a portion of the people shouting “but X just needs some work” at least had a look at the codebase, but then noped out of it – and subsequently stopped whining about the switch to Wayland.
What’s been a bit disappointing is DEs getting on the wayland train so late. A lot of the kinks could have been worked out way earlier if they had given their 2ct of feedback right from the start, instead of waiting 10 years to even start thinking about migrating.
What’s been a bit disappointing is DEs getting on the wayland train so late. A lot of the kinks could have been worked out way earlier if they had given their 2ct of feedback right from the start, instead of waiting 10 years to even start thinking about migrating.
That’s the real issue. And its worse with Gnome, as Gnome doesn’t want support “all of” Wayland and its protocols. That means Wayland will be broken on Gnome, despite Gnome being the most used DE (at the moment). People complain about the problems in Wayland, but not all problems are caused by Wayland itself.
However there were or are two big reasons I can think of why Wayland wasn’t adopted early and for some may never: a) its much harder to be Wayland conform, because the window manager/DE has to do much more work, b) Wayland was just not ready before, as many important aspects were missing (in example some basic protocols, Nvidia) or broken. I don’t blame them. For the record, I am not a Wayland chill, just talking about this, because there are many misconceptions (me included, I’m not perfect) and switched to Wayland just end of last year. Before that Wayland did just not work for me. I even switched from Qtile to KDE, because KDE has probably the best Wayland support (I hate manual window management).
Edit: I just remembered another reason why Wayland wasn’t probably adopted early. Canonical/Ubuntu started a Wayland alternative called Mir (that was before Mir transformed into a Wayland compositor). And devs probably didn’t want set on Wayland or Mir before knowing what will be around in the future.
Wayland kinda is an x.org project in the first place. AFAIK it’s officially organised under freedesktop but the core devs are x.org people.
x.org as in the organisation and/or domain might not be needed any more, but the codebase is still maintained by exactly those Wayland devs for the sake of XWayland. Support for X11 clients isn’t going to go away any time soon. XWayland is also capable of running in rootfull mode and use X window managers, if there’s enough interest to continue the X.org distribution I would expect them to completely rip out the driver stack at some point and switch it over to an off the shelf minimum wayland compositor + XWayland. There’s people who are willing to maintain XWayland for compatibility’s sake, but all that old driver cruft, no way.
Wayland kinda is an x.org project in the first place.
Not really. Wayland is fundamentally different from Xorg. Otherwise we would not need Wayland and create X12. It’s like saying mechanical hard drives are kind of Solid State Drives, just because they allow to do something similar. Even if the developers are the same, does not mean the technology is.
AFAIK it’s officially organised under freedesktop but the core devs are x.org people.
I’m not sure if this is correct. But let’s assume this is correct. Why does it matter? If Wayland was developed by different people than those who maintain Xorg at the moment, would not change the fact that we need Wayland, because it is different and solves issues that cannot be solved with Xorg without rewriting it. And nobody wants to rewrite Xorg or understand the code (other than very basic security maintenance).
And nobody wants to rewrite Xorg or understand the code (other than very basic security maintenance).
That’s precisely the point: All the devs got tired of it and started wayland instead.
X12 might happen at some point when wayland is mature, as in a “let’s create and bless a network-transparent protocol so we might have a chance of getting rid of XWayland in 50 years” kind of move.
arstechnica.com
Hot