It’s prism. A multi-launcher for Minecraft Java edition.

Even worse is when they strip the plus sign out after the fact and then you can’t log in anymore because you didn’t realize that’s what has happened.

Yeah, it should inflate to 15TB or more I think

It’s literally says in the link. Go to the link and it’s the title.

Really with they would take security vulnerabilities seriously 😞

Because they are significant, and broad reaching.

Honestly, I more than half agree because the factor most seem to conveniently ignore is that languages and environments that encourage better and safer code are aimed at the lowest common denominator.

The lowest common denominator of developers are the ones that benefit the most from a reduction in defects or unsafe code they may produce. They are the biggest pool of developers. And in my experience, the ones least likely to proactively take measures to reduce defect rates unless it’s forced upon them and/or baked into their environment.

They are the ones that will slap any in typescript to resolve errors instead of actually resolving them, or the ones that will use dynamic in C# instead of actually fixing the bad design … etc

According to all teams I’ve worked on.

Pretty fucking hard.

I know this is satire, But really though better languages that make various classes of defects unrepresentable reduce defects. It’s wild that such a statement needs to be made, but our industry is filled with folks who don’t critically think about decisions like these.

Edit: I forgot this was self-hosted community, disregard.

How does organization work out?

We have dozens of workflows for our monorepo CI/CD stuff. GitHub organization with the flat structure is incredibly annoying.

GitLab is a single file?? (Or am I misinformed? )How does that work out?

A lot of that pain can be reduced by writing and running your code locally before pushing it to a CI environment. Generally with our automation we write a CLI, And GitHub actions is just an execution environment that calls the CLI.

And if what you’re trying to do must execute inside an action. You can run workflows locally with docker!

GitHub Actions mostly.

The rest is usually plumbing and code to support it. The actions are just the automated execution environment.

I disagree.

I don’t necessarily know about new music, artists, or genres. I want to get a mixture of stuff I haven’t encountered.

Something like 60% of the music I listen to in a given month I had never heard of 12 months prior. I’ve found so much music that I vibe with by way of generated playlists.

Discovering something new that scratches my music itch is in itself a pleasure for me, and I can go back to it at a later date, like everything else.

This doesn’t mean I support Spotify, but it does mean I disagree with your stance.

Not a single one of the robot vacuums that I’ve bought in the last 2 years seem to be able to function without internet access.

It’s asinine.

Also they break down so freaking fast. It’s not even funny. Even worse when the part that’s broken is non-replaceable and it’s like a $3 part.

What you say is true.

It’s not a product that you pay for or product that is sold. It is a product that is provided for free. However, that product can no longer be provided for free because Mozilla doesn’t profit off of you using their free product.

Mozilla (the non profit) actually doesn’t aim to profit at all. They aim to support the ongoing development of Firefox and similar projects. Which is currently under risk of not having the necessary funding to pay engineers to build and maintain it.

Mozilla needs more money so that they are not under the risk of sudden collapse if they stop getting money from Daddy Google.

Honestly, it’s a shitty situation to be in. As the grand majority of users don’t understand just how involved browser development is. And those users instead donate to projects that are either forks of Firefox (and directly depend on Mozillas investment) or are (at this stage) toys, like Ladybird.

Which leaves a slim set of choices for the continued funding of the project. All of which it’s core user base hates (Market trend following, new features to see what sticks, AI related integrations, ads, subscription services…etc)

Yet it’s core user base isn’t willing to donate so it’s kind of a self-caused problem.

Side note. IIRC the foundation’s highest paid executive employees make about what a senior engineer at Netflix makes. To put that into perspective.

Firefox is a commercial product. Is it not?

They need to make money so that they can fund hundreds of engineers salaries to keep building it and maintaining web standards operability.

And somehow do this while keeping off with Chrome who has a team 4-5x their size.

Trying to figure out a way to be independent of Google while competing with Google is a tough nut to crack. If they can’t sell it and they can’t get enough donations, then then it comes down to partnerships and advertising.

Then donate!

They are in this situation because they have to keep up with chrome’s capabilities _ velocity with a team that’s 1/4 the size at best.

Essentially they have to produce more with less and they have a funding problem. Almost all of their funding goes into software engineering salaries.

At the risk of not being able to keep up and becoming an obsolete web browser leaving Chrome as the only dominant one there is a shitty position of being the bad guy so that you can get money.

In short, I sympathize with the reasons why they are having to do this even if I greatly dislike them. Reality is complicated.

Wayyyyyyy lesser.

We’re talking Mussolini versus your local grocery store clerk who’s a dick sometimes.

Development time and user support?

These are two pretty obvious reasons. It takes time and time is a limited resource. Therefore, time should be spent on solving impactful problems. Lemmy account login is extremely low impact, it’s not a bad thing, it’s just not something that improves immich for a large portion of its user base.

Another thing is user support. Since the many instances are self-hosted for the most part, and they will go offline, and they will go away forever in some instances. Users asking for support for this login type and asking for additional features to make up for this baked in instability.

Essentially. Low impact work that may drive a higher volume of support efforts.

It’s the same reason some niche projects stop supporting Linux. Low user volume and disproportionately high “neediness” of those users.

Does it support multi-tenancy?

For instance, being a backup and media manager solution for multiple people in my family hosted on one server.

The same with a few friends that want to get out from under Google’s thumb.

I mean, yeah, probably all of these things.

Yes, containers make your application logic work.

That’s the lowest hanging fruit on the tree.

Let’s talk about persistence logic, fail forwards, data synchronization, and write queues next.

Let’s also talk about cloud provider network egress costs.

Let’s also talk about specific service dependencies that may not be replicatable across clouds, or even regions.

Oh, also provider specific deployment nuances, I AM differences, networking differences…etc