thingsiplay

joined 2 years ago
[–] thingsiplay@beehaw.org 2 points 4 hours ago

I think that I explained it. Here a shorter list:

  • these statistics are only about Steam games, not 90% of Windows games
  • 90% of games does not equal to 90% players / users

Most players don't care how many games from the Steam catalog are playable, if their favorite game is not. That's the point. And the article did a bad job of making it clear.

[–] thingsiplay@beehaw.org 2 points 5 hours ago

I agree that for you it doesn’t make sense

What do you mean it doesn't make sense for me??? What exactly doesn't make sense to me in your opinion. I am stating facts and we should not hide them when recommending or showing statistics. It is disingenuous titles like these that will let people try once and forget forever.

Everyone should decide themselves it the move / change makes sense. But we need to provide the facts and information. This article fails to do so.

[–] thingsiplay@beehaw.org 23 points 10 hours ago (10 children)

The only problem with such statistics are, that a) these are Steam games, which do not include all Windows games such as Fortnite, and b) most AAA multiplayer games that are very popular are not playable on Linux. So 90% of games does not equate to 90% of players. Because for most players in example it does not matter the 20% games on Steam with 1 or 2 players at most (just figuratively speaking). This article leans towards Steam statistics and ignores Fortnite, League of Legends, Roblox, Valorant and even on Steam itself GTA Online, PUBG, Call of Duty games (online part), Battlefield games (online part) and so on.

I am a die hard Linux user and gamer since 2008, but I am not someone pretending that 90% of Steam games playable on Linux is as impressive as the the statistics sound. It is important to tell the entire truth, so people switch based on correct and full information and not on a wishful thinking.

[–] thingsiplay@beehaw.org 17 points 1 day ago (2 children)

You can set Vim as your pager. If you are on Neovim, its very easy, just set this variable:

export PAGER='nvim +Man!'
export MANPAGER="${PAGER}"

Then try man grep. These variables could be set in your .bashrc in example. If you use the "original" Vim, it's a bit more complicated to setup. I did that before too, so it's definitely doable.

[–] thingsiplay@beehaw.org 1 points 2 days ago

At least from test coverage point of view, I think they aim to have the same tests to pass as the original tools. Not all pass right now, so incompatibility is expected at some point, somewhere.

[–] thingsiplay@beehaw.org 5 points 2 days ago

I just released my first cross compiling app on Linux and Windows, using Podman. This is so great.

[–] thingsiplay@beehaw.org 2 points 2 days ago

Oh yes, that tiling issue is solved (if you had the same as me, but you probably had). I had huge tiling issues in the beginning of the transition phase from its codebase KDE 5 to 6 and on top of it on Wayland. It's noteworthy that Kwin developers specifically addressed issues with Krohnkite, and even noted that in the update notes. I am using it quite some time now (a year or longer maybe) and it works basically correctly like any other standalone tiler.

Just my personal experience on a single monitor, as I am single. (yes I wrote that, just to make a joke, but I really use one monitor only)

[–] thingsiplay@beehaw.org 2 points 3 days ago (2 children)

As a user of Krohnkite, I am interested into the problem of Layouts breaking easily. What do you mean by that? As for the multi monitor, well I am single monitor user, so never cared about this issue.

[–] thingsiplay@beehaw.org 5 points 3 days ago* (last edited 3 days ago)

Relevant post: https://beehaw.org/post/22870135

Tip. You can use the cross-post function of Lemmy. This will automatically link the original post and also all posts linking to the same source on the web are linked together in a list. So we can see how often it was "shared" and open their post directly to see others replies.

[–] thingsiplay@beehaw.org 2 points 5 days ago

I understand the reason why you do it this way. Hardcoded and be explicit has its advantage (but also disadvantage). I was just saying that I personally prefer using variables in a case like this. Especially when sharing, because the user needs to edit a single place only. And for variables, it has the advantage being a bit more flexible and easier to read and change for many commands. But that's from someone who loves writing aliases, scripts and little programs. It's just a different mindset and none way is wrong or correct. But probably not worth it complicating stuff for one off commands.

And for the cat thing, I am not that concerned about it and just took the last example in your post (because it seemed to the most troublesome). I personally avoid cat when I think about it, but won't go out of my way to hunt it down. I only do so, if performance is in any way critical issue (like in a loop).

view more: next ›