Yeah, I can understand the frustration when an external decision forces you to disappoint some of your users, but ultimately you have to pick your battles. When neither the Python nor Rust ecosystem thinks those platforms are worth supporting, it’s probably not either worth it for you to worry…

https://infosec.exchange/@0xabad1dea/116335209525412306

It’s Apple’s programming language, kind of intended as a successor to Objective-C.

From what I hear, it’s actually decently designed and has quite a few similarities to Rust. Still not sure, how great it is outside of the Apple ecosystem…

My instance went down, so I’m way too late to make this joke, but anyways:

We’re not cantankerous, just a little …crabby. 🙃

Considering their policy for the majority of their existence has been that open-source is cancer, it might as well be viewed like that. Just buy the central open-source exchange platform and slowly make it worse to hurt all of open-source.

It’s key-based client authentication. Just open your SSH key’s .pub file in Microsoft Publisher, then export to PDF.

In my experience, the biggest problem is that maintainable code necessarily requires extending/adapting existing structures rather than just slapping a feature onto the side.

And if we’re not just talking boilerplate, then this necessarily requires understanding the existing logic, which problems it solves, and how you can mold it to continue to solve those problems, while also solving the new problem.

For that, you can’t just review the code afterwards. You have to do the understanding yourself.
And once you have a clear understanding, it’s likely that the actual code change is rather trivial. At least more trivial than trying to convey your precise understanding to an LLM/intern/etc…

Yeah, IPv4 addresses use four bytes. Those four bytes are represented as four decimal numbers, separated by dots. And a byte can only represent the decimal values 0–255.

Everything I implement at work is open source because I don’t want to wait for a purchase approval.

Just to say, though, I feel like 99% of the software we deploy is open-source for that exact reason. Projects generally start out small, where you try to evaluate some concept. You’re not gonna spend months to go through the purchase process of some proprietary tool, if you can help it…

Well, this version is going to be in the Ubuntu repos eventually, but might take a while. Ubuntu 26.04 is already in feature-freeze, so it’ll be in 26.10 at the earliest (or 28.04, if you follow the LTS releases).

I guess, it would probably also show up in the “backports” repo before that, if you enable that, but might be easiest to use the Flatpak or AppImage instead…

Ah yeah, that seems to be it. When I drop my keys in the right place, it goes into suspend. If I lift them back off afterwards, it wakes back up.

Neat. 🙃

Today, I noticed that my glasses case sticks to my work laptop like a magnet.
I played around with it for a few seconds, then the thought struck me, that it might be my glasses case that’s magnetic, and I might be fucking up the electronics or the HDD or something by holding it close to my laptop. Pulled away real quick then. 😅

I did try with my keys later, and well, turns out that it’s my work laptop that’s magnetic, so I guess, I wasn’t fucking anything up after all…

Feels like one of those jokes that explicitly shouldn’t go into programmerhumor. A programmer that doesn’t interact with Linux, that’s something to tell the world about…

Obsidian is not open-source…

I just saw this on F-Droid, will need to test it, but sounds like it could be really good: https://f-droid.org/packages/lu.knaff.alain.saf_sftp

I’m hoping, it works like mounting or FUSE on proper Linux, where you can just use normal applications to transparently access network files. Then you’d be able to use any old file manager app to actually work with the files…

You probably just misread, but just to note that SFTP is different from SMB. They’re similar in purpose, but basically competing protocols…

Yeah, this should be equivalent to interpolation search, which has an average performance of O(log(log(n))).

It helps that the months are separately indexed, so instead of a search on 365 input elements, you can do two searches with much lower input size, i.e. 12 and 31.

But yeah, you’re still in the larger O(log(log(n))) category with that.

Well, I assume they had other concerns, too. For example, it adds a bunch of complexity for reformatting a JSON from single-line to pretty-print, if comments can appear in there. I’m certainly not saying that I’m always best friends with the decision to remove comments, just that I can somewhat understand it.

I can understand the sentiment and would 100% agree for programming languages.
But personally I actually like that it encourages a flat structure, because you do not want to be yakshaving the structure of your config file. Too much nesting means you will sooner or later run into configuration keys being nested under the wrong category, because your project context changed over time.

And well, as I’ve argued in a few other comments already, I think non-techie users have a disproportionally simpler time when no nesting is used. They understand the concept of a heading and then just adding a line underneath the appropriate heading is really intuitive.
You can just tell them to add the line certificate="/tmp/cert.crt" under [network.tls] and they will find a line in their config file which actually reads [network.tls] and they can just paste that line as-is.

With nesting, they’d need to add it under here:

network: {
    tls: {
        certificate: "/tmp/cert.crt"
    }
}

Which means:

• You need some awkward explanation where they should nest it, or an explanation that e.g. “network.tls” translates to nesting.
• They will ask whether they should indent the line you sent them.
• Well, and it’s also surprisingly difficult to explain between which braces they should put the text, and that’s at the end of the braces, but not after the braces etc., if you’re talking to them on a call.

It’s not even that I’m completely enamored with TOML, but this aspect is certainly growing on me…