3 ms·

Also, Luakit: http://luakit.org/ http://luakit.org/ It has lots of extensions, like Adblock and Noscript, written in highly-readable Lua, also making it very h

Also, Luakit: http://luakit.org/ http://luakit.org/ It has lots of extensions, like Adblock and Noscript, written in highly-readable Lua, also making it very hacker friendly and very fast.

scrollaway 11y ago
Last time I recommended Luakit, I was told it was no longer developed and superceded by dwb (linked below by someone else)
- gh02t 11y ago
  dwb is dead too, fortunately there is a replacement for that too: https://github.com/The-Compiler/qutebrowser https://github.com/The-Compiler/qutebrowser . It's already pretty much a drop-in replacement. The dev is very responsive and friendly as well.
  - XzetaU8 11y ago
    Sure it's not that active but I wouldn't call it dead. last commit: 2015-07-26 https://bitbucket.org/portix/dwb/commits/ https://bitbucket.org/portix/dwb/commits/
    - gh02t 11y ago
      I thought I remember seeing a thread on Reddit that it'd been abandoned around that time and wasn't just inactive, but I could be mistaken.
      - XzetaU8 11y ago
        It's right there on your qutebrowser link, dwb is first on the "Similar Projects" list (Scroll down) their "Unmaintained" comment leads to the reddit thread you mention, mind you that thread is 1 year old and the user/post is deleted: https://www.reddit.com/r/linux/comments/2huqbc/dwb_abandoned/ https://www.reddit.com/r/linux/comments/2huqbc/dwb_abandoned...
        gh02t 11y ago
        Ah, I see. Either way, I was eager to switch at the time as webkitgtk had a bad bug in it that would cause dwb to insta-crash on loading a page about once an hour and which wasn't getting fixed. Qutebrowser is based on Qtwebkit and didn't have the same issue, so I jumped ship pretty early in its development.
- mitchtbaum 11y ago
  The code itself works very well. Mason, founder of Luakit and most generous contributor, got hit by a bus so new maintainership roles have yet to get filled by existing and new users and developers. All current development takes place outside of "central" repo, and it needs organizing and compiling. Once this takes place, development and merge requests can continue full course.

Also, Luakit: http://luakit.org/ http://luakit.org/ It has lots of extensions, like Adblock and Noscript, written in highly-readable Lua, also making it very hacker friendly and very fast.

scrollaway 11y ago

Last time I recommended Luakit, I was told it was no longer developed and superceded by dwb (linked below by someone else)

gh02t 11y ago
dwb is dead too, fortunately there is a replacement for that too: https://github.com/The-Compiler/qutebrowser https://github.com/The-Compiler/qutebrowser . It's already pretty much a drop-in replacement. The dev is very responsive and friendly as well.
- XzetaU8 11y ago
  Sure it's not that active but I wouldn't call it dead. last commit: 2015-07-26 https://bitbucket.org/portix/dwb/commits/ https://bitbucket.org/portix/dwb/commits/
  - gh02t 11y ago
    I thought I remember seeing a thread on Reddit that it'd been abandoned around that time and wasn't just inactive, but I could be mistaken.
    - XzetaU8 11y ago
      It's right there on your qutebrowser link, dwb is first on the "Similar Projects" list (Scroll down) their "Unmaintained" comment leads to the reddit thread you mention, mind you that thread is 1 year old and the user/post is deleted: https://www.reddit.com/r/linux/comments/2huqbc/dwb_abandoned/ https://www.reddit.com/r/linux/comments/2huqbc/dwb_abandoned...
      - gh02t 11y ago
        Ah, I see. Either way, I was eager to switch at the time as webkitgtk had a bad bug in it that would cause dwb to insta-crash on loading a page about once an hour and which wasn't getting fixed. Qutebrowser is based on Qtwebkit and didn't have the same issue, so I jumped ship pretty early in its development.
mitchtbaum 11y ago
The code itself works very well. Mason, founder of Luakit and most generous contributor, got hit by a bus so new maintainership roles have yet to get filled by existing and new users and developers. All current development takes place outside of "central" repo, and it needs organizing and compiling. Once this takes place, development and merge requests can continue full course.