nEXT Browser

Dev tools

programmable browser

SHOW HN2017

132points
44comments
#309of 2,242 in 2017
Top 14%of 2017 by points

How HN took it

MixedNo clear lean

6 positive, 6 neutral or asking, 0 mixed, 3 critical, out of 15 comments about the project. Thread score +0.15.

Idea: 4 for, 1 againstDesign: 0 for, 2 againstExecution: 1 for, 0 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Excited by a Lisp-controlled desktop and browser

    From 3 comments
    • Oh, this is awesome! Between StumpWM, emacs & now nEXT, my entire desktop could be Lisp. Rather than using ECL to embed Lisp in C++, have you considered using an FFI to call out…
      zeveb on HN
    • Wow, this is actually an amazing idea! Great job.
      patricksimpson on HN
    • Holy cow. Great job. Sadly i'm busy even on weekends atm, but i'm bookmarking this and i will try to contribute when i find some time.
      orwin on HN
  • Interest in a programmable alternative to Vimperator

    From 1 comment
    • Now that Vimperator is mostly dead, this looks like a potentially interesting alternative to have a programmable browser.
      nextos on HN

Objections

  • Not truly Lisp-based since rendering is delegated to QtWebKit

    From 2 comments
    • How is this “Lisp-based” when it’s a wrapper around QtWebKit? I’d expect a “Lisp-based” browser to implement its rendering engine in Lisp, probably atop CLIM. Otherwise you’re…
      eschaton on HN
    • Then Emacs does not count as a Lisp based editor too, given it's renderer is in C.
      gkya on HN
  • Name conflicts with existing Next Browser and NeXT trademarks

    From 2 comments
    • This feels like a particularly ill-considered name. First off, there is already commercial software called "Next Browser" -- it appears before your code in google searches. I…
      SeanLuke on HN
    • The logo and odd capitalization of "nEXT" might get some attention from Apple laywers, if they care about the NeXT trademarks at all anymore.
      ams6110 on HN

Requests

  • Ad-blocking support

    From 1 comment
    • Oh, this is awesome! Between StumpWM, emacs & now nEXT, my entire desktop could be Lisp. Rather than using ECL to embed Lisp in C++, have you considered using an FFI to call out…
      zeveb on HN
  • Windows binaries

    From 1 comment
    • JMercouris, Thanks for this, you made my day!! I was always curious of what could be done using EQL. Do you have binaries compiled for Windows​? What would your recommendation be…
      flavio81 on HN
  • Replace HTML, CSS and JavaScript with Lisp-based formats

    From 1 comment
    • I love it! Now, if it can render content where: - HTML is replaced with S-Exprs - CSS is replaced with lisp - javascript is replaced with lisp Then I think I'll be ready to join…
      peatmoss on HN

Questions

  • What rendering engine is used

    From 2 comments
    • What rendering engine does nEXT utilize, assuming you didn't write a rendering engine in Lisp?
      dna_polymerase on HN
    • What's it using as a browser engine?
      soperj on HN
  • Where are the pre-built binaries

    From 1 comment
    • The readme references a "releases" section to go to for pre-built binaries. Is this not available yet?
      kup0 on HN

Alternatives named

  • Qutebrowser

    From 1 comment
    • Qutebrowser – a keyboard-focused browser with a minimal GUI | https://news.ycombinator.com/item?id=15458824 (Oct 2017, 91 comments) >vortico: This is definitely the best hackable…
      j_s on HN
  • Hiccup, Garden and ClojureScript

    From 1 comment
    • HTML: https://github.com/weavejester/hiccup CSS: https://github.com/noprompt/garden Javascript: https://github.com/clojure/clojurescript seriously, Clojure is the utopia.
      keymone on HN
  • StumpWM and Emacs

    From 1 comment
    • Oh, this is awesome! Between StumpWM, emacs & now nEXT, my entire desktop could be Lisp. Rather than using ECL to embed Lisp in C++, have you considered using an FFI to call out…
      zeveb on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/15418719)