Ephera

First option for small codebases. Second option when you know your codebase will grow large enough to break things apart into multiple packages.

The thing is, you typically need dependencies for de-/serialization. You only want those dependencies in the parts of the codebase that actually do the de-/serializing. And your model will likely be included in pretty much everything in your codebase, so the de-/serializing code should not be in there.
Well, unless your programming language of choice supports feature flags with which the de-/serializing code + dependencies can be excluded from compilation, then you can think about putting it into the model package behind a feature flag.

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…

I need something without understandable lyrics (unless I’ve listened to that song many times before) and something that pumps me up, but doesn’t cause headaches. So, 8-bit music and cheesy / ‘epic’ cinematic scores work well.

Well, unless it’s 4 o’clock in the morning. Then nothing beats classical music. I’m never as productive as I am at 4 AM, listening to Beethoven and friends.

I guess, if the gender stuff hurts your little brai-brai, then wanting to define everyone as the same singular gender is actually quite consequential…

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

And here I would argue that the Rust library is strictly better, specifically because it will come with an automated or precompiled build of the C library. Compiling C is such a pain.

They are still technically open-source. I’m not saying that they’re not. But they’re actively alienating users who want to use open-source, because those users cannot get support, report bugs or contribute to the project without using proprietary software.

I’m so tired of projects being like “We’re open-source” and then they’re hosted on GitHub, using Discord and whatever fucking other awful tooling they can get their hands on. Thanks guys. I’ll definitely check out your project, yes.

In 2010, Oracle bought Sun Microsystems, which held the trademark for the OpenOffice.org project. The open-source community that developed OpenOffice.org was worried that Oracle would do bad things, so they set up a non-profit, The Document Foundation, and established the LibreOffice project. Most of the outside contributors moved over to contributing to LibreOffice instead.

A few years later, Oracle donated the OpenOffice trademark to the Apache Software Foundation, which is why Apache OpenOffice now theoretically exists. But yeah, it hasn’t seen a non-bug-fix release since 2014. You simply want to use LibreOffice at this point…

Hmm, I don’t know anything about Whoogle, but from other privacy-conscious search engines, I would expect it to work when you use that URL in your bookmark.

Three things I can imagine:

• Something in your hosting stack strips the URL parameters, like maybe your reverse proxy, if you use one. You might be able to see in the Whoogle or web server logs, which URLs actually reach it. Might need to set it to debug/trace logging.
• Maybe there’s a flag in the Whoogle configuration you need to enable to accept these preference URLs.
• It’s a bug in that Whoogle version.

Tangentially related rant: We had a new contributor open up a pull request today and I gave their changes an initial look to make sure no malicious code is included.
I couldn’t see anything wrong with it. The PR was certainly a bit short, but the task they tackled was pretty much a matter of either it works or it doesn’t. And I figured, if they open a PR, they’ll have a working solution.

…well, I tell the CI/CD runner to get going and it immediately runs into a compile error. Not an exotic compile error, the person who submitted the PR had never even tried to compile it.

Then it dawned on me. They had included a link to a GitHub Copilot workspace, supposedly just for context.
In reality, they had asked the dumbass LLM to do the change described in the ticket and figured, it would produce a working PR right off the bat. No need to even check it, just let the maintainer do the validation.

In an attempt to give them constructive feedback, I tried to figure out, if this GitHub Copilot workspace thingamabob had a Compile-button that they just forgot to click, so I actually watched Microsoft’s ad video for it.
And sure enough, I saw right then and there, who really was at fault for this abomination of a PR.

The ad showed exactly that. Just chat a bit with the LLM and then directly create a PR. Which, yes, there is a theoretical chance of this possibly making sense, like when rewording the documentation. But for any actual code changes? Fuck no.

So, most sincerely: Fuck you, Microsoft.

I usually keep todo-lists, where I’ve kind of noted down the next few steps for each feature. And well, those then usually also contain infos for the step I’m currently working on or for previously completed steps.

I rarely actually stick to my planned next steps, but it does help when switching between contexts, if that’s why you’re asking.

Apparently, this is a dogfood burger. No idea why that exists, but I’ll take it, because I’m definitely dogfooding.

I’m building a build system. And I’ve got three previous/ongoing projects where I’m directly integrating it.
And yeah, I’ve noticed that I’m kind of jumping between features, always just building them as far as I need them.

And in particular, I’m not really planning ahead. For exanple, I noticed after the fact that I could easily pull out a whole feature into a separate library, and that would already be useful on its own.

But on the plus side, it’s much easier to figure out actual requirements this way.