I was in the same camp when I had to use Python on the job, but when Scala introduced (optional) significant whitespace, I actually grew to like it a lot. I think the important difference to Python is, that with a good type system and compile time checks a whitespace error is basically always a compile time error in Scala.
That's also for me it's worse in a configuration language (unless you have a schema file for validation, which is rarely the case sadly)
This basically amounts to a key/interaction logger in the IDE. I'd suspect this would prevent many people contributing to projects using something like that, at least I wouldn't install such a plug-in.
What exactly would you checksum? All intermediate states that weren't committed, and all test run parameters and outputs? If so, how would you use that to detect an LLM? The current agentic LLM tools also do several edits and run tests for the thing they're writing, then edit more until their tests work.
So the presence of test runs and intermediate states isn't really indicative of a human writing code and I'm skeptical that distinguishing between steps a human would do and steps an LLM would do is any easier or quicker than distinguishing based on the end result.
Even counting all who voted for them, as the voter turnout was 64%. I'm not sure how much of the population 100% would be with that voter registration system the US has (is 100% all registered voters or all that could in theory register), but even if 100% was all the population, it would only be around 35% MAGA voters
No one is planning to loosen any current rules, this is about a new law, that would ban names like soy milk.
At least in Germany, even without the new ban, it was not allowed to call anything but cow milk simply "milk" without any prefix, and what you can add to cow milk is already regulated (https://de.wikipedia.org/wiki/Milch-_und_Fettgesetz). Is it different where you live and currently milk is often watered down?
We have three cats, and the idiot one is also the plotting one (just unsuccessful).
She regularly tries to get into places she isn't allowed, like the stairway to the other flats, but at the same time took two years to understand how to push open an ajar door...
It runs as part of steam, so you would need to add the program you want to use to steam as an external program and start it through steam. Steam Input then runs as a translation layer around the other program. At least that's how it works on the Steamdeck.
A lot of Dockerfiles start with installing dependencies via the base image's package manager, without specifying exact versions (which isn't always possible, as most distros don't keep all history of all packages in their repos). So all your dependencies may have different versions, when you build again.
The barrier repo is basically dead, input-leap is a fork from two of the previous maintainers and still actively developed: https://github.com/input-leap/input-leap/issues/1414
So unless you're using an apt based distro (which don't seem to have it packaged yet), I'd recommend using that instead.
Als die Grünen hier im Dorf Plakate für die Kommunalwahl aufgehängt haben, war das erste Plakat schon zerstört, bevor sie mit ihrer Runde fertig waren, also in unter einer Stunde :(
The last time I tried WFInfo, it wasn't working for me on Windows either, so maybe not a Linux issue. But if you get any of the Linux alternatives running, I'd be interested too.
I thought the default interactive shell is still bash on Ubuntu, dash is only used for /bin/sh, isn't it? At least bash is also installed by default, as there are so many scripts that wouldn't run otherwise
I switched to zsh at a time where completion for commands parameters except file paths in bash wasn't really a thing, you could add some with a script, but they didn't work well. I'm sure the situation has improved by now, but someone told me recently, there are still no descriptions for the completions. I find it very helpful and it saves me opening a man page a lot of times. For example, typing grep -<Tab> gives me this:
And now I'm so used to many little features (mostly around the syntax) that wouldn't be a reason to switch on their own, that I find bash cumbersome to use.
I'm not sure if supports encryption though, which is probably where a dedicated server would be useful.
Well, ideally you encrypt your data before transferring, so the provider never sees your data. I'm using a storagebox to backup btrfs incremental snapshots (using btrbk) and just AES encrypt them locally before sending them over, so I don't care if the storagebox itself is encrypted.
I was in the same camp when I had to use Python on the job, but when Scala introduced (optional) significant whitespace, I actually grew to like it a lot. I think the important difference to Python is, that with a good type system and compile time checks a whitespace error is basically always a compile time error in Scala. That's also for me it's worse in a configuration language (unless you have a schema file for validation, which is rarely the case sadly)