To be fair, most tools are pretty bad at all other jobs besides the one it was made for. Same goes for an OS. If Ubuntu is made to off ramp people more comfortable with Windows, then that’s just a fine purpose for aln OS.

I wouldn’t describe Microsoft as a walled garden (and Canonical even less). But maybe that term comes with degrees, and different perspectives of what’s tolerable.

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.

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.

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.

The job of HR is to manage employee needs, not to make business decisions, like what kind of employees are a good fit for a team. The moment HR gets involved with that decision making is the moment a poisonous cancer mestastatises and starts killing the company from within.

Just a thought, communities dedicated to one particular gender are often not inclusive by design, especially if you actively try to funnel people of a certain gender to certain communities. And therefore they, historically, have tended to devolve into echo chambers, and then subsequently into toxic spaces, with little room for nuanced discussion nor hosting a broad range of opinions. That’s not to say all communities are like this and most don’t start out like that either. There is value to have these communities if they themselves promote inclusion. But putting people of a particular gender into a gender-specific community is not at all the solution to “Too few women on Lemmy”.

I’d rather see the focus on making the general communities be welcoming to everyone equally.

Software dev is full of obscure keywords that describe otherwise pretty simple or basic concepts you stumble upon in practice naturally and that you probably already understand.

• singleton: a class/object that is designed to be single use, i.e. only ever instantiated with a single instance. Typically used when you use class/objects more for flow control or to represent the state of the program itself, rather than using it to represent data
• immutable: read-only, i.e. unchangeable
• dependency injection: basically when you pass a function or object into another function object, thereby extending their effective functionality, typically for modular code and to separate concerns.

Here’s one more of my favourite examples of such a keyword: memoization

The right example is poorly executed. The left example is fine, but has one crucial deficiency: it’s not very modular, which makes it difficult to test and scale. Big problems need to be broken down and managed in discrete steps, and this is also true of computer code.

The left example is like running a pizza shop where you explain all the steps to everyone and then let everyone loose at the same time to make a pizza. The right example is like creating stations and delegating specific responsabilities to one person at a time.

The former creates redundancy and is manageable at small scale. But as you grow, you find that the added redundancy is of no additional value, while you end up with chaos, as people argue and fight over the process.

Can you imagine five developers working on the monolithic pizza code all at the same time? Total chaos. Better to have one developper assigned to baking, another assigned to prep, etc.

Someone tells you what to do, and you have to obey or else you lose your housing, healthcare, and other basic necessities.

This is so wrong. You are not entitled to basic necessities. You have to provide them for yourself, that is the natural order. This is what most of humanity did for milenia via subsistence farming and it sucked.

Sooner or later people decided that working in a factory sucked a little less than working in the field. Then more recently, people decided working in an office sucked a little less than working in the factory.

Employment is not slavery. You can quit anytime.

No one else uses the term “cloud” like that.

That part of this comic really stuck out like a sore thumb. I can’t tell if it’s an oversight, a comment about the challenges of self-hosting, or subtle mockery of self-hosting hypocrisy.

Centralized power is authoritarian. Authoritarianism isn’t exclusively right. In fact the right/left dichotomy is a simplification of politics that belongs in the stone age. People have different values across a range of issues, that often don’t fit a specific mold.

“Government” is a pretty broad term. It encompasses both elected or ruling leaders that implement policy (politics), as well as the administrative beaurocracy that implements whatever policy is enacted day to day. It’s pretty typical for the beaurocracy to continue functioning under whatever mandate they have and even to make their own descisions if the mandate gives them that latitude, even if the leadership part of the government is being changed or otherwise non-functional.

I guess people forgot how the internet itself used to be a “monoculture” of nerds and weirdos. Weirdos and nerds have been making the cool trendy places that the mainstream first shuns and mocks then flocks to (maybe “ironically” at first) for centuries. Maybe even millenia.

Information is power. Information is used against you pervasively for control. This control ranges in nefariousness. You want examples? Here are some examples of consequences of use of information as a means of power:

• A present or future employer making HR descisions based on your behaviour outside of work.
• An insurance provider discriminating you and your coverage based on some knowledge like a pre existing condition or behaviour
• Behaviour that is socially acceptable today or appropriate in context being broadcast in the future when it is not or out of context
• Defamation
• Extortion
• Being targeted for having certain political thought
• Being targeted by perpetrators of acts of violence, theft, or nuisance (think swatting)
• Being manipulated into making purchasing or life descisions that are not in your best interest
• Systematic or discrete racial, sexual, religious or other identity discrimination
• …

The usual response to a list like this goes something along the lines of, bah, none of that will happen to me, I’m a goody-two-shoes. That advice is about as good as saying “I’m a good driver, I won’t get into a crash, so I don’t need to wear a seatbelt”. Back to my point, the consequences of information used against you are too far and too abstract for people to accept.

The problem isn’t that people don’t care. The problem is that the negative consequences are too abstract/too far to see. Not so different than smoking or climate change denial.

This a 1/1000 likely outcome. Bankrupted companies will typically sell assets including IP and software to other companies to pay creditors (which excludes open sourcing them). And well before bankruptcy, any financial issues will cause Plex to be modified to support shitty monetization to the point that you won’t want the source code amyway.

Sorry for the bad outlook, better that you be ready than to hope for a unicorn.