Firefox is partially in this position because the community really does not support Firefox. Every decision Firefox makes or Mozilla makes in an attempt to try and claw back their financial freedom away from Google, the community dumpsters them on. Then, on posts like this, the community turns around and dumpsters Firefox for being so financially dependent on Google.

FireFox was and is an awesome project, but unfortunately, without the financial backing of a large for-profit business, they cannot keep up with Chrome. Even then, FireFox, with an engineering team a quarter the size of Chrome’s, still manages to keep up, which is a god damn miracle.

Developing a browser that is fast, actually works with new web standards, stays up to date, and is adding features is incredibly difficult. It is a stupidly expensive endeavor, similar to the level of effort necessary for operating systems.

And unfortunately, there is no Linux equivalent for web browsers, at least not right now. There are some up-and-coming projects, but it’s going to be decades before they reach the level of maturity necessary to start competing against Chrome. At which point there may be so much standards capture that some of these browsers may find it impossible to actually catch up.

You know, I seem to see this rhetoric a lot, and it seems to be getting upvoted more now, which isn’t a good sign for Lemmy, but are you really surprised by this? Is this really a question? Are you really that under a rock?

If it’s rhetorical, then what’s the point? Is this just a petulant way to try and dumpster something without going through the effort of actually picking out a real problem with it, of which there are countless?

Is this starting an interesting discussion? Is this voicing an interesting opinion? What is the point of this exact kind of comment?

Maybe I’m just too autistic and I’m going off the rails here, but these are starting to itch like a form of “internet forum hives”.

In all sadness, folks on Lemi and other more technically inclined forums infight even more than leftists infight, and all they do is sabotage themselves.

Projects like Firefox are mountains above Chrome when it comes to privacy and not ceding web control over to Google. Yet any thread about anything Firefox is doing is just filled with FUD from people complaining about small individual changes or Firefox not being perfect enough, so on and so forth.

It’s self-sabotage. If you didn’t think Firefox is good enough, congratulations. Now you’ve got Chrome, and pretty soon you won’t have Firefox.

😒

Actually, reading stuff can be a bit of a high bar for some folks, unfortunately.

I think there’s a fundamental misunderstanding here.

All of the qualities that make a codebase easier to read, maintain, and consume by humans do the same things for LLMs.

A codebase designed for humans is a codebase that is designed for LLMs. It’s just that most teams don’t even know how to design a codebase for humans. And those same teams just kind of accept LLM and Agent Slop as “Designed for LLMs”. When it most definitely is not.

• Patternization
• Structural consistency
• Naming conventions
• Style Opinionation
• Organizational conventions
• Safety and Quality Standards
• …etc

All these things matter just as much for humans as they do for LLMs. And like I said previously, most human developers don’t understand these things and do not optimize for them anyways. Which means that most human developers are ill-equipped to create codebases that are not degrading rapidly under the use of agents.

This is a bit of a rant of mine… because I’ve spent the last decade learning how to optimize software engineering to best fit the needs of humans. Now that LLMs are crashing onto the scene, teams that already were writing slop by hand can now write slop at twenty times the rate. And then seem to think that all the things that make for good software no longer apply to them

What do you think LLMs were trained off of, my friend?

Funny enough, this threshold for what you find dirty or gross can cause a lot of relationship strife within a household as partners may have different thresholds for this.

Generally, the partner that has a lower threshold for when they feel like things are too dirty or too messy or too gross and it starts bugging them feels like they do most of the cleaning work because they start feeling stressed and end up cleaning earlier then the other.

This is also assuming that reading and writing are mutually exclusive.

The places where this level of storage density and longevity are valuable are places that are generating terabytes or tens of terabytes a day. Especially scientific research.

It is definitely an interesting development, and the lack of bit rot makes it incredibly useful as an archival system. However, I am curious if the surrounding hardware necessary to actually successfully read from it is going to be as long-lived. Similar to magnetic hard drives, I am sure the plates that are being written to need to exist in an extremely sterile and particle-free environment in order to be read and written to.

At 10MB/s it’d take you 416 days if constant writes to fill it up.

EXTREMELY slow archival.

At least for now, till it gets better

It’s a classic knee jerk from commenters who don’t know what they are talking about.

A tale as old as time.

… What?

Are you drinking your grandma’s bath water again?

No, they still rely on the Firefox engineering team to keep updating Firefox and to keep adding necessary additions for web standards, security updates, performance fixes, and so on and so forth.

All of these forks will fall behind web standards changes and effectively just become the Firefox flavor of Internet Explorer over time. It won’t happen overnight. You’re right about that, but it will most definitely happen over the course of a few years. Effectively handing full control over to Google and Chrome

All of these forks rely on Firefox to provide the hard bits in order to keep up with Chrome, or at least attempt to keep up with Chrome.

Building a browser is pretty damn hard, and honestly, it’s a miracle that even the Firefox engineering team has managed to do what they do, given they only have, at best, a quarter of the resources that Google puts towards their browser.

It’s a lot more than just video. It’s all your audio while you’re in the car. Your driving habits, your location, your devices, who is in the car with you so on and so forth.

There’s a ton of data that can be gathered and associated without having to have a camera.

If you ever talk in your car and it’s a modern car. Congratulations! That’s being recorded cataloged and sold off to the highest bidder.

That’s the point. This is just a foot in the door to block your access to print things that might be trademarked copyrighted or affiliated with your corporate overlords.

And a foot in the door to start blocking your right to repair your own things.

Guaranteed.

90%?

More like 99.999%

Including op.

There’s a difference between building a pile of crap and actually building something that works effectively. It’s a difficult hardware and software problem.

You mean all the forks that rely entirely on the Firefox engineering team to exist?

Exposed endpoints that have no authentication and various other things like that.

It’s application level security issues.

If there is an older collation here https://github.com/jellyfin/jellyfin/issues/5415

Yes for yourself on a device that supports it but that doesn’t address what my post stated.

The devices that I listed in my post are still going to run to the same problem in that sense that you’re not going to be able to run tailscale on them either.

It is incredibly difficult to get jelljfin ypen into your friends or your parents or grandparents house without considerable setup and maintenance over time.

And effectively none of the Jellyfin clients support this…

So that’s not going to work anyways on your friend’s TV or their Xbox or their Roku or something else like that.

Problem is access outside your home for family and friends.

There are serious security gaps that make it a non starter to expose to the internet.

I’ve been using Jellyfin ever since they forked out of Emby, and honestly, it’s the biggest complaint that I have. It is incredibly difficult to make it available to friends and family who are on various devices, networks, so on and so forth.

Whereas Plex “just works.”