Skip Navigation

Posts
16
Comments
396
Joined
3 yr. ago

  • 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.

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

     bash
        
    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.

  • still has me

  • 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.

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

  • 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)

  • What's the point of a read only wiki? I don't get it. Or is this about the source code, not the user data / articles?

  • 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.

  • 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.

  • I am a European who grew up with the German layout. For programming, its a disaster. Even back in 2006ish or so when I learned about AutoHotkey, I started using the US keyboard layout. After some time I switched entirely to the US layout. But recently, just a few years ago I found out there is a hybrid layout which is basically US, but with additional shortcuts to use my German characters (it shows up as this in KDE): German (US)

  • Yeah, I noticed too it does not work well. After some other comments, I tested it on more stuff where I know for a fact it was written by human (myself). And it even gave me over 40% ai probability. It's entirely possible it does that by design, because they have a functionality to obfuscate text for other Ai to detect.

    I need to stop talking and posting about these tools, they are as bad as Ai can get.

  • Yeah, looks like this tool is bullshit too. I have similar results with my own written text too. I will edit my text and stop posting about this tool.

  • @syklemil@discuss.tchncs.de Just for curiosity I checked the text with an Ai detector. Mind you, this is not proof for or against, as I don't take these tools too serious too. They are Ai tools themselves.

    https://www.scribbr.com/ai-detector/ says 0% likely is written by Ai.

    https://stealthwriter.ai/ says 93% is written by Ai. This tool also shows the passages it thinks it is.

    Remember, this is not a proof. But it looks suspicious to me. Test the services with text you know for a fact it is written by human (like yourself). And test is with some text you know for a fact it is output by an Ai (maybe directly ask an Ai for some text). In example the second tool gives me 48% written by Ai, for some text from my own blog post.

  • i find this one sentence for each paragraph to be hard to read as a blog post.

  • Edit: Looks like the tool I linked is total bogus.

    I've copied the text and put it into a tool that tries to find out if its written by an Ai (using an Ai model themselves off course, the irony). Here is one such: https://stealthwriter.ai/

    > About 66% of the content is likely human-written, while 34% appears AI-generated.

    The tool also has the ability trying to obfuscate or rewrite passages that should avoid being detected by such a tool themselves. So it is possible this article was written by an Ai model, a tool to obfuscate was used and them maybe a human edited and rephrased stuff. I can imagine this being part of the publishing process. Complete assumption by me here.

  • 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).

  • In that case I would prefer using variables for the filename:

     bash
        
    file="/dev/nvme0n1"
    text="text I remember"
    strings "${file}" | grep -n "${text}"
    tail -c -100000000000 "${file}" | head -c 50000000000 | strings | grep -n "${text}"
    tail -c -123456789012 "${file}" | head -c 3000 > filerec
    
      

    Even if it's in the terminal, a temporary variable helps a lot. And for a series of commands I would probably end up writing a simple script or Bash function to share.

  • Yes and no. The original design of sudo stands for super user do, and could only run with super user privileges. The run as other users feature was added later, and then they renamed it to substitute user do. I even looked up to get that fact right, and always forget its "substitute" and not "switch", but I also think of sudo as switch user do.^^