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.

I don’t think the concern over pinging 1.1.1.1 is warranted.

ICMP is pretty raw Network traffic, meaning you’re not really causing much actual load here.

You can’t even really try to DDOS with normal ICMP packets. You usually have have to max it’s size out at 64KB with an ICMP floor to even think of having an effect. Vs the, effectively inconsequential, 32 bytes of a normal ICMP packet.

You watching a short YouTube video is equivalent Network load as 180 days of pinging for Network up time.

They keep giving us more reasons to sail the high seas.

This is what LGPL is for.

You can still use a library like a library freely, without restriction, but you are keeping your IP protected from being copied cloned and modified elsewhere.

I’m going to guess because of the tools that don’t use LGPL.

Which makes them quite limiting and kind of controversial since you have to adopt their license from my understanding, even if used as a library.

I try and use LGPL on all my projects since it allows others to use the Library as a library, and anyone that wants to modify or use the source has to copy left.

Naw, they’ll find some way to “incentivize” (punish you for not) viewing ads and enforce it with eye tracking.

Super glue seems appropriate 🤔

“unfortunately your In-Flight Engagement Actions ™️ did not meet the requirements to qualify you for in flight perks such as entertainment and meals”

“Please ensure you are looking directly at the screen while ads are playing to accumulate In-Flight Engagement Actions ™️”

Coming soon to an airline near you.

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.

Not trying to start an argument here but I do want to point out that your argument foundations on blaming other competitors instead of looking at what can make the platform you’re passionate about more palatable.

There are many, MANY, reasons people will choose Mac and windows on their own accord.

Your argument hand waves that away to make a boogieman out of mac and windows, and erodes the true viability of Linux as a platform by not looking at how it can improve, and instead focusing on how the competition “is bad”.

Taking the ego stance that Linux “would be great if it wasn’t being held back by the bad guys” doesn’t actually help Linux desktop adoption…

It turns into a Linux problem when it holds back Linux desktop adoption by creating a difficult or even toxic environment for new, low-technical or non-technical users.

I mean if you’ve never seen or used a car before, and someone from a position of relative authority or trust gave you a very convincing argument that a particular part that you don’t understand is easy to remove and you’ll benefit from it…

Yeah it’s pretty reasonable that the average person might shoot themselves in the foot by letting them remove that part (tell them a command to run).

I mean you essentially just highlighted a primary user experience problem with Linux…

Information & advice is fragmented, spread around, highly opinionated, poorly digestible, out of date, and often dangerous.

And then the other part of it is that a large part the Linux community will shit on you for not knowing what you don’t know because of some weird cultural elitism…

When you finally ask for help once you realize you don’t know what you’re doing, you’re usually met with derisive comments and criticism instead of help.

Do you want Linux to be customizable so that users can control it however they want. Or do you want it to be safe so that users don’t mess it up? You can’t have it both ways, and when you tell users to “go figure it out” and then :suprise_pikachu: that they found the wrong information because they have literally no idea what’s good or bad, instead of helping, they get shit on.

It’s the biggest thing holding Linux desktop back.

Damn, that’s just cancerous

Yeah I had literally no idea what you were talking about until you mentioned the actual name in the comments.

NPM almost universally refers to node package manager in any developer or development adjacent conversation in my experience. Given that both the site, the command, the logo, and the binaries are “npm” makes that more appropriate.

Nginix proxy manager is far to niche to be referred to universally by acronym when it’s only ever used as an acronym when the context for it’s usage has already been defined (ie. In it’s documentation).

This becomes much more clear when you Google the acronym.

It is, but also it’s worrisome since it means support is harder, which means risk of abandonment is higher and community contributions lower. Which means “buying in” is riskier for the time investment.

Not really criticizing, 10/10 points on making something and then putting it out there, nothing wrong with that. Just being a user who’s seen too many projects become stale or abandoned, and have noticed that the trend has some correlation to the technology choices those projects made.

I’ve been looking a platform for personal blog, portfolio, and what not that’s kind of fun to play with without having to build the whole thing myself.

What’s your opinion of this project?

As of today I’m actually in a lucky position where I am now able to set up a secondary NAS at my brother in laws and use that as a backup server that I can back up to essentially in real time.

All it’ll cost me is the hardware and the electricity.

Yes.

I’m sure one can reasonably infer that I do not mean 30 meters.

Conveniently at highway speeds 30 minutes and 30 miles away are essentially equal.

I’ll try and use appropriate notation next time