I believe, the problem is mainly white bread, which is what people typically have in mind for feeding ducks.
As opposed to wholegrain, it only retains the endosperm, which is mostly just carbohydrates without many nutrients:
I think, the lack of fiber is also particularly problematic. At least, I’ve heard that it gives them diarrhea, which probably means their guts don’t have time to extract the few remaining nutrients.
A few years ago, I set up a home-server with music and some pictures on there, and recently I noticed that my storage disk was getting full. Then I saw that the disk only had 16 GB and wondered, where the hell I got that small of a disk from.
So, I go to plug in a bigger disk and can’t even find the original disk at first. Turns out my whole storage capacity was one of these bad boys:
And yeah, I’ve got about 1800 songs, clocking in at 5.8 GB, so even that tiny storage would easily be enough for a much larger collection.
And I do also have them replicated on my phone, for listening on the go. (Don’t even need an SD card in my case.)
Presumably, that ampersand needs to be replaced with &…
I would argue that a substantial reason for their popularity is also just that devs have fun when developing them.
With most other genres, you’ve seen the story a gazillion times, you’ve done each quest a thousand times etc… It just gets boring to test the game and it becomes really difficult to gauge whether it still is fun to someone who isn’t tired of it.
Meanwhile with roguelikes, the random generation means that each run is fresh and interesting. And if you’re not having fun on your trillionth run, that’s a real indicator that something needs to be added or improved.
Legend has it that he does have his own store already, so I’m really not sure why he’s saying anything at all.
I find that it’s mainly frustrating to those learning German at an advanced level, since using a wrong article immediately exposes you as a non-native speaker. Because yeah, as the others said, it hardly ever happens that native speakers use a wrong article…
Their primary purpose certainly isn’t the same, but with JavaScript being used to implement text editors, it’s in a playing field where many would argue that Rust is better suited.
Well, and Rust can play in JavaScript’s playing field, too: You can implement webpages in HTML+CSS+Rust by going through WebAssembly.
Man, at $DAYJOB, if we open-source something, they tell us to check for checked-in passwords and whatnot, and force us to throw away the commit history, which always feels stupid when we’ve known upfront that we’re going to open-source it and so kept things clean from the start.
But then, yeah, you see a post like that and just think that it really wouldn’t have been too difficult to search for swear words before publishing.
I mean, I also don’t really care, since it’s code rather than an official communication channel, but I can understand why management might care.
The description in the ticket isn’t too bad:
allows users to make a window disappear and keep only its title bar visible.
It really just hides the window contents. In effect, it is similar to minimizing a window, except that it doesn’t spring into your panel and rather stays in place as just the window title bar without the contents.
It is a niche feature, if you couldn’t tell. But it isn’t some KDE specialty feature; various other desktops and window managers also support it. I think, it was more popular in the early days of graphical user interfaces, when we were still working out, how we want to do panels and such.
And conversely, I do think it makes more sense as a feature on big screens like you can have today, where your panel might be quite a bit away.
Don’t think, window shading will make a big comeback just yet, but yeah, probably enough existing users that use it, so that it would be cool to support that workflow.
There’s a store in the next town, which has only organic foods. Rather expensive to shop there, but I still go there more often than I need to, just because everyone’s friendly and relaxed.
Yeah, if I ever catch a calm hour in the store, I’ll actually look through the aisles and check out products I wouldn’t normally buy. If the store is busy, I grab the usual and flee as quickly as possible.
I thought about creating something like that and the major problem that I see is that lots of meme templates do have copyright and the font that’s typically used for memes, Impact, isn’t free either. Well, and it isn’t done by merely developing a software and offering it for download. You would need to host the meme templates or some editor webpage, which is a whole 'nother skillset.
If we say that users bring their own meme template, and it can be a free font that looks similar to Impact, and it’s not to be hosted as a webpage, then it would be quite doable.
You would “just” need to call the ImageMagick library with the right parameters. Still not trivial, but the path to get there is fairly straightforward. I could imagine that something like that already exists as an open-source project…
It’s mostly about ease of use. You don’t really want to spend more than a few minutes on a silly meme. As such, having a database with meme templates, the right kind of font and easy text placement, can make the difference, whether you’ll bother creating a meme or not…
I mean, modern package managers generally now come with lock files, which effectively auto-pin your dependencies, until you trigger a dependency update.
And while it isn’t bullet-proof, it does result in you effectively having a dependency cooldown most of the time. You’re only vulnerable, if you trigger the dependency update while the compromised dependency release is public.
Obviously, this can be bad enough, but it does also mean that an ecosystem with lock files is far less attractive to target with a supply-chain attack, since far fewer hosts will get compromised on average.
One time, I had to request firewall access for a machine we were deploying to, and they had an Excel sheet to fill in your request. Not great, I figured, but whatever.
Then I asked who to send the Excel file to and they told me to open a pull request against a Git repo.
And then, with full pride, the guy tells me that they have an Ansible script, which reads the Excel files during deployment and rolls out the firewall rules as specified.
In effect, this meant:
Yeah, the whole time I was thinking, please just let me edit an Ansible inventory file instead. I get that they have non-technical users, but believe it or not, it does not actually make it simpler, if you expose the same technical fields in a spreadsheet and then still use a pull request workflow and everything…
They have breaking changes in their minor versions…
Personally, I find that (complex) software implemented in Python tends to be so unreliable that I typically don’t want to use it after all, but I only find that out after wasting a bunch of time learning the software.
It’s just frustrating, especially if I come back to the software every so often, naively thinking that it’s been a few versions, so maybe they’ve fixed it. It’s always just different bugs, which still end up being too frustrating to use the software.
To give an example, I like to compose music using Lilypond, which is more-or-less a programming language to create sheet music. And there is a program that’s supposed to give you a well-integrated workflow for that (i.e. an IDE), called Frescobaldi.
The first time I tried it, playback of the composed music wouldn’t work.
The second time, I couldn’t click on notes to jump to the respective code snippet.
And I tried it again a few weeks ago and it just crashed immediately with an obscure error message.
Instead, I’ve slapped together a script, which just opens the sheet music in my PDF viewer, the code in my normal editor and then uses a CLI tools to generate and playback the sheet music. And while it’s definitely not perfect, it has been working more reliably for me than Frescobaldi ever has.
Bash fucks me up so much, too. You just put the parentheses there to say that something is a function, not for actually declaring the parameters that can be passed in…
Yeah, we just have two ear canals. Stereo is basically all your brain will get.
The thing to me is always that, yeah, you need a huge commit for a breaking change in an internal library inside a monorepo, but you will still need to do the same work in a polyrepo eventually, too.
Especially since “eventually” really means “ASAP” here. Without going through the breaking change, you can’t benefit from non-breaking changes either and the complexity of your codebase increases the longer you defer the upgrade, because different parts of your application have different behavior then. So, even in a polyrepo, you ideally upgrade all library consumers right away, like you’re forced to in a monorepo.