

Yeah, I might block a contributor on sight, if they post something like that.


Yeah, I might block a contributor on sight, if they post something like that.


In case, you’re not aware, you can also email the dev. You can code up your commits as normal and then use e.g. git format-patch -3 to put the last 3 commits patch files. You can then attach those files to an e-mail and the dev can apply those patches with git am.
It takes a bit of playing around, but it’s actually really easy.
The Linux kernel, one of the most complex projects on the planet, develops like this.


I think, you could open the same file multiple times and then just skip ahead by some number of bytes before you start reading.
But yeah, no idea if this would actually be efficient. The bottleneck is likely still the hard drive and trying to fit multiple sections of the file into RAM might end up being worse than reading linearly…


Yeah, and the worst part is that submitting the PR is trivial. You just offload the reviewing work onto the maintainer and then feed the review comments back into the AI. Effectively, you’re making the maintainer talk to the AI, by going through you as a middleman, a.k.a. completely wasting their time.
I don’t feel like these positions are at odds with one another, unless you become active in reducing the number of humans, of course.
Like, you can uplift and protect people by stopping them from killing their environment, because you recognize that people are an invasive species that will do that.
If you’ve got access to a microwave, I’ve found rice dishes quite convenient, like for example a lentil curry. They generally re-heat without tasting worse and the rice traps the moisture, so even if your container isn’t 100% sealed, you’re unlikely to get mess everywhere.
(Though I’d still recommend getting a properly sealed container. Personally, I also transport my food in a separate cloth bag, so that if it should ever leak, I can just wash that bag.)


Yeah, I always plead for as much as possible to be automated offline. Ideally, I’d like the CI/CD job to trigger just one command, which is what you’d trigger offline as well.
In practice, that doesn’t always work out. Because the runners aren’t insanely beefy, you need to split up your tasks into multiple jobs, so that they can be put onto multiple runners.
And that means you need to trigger multiple partial commands and need additional logic in the CI/CD to download any previous artifacts and upload the results.
It also means you can restart intermediate jobs.
But yeah, I do often wonder whether that’s really worth the added complexity…
I always thought openSUSE’s package manager zypper has quite a few neat ideas:
zypper install→ zypper in, update → up, remove → rm.fish git texlivezypper repos gives you a list of your repositories, numberered 1, 2, 3 etc., and then if you want to remove a repo, you can run zypper removerepo 3.zypper search, it prints the results in a nicely formatted table.Documentation: https://doc.opensuse.org/documentation/tumbleweed/zypper/


Yeah, same. As they discuss in that issue I linked, it seems like in this partocular scenario, it gets stuck thinking it should remove a UnifiedPush distributor, but there is none to remove, so it keeps trying again and again, each time sending the same notification. But yeah, just my high-level understanding of the initial analysis…


What I find tricky, is that you’re always describing a work-in-progress. I also wanted it to be useful as soon as possible, so I started building the actual core logic first and documented that part of it.
But to actually use it, you need several steps before, which need to be documented, but preferably automated or ideally eliminated.
So, you kind of don’t want to invest time documenting that, because you know it’ll change a lot still.
And just as well, any quirks you document, it’s always like, okay, but what if I fixed this quirk instead?
Obviously, one has to strike some kind of balance. Things will never be 100% perfect or final. And I am most definitely lying to myself, when I figure that fixing it won’t take much longer than documenting it. But yeah, it’s just a constant struggle to find that balance…


It’s likely a bug: https://gitlab.com/relan/fennecbuild/-/work_items?show=eyJpaWQiOiIxNzYiLCJmdWxsX3BhdGgiOiJyZWxhbi9mZW5uZWNidWlsZCIsImlkIjoxODY5NDI0MzF9
Personally, I’m waiting to see what the devs say, but if it gets on your nerves, you can hide the notification in the Android settings.
I’m just not sure, if it is maybe needed again at a later point, which is why I’m holding off.


Perhaps also worth adding that here in Europe, lots of soy is now actually being grown regionally, as it can withstand the higher temperatures we now have from climate change…


Am vegan. Certainly don’t eat nearly as much as @Carnelian@lemmy.world. But it is a pretty flexible food. Like, I can get soy yoghurt that tastes like the real deal. I can get TVP, which is chewy like a steak. I just had fucking noodles out of 85% soy + 15% chickpeas, and they actually tasted good. And of course, the all-time classic: Soy sauce.
I don’t stan for soy nearly as much as many others, because other legumes and nuts are awesome, too, but you just can’t deny that soy covers a lot of bases quite well.
Yeah, this is one of those issues that I feel separates the seniors from the, uh, less experienced seniors. (Let’s be real, as a junior, you know jackshit about this.)
Knowing when to use an ORM, when to use SQL vs. NoSQL, all of that is stuff you basically only learn through experience. And experience means building multiple larger applications with different database technologies, bringing them into production and seeing them evolve over time.
It takes multiple years to do that for one application, so you need a decade or more experience to be able to have somewhat of an opinion.
And of course, it is all too easy to never explore outside of your pond, to always have similar problems to solve, where an SQL database does the job well enough, so a decade of experience is not a guarantee of anything either…
It’s key-based client authentication. Just open your SSH key’s .pub file in Microsoft Publisher, then export to PDF.


I do agree, yeah, although I can certainly also understand LISP fans being annoyed that someone created a custom DSL for something that is adequately solved by the LISPs. I’m also certainly not enamored with the Nix syntax myself, but do find it easier to parse than a million parentheses.
But yeah, ultimately the complexity of Nix and Guix isn’t in the particular symbols you type out. The complexity comes from them being expression-based (which does make sense for the use-case, but isn’t as familiar as e.g. imperative languages), as well as just having to learn tons of modules for the different things you want to configure…


Wikipedia seems to do a decent enough job defining it:
Authoritarianism is a political system characterized by the rejection of political plurality, the use of strong central power to preserve the political status quo, and reductions in democracy, separation of powers, civil liberties, and the rule of law.
But basically, my point is:
Basically, my opinion is that politics is a constant work in progress, no matter the political system.
I hear, it helps with saving up for treatment by not paying for nudes. 🥴