this post was submitted on 06 Aug 2024
80 points (100.0% liked)

Technology

37599 readers
273 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] onlinepersona@programming.dev 4 points 1 month ago (1 children)

I hope an opensource, non-C/C++ browser will pop up that can claw back from Chrome/Chromium. It's about time.

Anti Commercial-AI license

[–] Markaos@lemmy.one 3 points 1 month ago (1 children)

Why not just say Rust? There isn't really anything else that would provide good enough performance for a browser engine with modern heavy webpages while also fixing some major pain point of C/C++

[–] onlinepersona@programming.dev 3 points 1 month ago* (last edited 1 month ago) (1 children)

Go is not an option? Zig neither? Even Java would be better (it's used in high-frequency trading) than C++.

Rust is not the only contender.

Anti Commercial-AI license

[–] Markaos@lemmy.one 1 points 1 month ago

Zig didn't come to my mind when I was writing my comment and I agree that it's probably a decent option (the only issue I can think of is its somewhat small community, but that's not a technical issue with the language).

My argument against Go and Java is garbage collection - even if Java's infamous GC pause can apparently be worked around with a specialized JVM, I'm pretty sure it still comes at the cost of higher memory usage and wasted CPU cycles compared to some kind of reference counting or Rust's ownership mechanism (not sure about the proper term for that). And higher memory usage is definitely not something I want to see in my browser, they're hungry enough as is.