

I think the renaming is the right move, in order to not confuse anyone. Congratz “on the upgrade”. And well done asking what the community thinks before doing this. I wasn’t a fan of this, if the name was kept. But this way, it makes perfect sense.
I’m here to stay.


I think the renaming is the right move, in order to not confuse anyone. Congratz “on the upgrade”. And well done asking what the community thinks before doing this. I wasn’t a fan of this, if the name was kept. But this way, it makes perfect sense.


Only if you are dependent on Ai, because you cannot program yourself or don’t want to.


I would just use an old phone, either yours or maybe from your family. A dedicated alarm clock that stays at home and is always charged. It has only one job: alarming. No need to make yourself dependent on a random online website. This can be done offline.


I don’t think so. Because they are different systems with different goals and different needs. If the community was named “Steam OS”, then it would make sense. But this community is not about the operating system, but the device itself.


If no password is needed to do authentication, then any script and any user is able to do whatever they want on your system. Basically every script and application has root access by default. That is something you do not want to have. Even more important in multiuser environments.


Looks like one of the better tutorial / documentation series in a blog I have seen a while for Bash. Most are short and shallow. I think this is NOT an Ai slop. I won’t read it, because I know most of the basic stuff and some advanced stuff too. But from quick look I could recommend this. Well done.


Right, I completely forgot about “Super”. It might even be the more common term.


The “Windows” key is just called “Meta” (Edit: or more commonly “Super”) key in Linux. It’s used for hotkeys, especially stuff that has to do with window management. I also set a simple press on it without other keys, which would open up “krunner” (to search or run apps).


!(r.SendNow || r.DryRun) requires you to read the entire statement and then negate the result. While !r.SendNow && !r.DryRun each part of the statement stands on its own and is negated for themselves. That is how I read. I like the Ai suggestion more, because that is how I would write it myself. What I like about it is, that the negation of is right there with the variable. It gets more important, the more you divide sub-expressions in multiple lines.


This item is currently unavailable in your region
Germany. :-( But why?


The wait for Half-Life 3 is longer.


Pretty cool. I know consoles could do this already and always wondered if it would be possible on Steam Deck too.


Thunderbird. I even use Thunderbird as my RSS reader too.
JSON output support for various commands, making it easier to parse flatpak command output programmatically
Nice. Instead manually parsing the stdout data, now there is a “proper API” to get information.


It’s actually the first time I used to do Ai assisted unit test creation. There were multiple iterations and sometimes it never worked well. And the most important part is, as you say, think through and read every single test case and edit or replace if necessary. Some tests are really stupid, especially stuff that is already encoded in the type system through Rust. I mean you still need a head for revision and know what you want to do.
I still wonder if I should have just gave it the function signature without the inner workings of the function. That’s an approach I want to explore next time. I really enjoyed working with it for the tests, because writing tests is very time consuming. Although I am not much of test guy, so maybe the results aren’t that good anyway.
Edit: In about 250 unit tests (which does not cover all functions sadly) for a cli json based tool, several bugs were found thanks to this approach. I wouldn’t have done it manually.


I like writing code myself, its a process I enjoy. If the LLM write it for me, then I would only do the worse part of the job: debugging. Also for many people let the Ai write code means less understanding. Otherwise you could have written it yourself. However there are things when the Ai is helpful, especially for writing tests in a restrictive language such as Rust. People forget that writing the code is one part of the job, the other is to depend on it, debug and build other stuff on top.
You shouldn’t feel any lag at all, even on Bluetooth if its working properly. Maybe there are other things going on that adds to the overall lag. You should test another controller that is not using the xpadneo driver.
I quickly searched the web: https://superuser.com/questions/1653283/how-to-resolve-the-input-lag-when-using-xbox-series-xs-with-bluetooth-on-linux and the person solved the issue by updating controller firmware, the Linux Kernel and the xpadneo driver itself. But its an old post, so maybe not what you need to do. I don’t know what distribution and version you have and if you can update at all.
I used the Xbox 360 game controller for years on PC, then switched to Xbox One, then Xbox One S and then to the Xbox Series S controller. So we speak about decades at this point. I played extensively Steam games and emulation for all kinds of systems (where input latency is extremely important in some games). At the same time I also have used extensively a wired classic SNES like shaped controller that is wired connected and recently I replaced my Xbox controller with a 8bitdo wireless controller.
So you see there is some experience in using and in comparison. Latency was never an issue and I never felt it. But the common theme here is, I never used Bluetooth and always use the (even if its proprietary) dongle by Microsoft for connection. That’s because it should provide superior connection stability and better input latency. I always had issues with Bluetooth before (I mean with any other kind of hardware connection) and always hated it and avoid it.
Having said this, Bluetooth can be good. In example the Playstation consoles and their controller are using Bluetooth and its not an issue there. But you have to make sure that the driver and the Bluetooth dongle (or chip) is compatible and working fine, in combination with the controller. If you notice a difference between wired and wireless, then its a sign that the wireless connection doesn’t work properly for your setup. I think my best advice is to buy the proprietary dongle from Microsoft (as I hate doing this, but its the best for Xbox controllers). You will also need to change the driver from xpadneo to xone.
However I switched recently to a different controller because I experienced a few issues with the driver. Because the driver wasn’t updated for a while and it broke with a new Linux Kernel update on my Archlinux based system.
This escalated quickly.