Personally, I’m at the point where I try to only use community-developed software. I’ve seen it too often that even projects which are nominally open-source start becoming cunts…

Android, Chromium.

The problem is that:

1. Google puts in more development power than anyone else. Any forks we’ve seen so far are only really soft forks, as in they only apply a few patches on top of what Google puts out, rather than taking the project in a new direction, because you’d be behind pretty quickly.
2. These projects establish platforms that have shitty decisions baked in. For example, the Android dev tooling has Google ads/tracking as one of the built-in UI components, which is why even if you patch the OS, the apps will still be shitty. To actually change this stuff, you’d need a majority of users to switch to your fork and stay there for a few years.
3. Partially, it’s only financially viable for Google to develop these projects, because they have those Android ads or benefit from a web with less tracking protection. This makes it extremely unlikely for any other organization to be able to splurge a similar amount of money, which brings us back to a fork just being unlikely.

And so long as a fork is unlikely, Google can do shitfuckery quite similar to proprietary projects.

It just fills in the gaps with a whole lot of imagination, not too different from how a human would. Unless it has access to a more detailed picture or contextual information, it cannot extract more information than was actually captured.

I don’t know about best, but makertube.net fits.

Puppy Linux is what I usually see recommended for such low specs. It’s also available with a Debian base.

https://puppylinux-woof-ce.github.io/

I still don’t get why the backslash is on keyboards to begin with. I don’t think I’ve ever seen anyone write a slash backward with a pen. And even if folks do, you could’ve had only one slash anyways. Like, people are going to understand what it means, whether it’s / or \.

I guess, it not being used for much else, does at least make it useful for escaping stuff and for Windows to use as path separator.

You might be seeing posts from the 196 community, which recently split up (personally, I had the old ones blocked and then due to it splitting, the new 196 community showed up in my feed).

The 196 community is very much about quantity-over-quality, when it comes to posts, and as such reposts do happen often, too.
No shade on that, but it’s also not for everyone, so yeah, you might want to just block those communities.

It’s only really Windows that doesn’t use LF these days. All the Unix-based ones (Linux, BSD, macOS, iOS, Android etc.) use LF…

Alternatively, the less proper tool: Record your screen, cropped to the SVG.

GIF, MP4 and such, they’re just a bunch of pixel grids. They don’t care where those pixels came from.

I was kind of thinking that yesterday when looking at a Rust library. Rust is competent with line numbers, so you don’t really have an incentive for splitting files from that angle, but sometimes, folks just seem to keep adding to their files ad infinitum.

Well, specifically that library has a few files with more than 1k lines. And I hope this one’s the largest at 4k lines: https://docs.rs/git2/latest/src/git2/repo.rs.html

What also needs to be said, is that this library is actually maintained by the Rust language team. Really makes me want to open an issue to tell them that Rust has a pretty cool module system. 🙃

Damn, this guy looks like he’s about to sing an 80s power ballad.

Apparently, a dev on the customer side estimated that he’d need two weeks to implement the whole project (which thankfully our customer representative also laughed at).

Man, I’m currently in a project which started out with 2 major goals. Pretty early on, we got told that one of the goals is practically impossible, so we decided to ignore that. And we realized the other goal needs to be simplified significantly to be achievable in the slightest, although we still weren’t sure, if it violates the laws of physics.

Now we’re a year into development, we’ve only figured out that it might be physically possible in certain situations. And yesterday, we talked to a guy with domain knowledge, who told us like ten different bigger challenges we’d still have to solve.

Found this channel recently about electric guitars: https://vod.newellijay.tv/c/workingclassmusic/videos

I have no specific interest about electric guitars, but their videos are fun. Although I’ve so far mainly watched the ones where they have two hosts on. Those with one host seemed a bit too product-review-y for my product-uninterested ass. 🙃

The browser has an internal model for representing the HTML document, called the Document Object Model (DOM). This DOM happens to be tree-shaped, because HTML is tree-shaped. And certain logic in a browser gets applied to subtrees, like e.g. most CSS rules.

Sometimes, however, you want a subtree to not get affected by what’s going on in the main tree, for example when including an SVG into that tree, or if you’re offering JavaScript library with a pre-built component.
And yeah, that is what the Shadow DOM does. It also shields the rest of the DOM from what you’re doing inside the Shadow DOM. And there’s certain mechanisms to selectively allow interaction across the shadow boundary, e.g. when providing a pre-built component, you might still want the user to be able to style parts of it.

It is very much real: https://developer.mozilla.org/en-US/docs/Glossary/Shadow_tree

Yeah, direct link: https://f-droid.org/en/packages/org.fossify.gallery/

I looked through F-Droid a while back and liked this one the best.

Both of those are sweet and fruit…?

I believe, you just launch a .exe file and it should be the default application that gets started…

Yeah, Python requires a “runtime” program, which interprets the Python code and then translates it into native machine code to actually execute it. Because Rust is compiled directly to native machine code by the developer, you don’t need a runtime program on your PC to run Rust programs.

This is also one of the biggest reasons why Rust can be used for kernel development. You cannot rely on a runtime program for developing a kernel, since launching a program requires a kernel to already be up and running.