You may be joking, in which case: Fair game.

If not… come on. In what world do you write “(…) I’ll find you. Mark my words.” In that kind of context without being (at least humorously) threatening?

-Wfatal-errors is my friend

I see a lot of strange takes around here, and honestly cannot understand where you are coming from. Like really: I’ve written several 100+ page documents with everything from basic tables, figures and equations, to various custom-formatted environments and programmatically generated sections, and I’ve never encountered even a third of these formatting issues people are talking about.

You literally just \documentclass[whatever]{my doc type}, \usepackage{stuff} and fire away. To be honest, I’ve seen some absolutely horrifying preambles and unnecessary style sheets, and feel the need to ask: How are you people making latex so hard?

There’s evidence that knights would dismount before battle to prevent their horse from being injured, even though they knew they were exposing themselves to greater risk. Although we have more technical knowledge about how to “optimally” care for horses now, there’s no reason to believe that we aren’t as or more exploitative of them, rendering them as or less healthy than horses back then.

You are almost on point here, but seem to be missing the primary point of my work. I work as a researcher at a university, doing more-or-less fundamental research on topics that are relevant to industry.

As I wrote: We develop our libraries for in-house use, and release the to the public because we know that they are valuable to the industry. If what I do is to be considered “industry subsidies”, then all of higher education is industry subsidies. (You could make the argument that spending taxpayer money to educate skilled workers is effectively subsidising industry).

We respond to issues that are related either to bugs that we need to fix for our own use, or features that we ourselves want. We don’t spend time implementing features others want unless they give us funding for some project that we need to implement it for.

In short: I don’t work for industry, I work in research and education, and the libraries my group develops happen to be of interest to the industry. Most of my co-workers do not publish their code anywhere, because they aren’t interested in spending the time required to turn hacky academic code into a usable library. I do, because I’ve noticed how much time it saves me and my team in the long run to have production-quality libraries that we can build on.

You’re not seeing the whole picture: I’m paid by the government to do research, and in doing that research my group develops several libraries that can benefit not only other research groups, but also industry. We license these libraries under MIT, because otherwise industry would be far more hesitant to integrate our libraries with their proprietary production code.

I’m also an idealist of sorts. The way I see it, I’m developing publicly funded code that can be used by anyone, no strings attached, to boost productivity and make the world a better place. The fact that this gives us publicity and incentivises the industry to collaborate with us is just a plus. Calling it a self-imposed unpaid internship, when I’m literally hired full time to develop this and just happen to have the freedom to be able to give it out for free, is missing the mark.

Also, we develop these libraries primarily for our own in-house use, and see the adoption of the libraries by others as a great way to uncover flaws and improve robustness. Others creating closed-source derivatives does not harm us or anyone else in any way as far as I can see.

I do exactly this: Write code/frameworks that are used in academic research, which is useful to industry. Once we publish an article, we publish our models open-source under the MIT license. That is because companies that want to use it can then embed our models into their proprietary software, with essentially no strings attached. This gives them an incentive to support our research in terms of collaborative projects, because they see that our research results in stuff they can use.

If we had used the GPL, our main collaborators would probably not have been interested.

This is starting to be some years back, but I was exclusively using apt when I was using Ubuntu, have they gone away from that?

I’ve only ever tried one distro. Please enlighten me on what’s wrong with Ubuntu.

Honestly: Yes. It’s an example that perfectly encapsulates how windows “as a concept” actively babies and dumbs down its users. I the 00’s, nobody had a problem with file extensions, but now that we’re working with users that have grown up with computers we suddenly need to remove them because they’re “too confusing”?

The amount of times someone has asked me why something doesn’t work, and I’ve silently pointed to the sentence or paragraph next to the code snippet they’ve copied…

Well yes, I get the differerence between an interface and a class, and what I write is typically a class, which contains properties and functionality that may or may not be overridden in derived classes.

For example, calling a parent class implementation can be useful when I have a derived model that needs to validate its input in some specific way, but otherwise does the same as the base class.

What I don’t understand is why this makes OOP bad?

I’ve seen this thing where people dislike inheritance a lot, and I have to admit that I kind of struggle with seeing the issue when it’s used appropriately. I write a bunch of models that all share a large amount of core functionality, so of course I write an abstract base class in which a couple methods are overridden by derived models. I think it’s beautiful in the way that I can say “This model will do X, Y, Z, as long as there exists an implementation of methods A, B, C, which have these signatures”, then I can inherit that base class and implement A, B, and C for a bunch of different cases. In short, I think it’s a very useful way to express the purpose of the code, without focusing on the implementation of specific details, and a very natural way of expressing that two classes are closely related models, with the same functionality, as expressed by the base class.

I honestly have a hard time seeing how not using inheritance would make such a code base cleaner, but please tell me, I would love to learn.

Read up a bit on this now, and it definitely looks like something I want to try out! One of the beautiful thing about C is its simplicity, and it looks like Odin has been able to keep that, while introducing some nice convenience features that I often feel like I miss when writing C.

I don’t know if this is done in practice, but if you have a nuclear powered sub, implementing a water electrolyzer that makes oxygen is fairly trivial. Then you have air as long as you have power, so they could in principle stay submerged for ≈ 20 years, or however long the nuclear reactors can go without refill.

I think that’s reasonable. As long as someone is posting relevant content, there should be no obligation to interact with their own posts.

I think people talking about premature optimisation are often talking about micro-optimisations. Those are almost always unnecessary until you’ve identified choke points. Optimising the overall architecture of the code base on the other hand, is in my opinion something that should be thought about before you even start coding. That’s where the major gains can often be done anyway.

I have to admit, I’ve never touched the kind of issue where I need to load a bunch of binaries I can’t automatically trust as part of a build process, so I won’t speak on that.

On the part about OS updates being a PITA, yes: I’ll admit that I offset updating the macOS major version for as long as possible. As long as my major version is maintained/get’s security updates, and the newer versions are backwards compatible enough that I can compile stuff for them without any hassle, I’ll stay on macOS 13. Judging by historical data, that means I have about two more years before I might need to spend an hour or two fixing up stuff that bugs out with the eventual major update.

WINE would like a word

what do you mean? clang is a command line tool, can’t you write some cmake and a bash script to automate the build process? That’s what I always do when I writing any C++ that needs to be compiled/updated fairly regularly.