I spent an unhealthy amount of time on Reddit. Getting bored of Lemmy is a feature, not a bug. Embrace it.

Before I understood Docker, I used to have HA installed directly on bare metal side by side with other “desktop” apps.

To be able to access devices, HA needs many different OS-level configurations (users, startup, binding serial ports, and much more I don’t have a clue about). It was a giant mess. The bare OS configuration was polluted with HA configurations. Worse, on updating HA, not only did these configurations change, the installation of HA changed enough that every update would break HA and even the bare OS would break in some ways because of configuration conflicts.

Could this be managed properly through long term migration? Yeah, probably, but this is probably a ton of work, for which a purpose-built solution already exists: Docker. Between that and the extra layer of security afforded by dedicating an OS to HA (bare metal or virtualized), discouraging the installation of HA in a non-dedicated environment was a no brainer.

If it’s such a problem, maybe we just collectively move on to ES or TypeScript nomenclature?

This is what happens when stack overflow is used for training.

The thing holding me back is multi monitor support. It’s just atrocious on Linux (and has been for a long time). I have issues with:

• can’t duplicate screens (“not supported” huh?),
• random screen not detected,
• broken layout when screen changed,
• flickering and constant layout changes

Not sure if anyone has tips? NVIDIA and Intel displays, scarred to even try VR.

The software is not the problem. Software breaks all the time. The problem is monocultures and centralization. Building entire industry ecosystems all around a single point of failure. This is the just-in-time manufacturing supply chain disruptions and fragility all over again.

Who knew, a diverse ecosystem was a strength, not a weakness.

Not too surprising if the people making malware, and the people making the security software are basically the same people, just with slightly different business models.

I suspect rebasing makes sequential commit IDs not really work in practice.

I think this is satire. Poe’s law is stronger than ever

Terminals are powerful and flexible, but still slower than a dedicated UI to see states at a glance, issue routine commands, or do text editing.

Terminal absolutists are as insufferable as GUI purists. There is a place and time for both.

Can’t tell if you are joking. I know a lot of junior developers who think this is a legitimate solution.

Asking your employer for more compensation because you are exerting more effort due to inexperience isn’t so different than a AAA studio charging high fees for a crappy product because of corporate bullshit and inefficiency.

In fact, these two things tend to be two sides of the same coin.

I do OOP because it naturally encourages me to do this sort of thing: abstract complicated logic into inspectable, reusable, testable properties of an object.

I think you are mostly right, except Lemmy and reddit are not organized.

Anyone can build a bridge. Only an engineer can build a bridge that barely stands.

In the same way, the fact that one built a large online platform, that doesn’t necessarily mean it was built with minimal ressources and without taking past or future risk.

Engineering is, as a profession, specifically the application of scientific principles to solve problems the right way, the first time, that is to say efficiently, and with minimal risk.

The fact that one codes, or wields a wrench, or operates a C&C machine does not mean one is applying science to solve problems efficiently and managing risk. These are entirely different skills and professions.

Fork the last commit with a LGPL commit?

GPL mentions explicitly that it is irrevocable, where as LGPL doesn’t mention anything about it. IANAL, but it looks like there is a case for irrevocable without violation of clauses by default https://opensource.stackexchange.com/questions/4012/are-licenses-irrevocable-by-default#4013

For people considering contributing to FOSS in the future, maybe check for irrevocable clauses? I wish licenses selectors https://choosealicense.com highlighted this part more clearly.

You should perhaps skim through https://docs.docker.com/storage/ quickly. That document explains that docker containers only have very limited persistence (this is kind of the whole point of containers). The only persistence of note is volumes. This is normally how settings are saved between recreating containers.

As for dependencies, well it’s possible that one container depends on the service of another. Perhaps this is what you are describing?

Either way, for more detailed help, you will have to explain your setup with more specific technical details.

This wouldn’t pass PR review and automated tests, unless they were a senior dev and used elevated privileges to mess with things behind the scenes.

To add to what has already been said about it taking a large effort, the follow up question is then, why don’t governments fund all this effort publicly through taxes, like what is done with roads, scientific research, education, healthcare?

Well the short answer is that high-performance computing specifically is a strategic resource. Publicly funding roads only benefits the country doing the funding, so that is an easy decision to make. Meanwhile, much of the publicly funded scientific research has minimal to no strategic value (or may only be of value in states capable of that investment in the first place), so this is also an easy decision to make. But giving away technological investments in strategic ressources to rival states is a pretty bad move.

We should strive for a wide range of test cases. Real testing is done when the software is tested against a wide range of user inputs. Code coverage is no indicator of response to cases.

Unit tests are a fantastic way of implementing test cases. I am of the opinion that most bug PRs should start with a unit test, if nothing else, a persistent reminder that: hey BTW, your user is going to input this garbage, so any logic you implement ALSO has to be resilient against that garbage.