Yeah, computationally intensive stuff is going to be slow when implemented in Python. You will find lots of data science libraries for Python that do computationally intensive stuff, but they’re then generally implemented in C/C++ or Rust, with only a thin API layer written in Python.

Expecting the runtime/browser to ship a native implementation of virtually everything you might want to do in a turing-complete language, is also really not sustainable, though.

Kind of wild that they managed to portray this loop in just 4 panels…

“Oven is going to be a grind, especially the first nine months or so. If work-life balance means a lot of time spent not working, it’s probably not a good fit.”

Oh man, someone here recently shared a blog post on startup culture in software companies, which likened software to an oven, where you’d add a specific button for a customer and that fucks up your whole architecture for years to come etc…

For just a moment, I thought this was a direct quote from that blog post.

I also like how they claim it’s completely different to KRunner and then, save for OCR and whatever “circle to search” is, these are all features in KRunner.

More of a general tip: https://reuse.software/ can help to get this stuff right.

Pretty sure, it won’t be able to help with your use-case of copy-pasting code snippets, though (it’s not at all trivial to know which parts you copy-pasted), but it gives you a structure to work with and can automatically annotate new source files.

Very good article for folks who’ve had to teach juniors/trainees Git before.

This is, to my mind, one of the greatest advantages of git (and, by-the-by, also automated testing): the added security that being able to restore to an earlier state whenever you need to allows you to take more risks and try more things when building software.

Yeah, I always tell them it’s like checkpoints or like a save in a game.

But this also ties into the needing-a-teacher aspect to properly learn Git: Due to the nature of what Git accomplishes, it has a lot of complex failure modes. And at the start, you need a teacher to get you through those.

The worst-case is if they start dreading merges, because they can’t past them and then they try to merge less often, which makes the conflicts so much harder to deal with.
Or if they can’t get past merge conflicts and stop seeing the point in small Git commits and in good commit messages. That also makes merge conflicts so much worse.

That’s kind of my motivation to be good at Git. I need to be able to tell juniors, that if they’ve created a commit, then we can unfuck the repo no matter what they might do wrong.

You might be thinking of OnlyOffice…?

Looks like a typo: !datahoarder@selfhosted.forum

df only shows partitions, whereas du adds up the file sizes in the directory you specify.

So, in particular, if you want to find out what’s taking up so much space, you can repeatedly run du -sh * and cd into the largest directory.

Hmm, don’t think you should need to compile it yourself? They offer downloads for Windows and macOS, and on Linux, the normal Firefox from the distro sources generally already has this compile flag enabled, as far as I know.

I mean, I actually never had a need for unsigned extensions, so never tried it myself, and obviously I wouldn’t know, if every single distro does it the same.

As for wanting to contribute to the statistics, I do understand that desire. But I believe, for the most part, it’s the user agent that counts. I doubt, they would set that to something else in the unbranded builds…

It is possible on Firefox Stable, by using an unbranded build.

Yeah, the naming seems to be all over the place.

From what I found online, what you ate would be referred to as “chicory greens”, if we’re being specific.

And the white ones, Wikipedia primarily calls “Belgian endive”, but then also:

Belgian endive is known in Dutch as witloof or witlof (“white leaf”), indivia in Italy, endivias in Spain, chicory in the UK, as witlof in Australia, endive in France and Canada, and chicon in parts of northern France, in Wallonia and (in French) in Luxembourg.

https://en.wikipedia.org/wiki/Chicory#Leaf_chicory

Interesting, I only know chicory as these bad boys:

Better than the original. As in, it’s a faithful reimplementation with quality of life improvements, like higher resolution, support for modern operating systems, and most loading times eliminated.

I believe, there’s still tiny differences to how the original behaved in certain situations, which is why they don’t call it “1.0” yet, but you’re not going to notice while playing.

https://en.wikipedia.org/wiki/VK_(service)

(“Russian Facebook” is pretty accurate.)

Man, you seem to get much nicer vegan cheese. In the shops here, it’s just slices of hardened fat with flavoring and no protein.

Some brands do make it taste like real Gouda, but it still feels so very pointless to throw just some fat onto your bread. Might as well eat the bread by itself or, you know, with real food like baked beans or dal or such.

What a video, man.

Argumentation: In specific cases, you can achieve better performance by manually ordering, but 99% of devs will never know that might be a possibility.

Conclusion: Those 99% should somehow know to opt into automatic re-ordering, rather than those who know what they’re doing having to opt out.

From what I understand, on Debian and therefore presumably also Devuan, the system-wide default shell is dash. So, sh symlinks to dash.

But dash is virtually unusable for interactive use, so they configure the terminal emulator to launch bash on start-up.

In effect, scripts get executed with dash by default, but commands you type into a terminal get run by bash.

Oh, huh, I saw the release announcement for Fedora 44 explicitly mention Plasma 6.6, so I figured it was tied to the release. 🫠