Because the lowest common denominator is much MUCH lower than you think it is.

This means it’s easy to indoctrinate and easy to maintain that for a massive number of people.

Scientific illiteracy is extremely high, and actual “6th grade reading comprehension” is the highest level of literacy for > 50% of a country like the U.S. and ~20% are low literacy or actually illiterate.

This means that half of everyone in the U.S. can read and understand what they read at or below a 6th grade level. This isn’t “reading big words”, it’s “tell us about what you read”, “what is the relationship between x & y” type questions.

This comment for example, up to this point only, would be difficult to understand & comprehend for > 50% of people in the U.S. (it demands an 11th grade reading comprehension). And may be misread, misunderstood, or not understood at all.

People are driven to religions to cults and alt conspiracy theories when they don’t understand how the world works around them. They latch onto extremely simple often misleading or incorrect ideas of how the world works because they can understand it and it “makes sense” within their sphere of ignorance (we all have one, this isn’t meant to be a disparaging term).

This means that the problem is that humans are just not smart enough to escape religion yet. It’s the simplest answer, and it appears to be correct.

The language it’s written in has very little, almost nothing, to do with how efficient larger applications are.

This is almost entirely up to the design and day-to-day decisions of the developers. These almost always outweigh the efficiencies of the underlying languages themselves (within reason).

A single location of poor data access patterns could negate the aggregate performance gains of your entire application, as an example. A framework that prevents you from making simple mistakes and drives you towards more efficient patterns goes much further than the language is written in.

Between Rust, C#, Java, and Go you’re essentially even on performance for large applications (with C# pushing ahead of the pack). What you are not even on is engineering efficiency, it’s going to take considerably longer to build the same set of features in rust than any of the others listed. And the performance is likely the same, potentially even worse depending on the maturity of the ecosystem.

Rust is a great systems design language and a great language to choose when developing high efficiency libraries & frameworks for I/O and data processing. It’s not really a great choice for application development due to how slow it is to actually get things done in.

I fully expect to see alternate backends written in more operationally efficient languages over the next decade that will catch up to the official Lemmy codebase, and potentially even replace it. It actually sounds like a super fun project, funding is always a problem though.

Ok…

So your point is that a bad logging implementation is bad. And I agree.

I’m not seeing how that’s extendable to implementations as a whole. You’re conflating your bad experience with "log aggregation is bad’.

Just because your company sucks at this doesn’t mean everyone else’s does.

Yeah, ofc it is.

I’m working in a system that generates 750 MILLION non-debug log messages a day (And this isn’t even as many as others).

Good luck grepping that, or making heads or tails of what you need.

We put a lot of work into making the process of digging through logs easier. The absolute minimum we can do it dump it into elastic so it’s available in Kibana.

Similarly, in a K8 env you need to get logs off of your pods, ASAP, because pods are transient, disposable. There is no guarantee that a particular pod will live long enough to have introspectable logs on that particular instance (of course there is some log aggregation available in your environment that you could grep. But they actually usefulness of it is questionable especially if you don’t know what you need to grep for).

These are dozens, hundreds, more problems that crop up as you scale the number of systems and people working on those systems.

Ah, the circle of life

They usually do yes however it’s all about prioritization.

You may have hundreds or thousands or open requests and issues.

With tens of thousands of closed issues that were either not reproducible, not actually problems, or largely indecipherable.

There’s usually a feature roadmap which is where most of the development money and time is spent. If it’s an older business application then certain bugs might easily take weeks to find, fix, test, validate, go through user acceptance, A/B test, and then deploy. But fixing is expensive work, so if the bug isn’t severe it’s usually deprioritized next to higher priority work.

I love this.

Especially being written in a language like C#. Which makes it incredibly accessible to work on, performant, and long-lasting.

Straight to the personal attacks, I’m sure this can only end well.

This is not how you promote a project…

You shouldn’t be opening up access to your Jellyfin server to the internet, that’s why.

Not only are there known vulnerabilities that can, and will, be abused by bad actors (Not even humans, automated systems). But it also provides a convenient way for media entities & your ISP to target you in mass piracy crackdowns.

Nevermind the undisclosed or unknown vulnerabilities that may be exposed by Jellyfin.

Having it behind a VPN protects you and your media.

I can already tell that this community is going to be an absolute dumpster fire with this sort of narrow visioned with hunt modding attitude.

And I don’t even think the problem is the community existing hail corporate is a hilarious and fun concept. I think the problem is the person creating and saying they are going to mod the community being narrow-minded, and toxic.

Yeah I see this turned into a witch hunt for places where fruitful discussion may have otherwise happened.

It’s interesting to get an inside view and how some corporations do their BS, which usually requires discussing it which is often kicked off by some complaint or misunderstanding of how the world works.

You can’t buy the idea of it because you don’t understand the theories around it?

That’s an odd stance.

Would it not be better to respect and explore the idea instead of trying to dismis is through ignorance?

You’re right, we should all stop talking about and discussing problems and risks. And silently stare at each other tille someone else comes up with a solution.

Step 1 in fixing a problem is to recognize and get awareness for it.

Step 2 is garnering interest from the people who are qualified to actually make realistic proposals

Step 3 is collaborating on ideas to figure out what will or won’t be effective, and to create new ideas by returning to step 2.

Step 4 is to circle back to step 1, but for actions and implementations. Repeat ad nauseum.

**We’re Still in Step 1. ** Complaining that we aren’t getting to the next step quick enough without providing assistance to get there is incredibly meta to this process 🤔

I’m finding the opposite…

Lots of posts made by bots, with majority top level comments being short quips and attempts at jokes as opposed to discussion. So many discussions devolve into ad hominems almost immediately.

Just like Reddit.

It’s a social media phenomenon I think. The lowest common denominator will always dominate unless communities push against it.

You’re down voted, but you’re right.

Naysayers are looking at AI capabilities today. Not AI capabilities in 10-20 years.

AI accelerates AI development/advancement.

… Maps?

Plat maps, land use maps, survey maps…etc can date to the early 1900’s and late 1800’s. Preserved & converted to digital form for country-side USGIS visualizations and mapping.

Or architectural blueprints, or sewer/water line diagrams/maps. Electrical & communication lines are approaching that age. Transportation infrastructure and diagrams.

We reference documents & technical knowledge that’s 30-50 years old, sometimes 70-80 years old right now in our industry. Mathematics knowledge that’s well over 100 years old.

There are countless examples of important things that are as old as the industry itself.

It’s essentially guaranteed that we will be referencing technical documentation and design and knowledge that is over 100 years old once this industry is old enough.

Bots taking the place of humans when it comes to social interactions is NOT a net positive…

It was negative side effects that we have been seeing for years now. One of which is the removal of organic human behavior, bots driving extremism & polarized views/discussion, and humans losing empathy for each other without realizing it’s the bots that despise.

Let’s not turn lemmy into reddit v2

OOTL what are tankies?

So, essentially, really poorly written malware? Given the number of assumptions it makes without any sort of robustness around system configuration it’s about as good as any first-pass bash script.

It’d be a stretch to call it malware, it’s probably an outright fabrication to call it a virus.

Sounds like a fun project 🤔