• 1 Post
  • 82 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • Libwebkit isn’t actually chromium, it uses blink which is a fork of part of webkit. Understandable confusion though because webkit was part of kde, forked by safari, and then used by through chrome variants for a long time.

    The rest of this comment is going to necessarily be nerdy Linux internals. sorry.

    Unfortunately, I’m pretty sure chromium includes it inside it’s binary and does provide or use any webkit libraries.

    Orca uses it internally for it’s browser so it won’t start unless it has access to the library. When you build a Linux app it includes the name of the library which includes the ABI (basically the version). Newer Linux release include a different version.

    You can see how that specific library stops appearing in Ubuntu releases https://packages.ubuntu.com/search?keywords=libwebkit2gtk-4.0-37

    The new version is 6.0 I believe.

    Appimage is one of the ways you get around this distro problem by including the versions of libraries. That’s why they’re so big. There are problems with that like how big the apps are stale bundled libraries with security issues but I digress.

    Orca hasn’t bundled webkit in the appimage and because of another problem/feature of appimage it falls back on the os library. Since new distros have dropped the older obsolete library version orca can’t start.

    That’s a lot but I hope it explains the problem better.

    I would like to help but my personal computer doesn’t currently have enough memory to compile orca so back to just watching warning people it’s a coming problem for them too.




  • It was actually 3gb because operating systems have to reserve parts of the memory address space for other things. It’s more difficult for all 32bit operating systems to address above 4gb just most implemented additional complexity much earlier because Linux runs on large servers and stuff. Windows actually had a way to switch over to support it in some versions too. Probably the NT kernels that where also running on servers.

    A quick skim of the Wikipedia seems like a good starting point for understanding the old problem.

    https://en.m.wikipedia.org/wiki/3_GB_barrier












  • Feels like the old php metric. PHP had a ton of great code and successful projects but it also attracted very bad devs as well as very inexperienced devs leading to a real quality problem.

    Honestly kinda see thing in a lot of JavaScript applications these days. Brilliant code but also a ton of bad code to the point I get nervous opening a new project.

    My point? It may be a tough pill but it’s not the project framework that makes projects fail, it’s how the project is run.