Problem is that it’s also an impossible equation to expect customers to keep paying higher prices despite inflation nixing their wages. I really don’t know what they expect to happen. Many people will simply wait until it goes on sale.
I guess, it’s a way to squeeze the day-one rich kids a bit more? But at the same time, you’re cutting down sales when the hype is biggest. And if two people spend $60 each, that’s more money than if only one of them ends up buying your game…
Seems like it’s Apache-2.0, but original sudo is under ISC license, which is more permissive as far as I’m aware. Although Apache-2.0 is very much still considered “permissive”, too.
Yeah, that is one of their attempts to get more independent from the Google money. They would need to be doing more of that, not less.
The problem isn’t the existence of forks, it’s rather how many developers are behind them. Mozilla has around 750 employees, so I’d guess maybe around 500 full-time devs work on Firefox. Tor Browser and such have significantly fewer contributors, who only do this stuff in their free time.
It’s better in some ways for now. All commercial social media platforms start out by being less bad than the competition. That’s how they attract users. When they have enough of a user base for network effects to take hold, that’s when they enshittify.
As I understand, it’s a legal food term in the US. Can’t write it onto your food there, unless you fulfill certain requirements in how it’s produced.
I’ve found that when you cook with lots of fresh veggies, you can mostly just dump them in and it tastes good. Again, you do want a bit of salt, but as everyone else said, you can hand out a salt shaker.
Nothing more boring than a perfect rhyme…
¯\_(ツ)_/¯
renaming symbols, presenting documentation, formatting files,
Yes, these are supported via the Language Server Protocol (LSP). I’ve mostly been using it with the Rust LSP server (rust-analyzer) and well, it typically works, but sometimes you have to tell it to restart the LSP server and stuff (which isn’t a huge ordeal, but don’t expect everything to always work as well as in a full-fledged IDE).
I believe, for formatting, there’s also some non-LSP support.
showing code diagnostics beyond syntax errors (for example code smells or so),
This is supported in principle via LSP, too, but it depends on the specific LSP server, how much info it provides. The Rust compiler gives out relatively much on its own, which is passed on by the LSP server, but you can apparently also configure it to use the linter on save.
have AI integration (explain this, rewrite this, replace this with prompt output, …),
Not out of the box. There’s a way to define “External Tools”, which basically allows you to run commands and pass arguments to them and then use their output. For example, you should be able to define an External Tool, where you can select some text, then press your keyboard shortcut for that tool, so it sends the selected text to that tool and then it takes the command output and inserts it instead of the selected text.
While this is a powerful concept, I don’t know, if you hit limitations at some point.
specific framework integrations (reactjs, django, actix, …),
Nope, except where this might be covered by LSP. But there’s no obvious way to just install additional plugins, for example. You get about thirty built-in plugins and that’s it.
and stuff like expanding macros in C/C++ and Rust?
Well, expanding macros is also possible with the Rust LSP server. Don’t know about other languages.
openSUSE has the best integration of KDE, but I wouldn’t expect to see issues like yours on any distro, really…
It doesn’t, no. If you do it the way I described, you can’t actually get the nozzle at an angle where you could target your balls or legs. It’s not as low down as the beam from the built-in bidets.
On the first few attempts, you’ll probably hit your cheeks more than you’d like, but that just rolls down the cheek until it hangs vertically and then it drops. I’m still seated when I do this, so my legs are more-or-less horizontal.
And well, with a tiny bit of practice, you hit the in-between every time, where the water is stopped pretty effectively and then it drops in the same place where you dropped the nuke.
I can understand the concern, as I had the same when I first tried it, but yeah, after the first few days of learning, I never splooshed the floor or my legs or my balls. I think, I splooshed my cheeks maybe once or twice when I was really sleepy, but that’s about it.
Hmm, personally I’m using a $20 manually operated travel bidet and my butthole feels like freshly showered.
I guess, the advantage of it being manually operated is that I can decide the water pressure by how strongly I squeeze the bottle.
Another advantage is that I have a firm handshake now. 🙃
Personally, I lean forward and to the left, so that my cheeks spread, and then I take the nozzle into my right hand and hold it as if I was scratching my ass.
Afterwards, I fold two sheets of toilet paper and dry myself off at the surface.
Yeah, good point. It also doesn’t update when the content of a file changes. So, in order to detect a change in a directory, you have to walk all the files and sub-directories and the directory itself to get the last-modified timestamp for each of them. Then determine the highest last-modified and compare it to what you measured in a previous run. If they differ, a change happened.
Yeah, I’m building more-or-less an alternative to make. Major difference is that I’m not using shell commands, but rather users will define their build code in Rust …because it’s intended to be a build tool for Rust applications (beyond what cargo does).
Thanks for the comment, though. So far, I haven’t limited inputs to just be files, so I don’t actually assume to have a last-modified timestamp. Rather, my assumption is that I can get some value which changes when the input changes. In the case of a file, that’s the last-modified timestamp, but theoretically, it could also be a hash. But that means I have to store these values to be able to detect a change. Being able to just say that one thing is newer than the other without storing anything, that is pretty cool and might be worth changing my assumption for.
I don’t think, inotify works for me, because I don’t have a continuously running process. My users rather just run some build command and then I go and check, if any input files changed since the last run.
Frankly, I would be surprised, if anything uses groff for displaying --help, unless it shows the man page for that.
The most basic implementation of --help is a manually formatted multi-line string written into the source code, which gets printed as-is.
For dynamic layouting, you do need more logic, but rendering it to groff source code first does not make that easier. For tabbing, you print an appropriate number of \t.
I don’t think that was entirely serious…