1. 13
  1.  

  2. 10

    Webkit, gecko and blink are absolutely bloated; I had the pleasure of trying to browse the web on a 2GB athlon-xp a few days ago, emphasis on trying.

    I wish that there was more support (developers and donations) to alternative browser engines, such as netsurf, the one that’s closest to being usable, as far as I am aware.

    1. 4

      This is absolutely what we need. I use Netsurf quite a lot, although there are still quite a few things about it I find frustrating. I no longer use it for Lobsters because I couldn’t upvote or post replies. I also couldn’t use any websites which required ReCaptcha, which is arguably not a bad thing. I also found it didn’t lend itself to a keyboard oriented workflow.

      On the other hand, it was fast, rendered websites well enough, and had a history tree. Beautiful.

      1. 4

        Netsurf is reasonably nice. It was also recently ported to 9front (https://github.com/netsurf-plan9), mostly by Jonas Amoson, Kyle Nusbaum, and others though I helped out a bit with the logistics, git9 bugfixing, OS issues, and merging with upstream.

        1. 3

          Integration between Javascript and DOM integration is the showstopper. They DOM-ified things in netsurf 2, but there’s still a long way to go. The problems you experience with the websites are likely directly to do with that.

          Keyboard oriented workflow could be improved and history tree is indeed nice, but these points aren’t engine-related so I give them less weight. The core of why I like netsurf is to do with its engine, which is designed with a focus on running on resource-constrained systems. The AmigaOS3 port is is one of the better options on AmigaOS, too.

        2. 2

          I wish that there was more support (developers and donations) to alternative browser engines, such as netsurf, the one that’s closest to being usable, as far as I am aware.

          Well, there is this: http://www.netsurf-browser.org/developers/contribute.html

          1. 2

            I’m biased, but I’d say it’s hard to be webcompatible and slim at the same time. But if I wereyou (as power users can bear some comp at risks and misfunction?) I’d totally try building in top of Servo or GeckoView

            1. 1

              These are too slow and bloated, unfortunately.

          2. 3

            I hope this labor of love becomes a long lived project that can exist simply due to WebKit being open.

            Make browsers minimal again

            1. 8

              Make browsers minimal again

              There are plenty of minimal WebKit-based browsers already. It’s actually surprisingly easy to make one: I made a very simple (but usable) browser in a weekend. The work is just in the UI and auxiliary features (bookmarks, password management, etc.)