[HN Gopher] Nyxt 3 Pre-release 1 (a Lisp powered web browser)
       ___________________________________________________________________
        
       Nyxt 3 Pre-release 1 (a Lisp powered web browser)
        
       Author : arthureroberer
       Score  : 142 points
       Date   : 2022-07-14 15:37 UTC (7 hours ago)
        
 (HTM) web link (nyxt.atlas.engineer)
 (TXT) w3m dump (nyxt.atlas.engineer)
        
       | yewenjie wrote:
       | Is there anybody who uses more than one browser as daily drivers
       | simultaneously? What's your workflow like? I have tried to give
       | Nyxt multiple tries but had to give up cause some things just
       | don't work and had to use Firefox for those.
        
         | SkyMarshal wrote:
         | Yeah, I alternate between Brave, Chromium, Firefox, and Opera
         | (and Safari on Mac). Firefox any time I want to try to download
         | some media like YouTube vids that are difficult or impossible
         | in other browsers. Brave, Chromium, and Opera are all Chromium
         | under the hood so they're pretty interchangeable. And Safari on
         | my Mac laptop for optimal battery life.
        
         | t-3 wrote:
         | I use several different browsers. I have one completely locked-
         | down (no images, js, cookies, etc), exceptions by whitelist-
         | only + host blocking. That one is used for most of my daily
         | browsing. I use a separate browser for anything that requires
         | webapps or cookies, and an entirely different computer for
         | anything financial or important. The only problem I have is
         | occasionally being frustrated by how bad the Chrome and Firefox
         | UIs are compared to literally anything else, or even themselves
         | a few years ago.
        
         | hosh wrote:
         | I use Firefox with containers on my laptop for my day-to-day,
         | and occasionally use Chrome for dev, testing, or if I just
         | can't load a page right.
        
         | edent wrote:
         | Yes. I use Chrome to access my work Gmail and Firefox for
         | everything else.
         | 
         | It's a good way to keep things separated. And means I'm
         | unlikely to accidentally share my YouTube viewing when I share
         | a tab in a Google Meet.
        
         | dmix wrote:
         | Firefox for personal, no extension Chromium for dev (besides
         | cookie editor, vue tools, and JSON prettifier)
         | 
         | (devtools > ff tools)
        
         | colechristensen wrote:
         | I have really aggressive privacy mechanisms on Firefox and when
         | they break something I need to do I switch to Chrome to do that
         | one thing. (It seems to be mostly a certain kind of oauth flow
         | that gets broken, I'm not curious enough to figure it out
         | because I couldn't change it anyway)
        
         | mark_l_watson wrote:
         | The last three companies (including where I am now) use Google
         | GSuite so I use Chrome on my MacBook for work. I otherwise use
         | Safari. This makes sense to me.
         | 
         | BTW, I used to donate to the Nyxt project but I started having
         | major difficulties getting it installed (perhaps this is when I
         | did the M1 transition?).
        
         | semi-extrinsic wrote:
         | Corpo intranet amd a very few other sites don't work properly
         | on Firefox (even more on Android FF), so I occasionally use
         | Chrome to get around that.
        
         | nibbleshifter wrote:
         | Yeah.
         | 
         | Brave for general browsing/watching videos, Chrome for work
         | apps, Firefox w/ FoxyProxy for some stuff at work only
         | reachable via SSH tunnel, and whatever the embedded Chromium
         | that ships with BurpSuite is for testing webshits.
         | 
         | Each will tend to have a fuckheap of tabs open too.
        
         | yashasolutions wrote:
         | eww and FF daily. I wish Nyxt had less critical issues, I would
         | 100% use it.
        
         | Mikeb85 wrote:
         | I use Chrome for anything Google and streaming
         | sites/Chromecast, Firefox for everything dev-related (and of
         | course test on both).
        
         | colordrops wrote:
         | On my work laptop I use chrome for corp stuff and development,
         | firefox for personal usage, and brave for media streaming.
        
           | maleldil wrote:
           | Why Brave for streaming?
        
         | halostatue wrote:
         | The use of tools like Finicky
         | (https://github.com/johnste/finicky) have made it pretty easy
         | for me segregate certain workloads to certain browsers (as long
         | as the links are opened from _outside_ of the current browser).
         | 
         | Safari is my daily driver, but I _only_ take Google Meet
         | meetings in Chrome and Teams meetings in Edge. I've also forced
         | certain JIRA URLs to different browsers (Firefox or Edge,
         | depending), because I have to be logged in as particular users
         | for them.
         | 
         | I rarely use other browsers for anything else, but will
         | occasionally test things in them--but using the separate
         | browsers has been really good for segregating certain classes
         | of work.
        
           | WalterGR wrote:
           | > as long as the links are opened from outside of the current
           | browser
           | 
           | How do you invoke Finicky, then?
        
             | donjh wrote:
             | Finicky is set as your system default browser and opens the
             | appropriate browser based on the URL.
        
       | pmoriarty wrote:
       | Being able to customize my browser in lisp would be great, before
       | I switch I'd need this browser to have something like:
       | 
       | - unlock Origin (for feature rich and sophisticated ad blocking)
       | 
       | - uMatrix (per-domain and subdomain Javascript blocking)
       | 
       | - NoScript (more Javascript exploit protection)
       | 
       | - Pentadactyl and/or Evil (vim-like modal browsing)
       | 
       | Lack of the first three was why I never switched to qutebrowser,
       | despite it having a nice Pentadactyl-like UI.
        
         | contravariant wrote:
         | Is there any need for NoSript with uMatrix and uBlock Origin?
        
         | jarbus wrote:
         | You can disable javascript in qutebrowser, and the default
         | adblocker works pretty good if you remember to update your
         | sources, but I agree that it's not like ublock Origin
        
         | usrn wrote:
         | By default it more or less has everything besides ublock (which
         | is why I haven't switched yet either.)
        
         | tremon wrote:
         | Yes, same here. I want to want this, but the lack of third-
         | party resource control (I'm a big uMatrix user) means I don't
         | trust most browsers, and I don't want to resort to running my
         | browser in a container.
         | 
         | I thought that earlier versions (when it was still called Next)
         | did support keyboard-based browsing, but maybe I'm
         | misremembering (I toyed with uzbl too). The first thing I'd
         | want for keyboard-based navigation would be an easily
         | accessible cheat sheet.
        
           | Jtsummers wrote:
           | https://nyxt.atlas.engineer/documentation
           | 
           | It does support keyboard-based navigation, and you can define
           | your own bindings to any of the functions so you can alter
           | the defaults or extend them to your own purposes.
           | 
           | Scroll down to "Visual mode" for their take on vim-like
           | bindings.
        
       | brabel wrote:
       | Would be nice if this was embeddable inside (and integrated with)
       | emacs.
        
         | dannyobrien wrote:
         | There's a bunch of support already for controlling the browser
         | via a SWANK/SLY repl, and also remotely run emacs functions
         | from Nyxt.
         | 
         | https://nyxt.atlas.engineer/article/emacs-hacks.org
         | 
         | (I guess it would be embeddable using xwidget, but I haven't
         | tried that).
        
       | jll29 wrote:
       | It looks a bit like Emacs, so I intuitively pressed CTRL x 0 to
       | close a window.
        
       | bgorman wrote:
       | Is WebKit stable on Linux? Gnome Web frequently crashes for me,
       | but I would love to try a stable WebKit based browser on Linux.
        
       | low_tech_punk wrote:
       | I'm down if this supports a Chromium backend.
       | 
       | Also, how does developer experience look like, e.g. DOM
       | inspector, source code debugger?
       | 
       | My job requires heavy debugging so it cannot be my daily driver
       | unless there is comprehensive developer tools.
        
       | [deleted]
        
       | leephillips wrote:
       | I'd love to use Nyxt, but it doesn't work. It doesn't work
       | because, despite claims to be engine-agnostic, in practice it can
       | only be used with webkitGTK. WebkitGTK displays (CSS and HTML
       | validating) pages with loads of rendering errors. I've tried it
       | on pages that look identical and are rendered correctly in
       | Firefox, Chrome (and all Blink browsers), and Safari, but do not
       | render correctly in Nyxt. The incorrect rendering is reproduced
       | exactly with Epiphany, the official Gnome browser that uses the
       | same engine--so I know that the problem is with webkitGTK. If
       | anyone can explain how to unlock the supposed engine-agnosticism
       | of Nyxt so that I can try it with Blink, I would like
       | instructions.
        
         | low_tech_punk wrote:
         | How did Tauri (Rust) solves the rendering engine problem? Maybe
         | Nyxt can borrow some of its magic.
        
           | darthrupert wrote:
           | Did it? Perhaps it's easier to support crossplatform things
           | if you can control which features of all the engines are
           | being used.
        
           | mattlondon wrote:
           | I think that it just uses the system webview, whatever that
           | is. I don't think it offers "dynamic" switching between
           | multiple implementations.onnthe same platform.
        
         | ithrow wrote:
         | Interesting, why does webkitgtk messes with webkit rendering?
        
         | alschwalm wrote:
         | I've also hit this issue. About a year ago I made an effort to
         | use blink, but after a bit of work I recall essentially
         | discovering that any support was effectively abandoned. I wish
         | they would remove the note in the FAQ about supporting multiple
         | engines, as it doesn't seem to be the case.
        
           | leephillips wrote:
           | At most it's a description of an aspect of the project's
           | internal architecture. It means absolutely nothing to the end
           | user.
           | 
           | I believe that the Nyxt website should have a big red banner
           | warning people that, because it uses a rendering engine that
           | is not conformant and, I suppose, is a work in progress, it
           | can't actually serve as a practical web browser. This would
           | save people from wasting time installing it only to find out
           | that it doesn't work. And remove the misleading comments
           | about it being engine-agnostic. I really don't understand
           | what they hope to accomplish by forcing people to discover
           | the true nature of their project the hard way, but it leaves
           | a bad taste in my mouth. The same goes for Suckless' surf
           | browser and others. For their part, the wekitGTK website
           | falsely claims that their engine is "a full-featured port of
           | the WebKit rendering engine". As mentioned in another
           | comment, these rendering errors do not appear in Safari,
           | which uses WebKit.
        
         | tikhonj wrote:
         | I've been playing a bit with WebkitGTK for my own development
         | and found the same thing--I was learning how to use SVG and was
         | getting really confused about how transform-origin was supposed
         | to work... then I tried the same SVG in Firefox and Chrome and
         | realized that my _understanding_ was correct and it was
         | WebkitGTK that, for whatever reason, didn 't handle it
         | correctly. Even over a relatively short time I ran into a
         | _number_ of CSS, SVG and DOM manipulation behavior that
         | WebkitGTK seems to handle incorrectly.
        
         | jmercouris wrote:
         | Thank you for your feedback. You're 100% right. The framework
         | _is in place_ , however the implementation is not! We wanted to
         | get Nyxt to a level of feature sophistication before focusing
         | on supporting (not just prototyping) two renderers as it can
         | slow down progress!
         | 
         | With 3.0.0 on the horizon, now is an ideal time. Once again,
         | sorry about the issues you've had, we're doing our best!
        
       | tannhaeuser wrote:
       | Interesting observations from the comments in this thread so far:
       | 
       | - Nyxt merely integrates WebKit so isn't actually a browser,
       | where a browser consists of an HTML and CSS parsing and rendering
       | engine, plus, optionally, Js; this is disappointing insofar as
       | the enormous HTML and CSS tower-of-Babel specs produced over the
       | last 20+ years _still_ are unproven by a from-scratch
       | implementation
       | 
       | - professional web users other than on Mac OS use Chrome for
       | webapps and FF for actual web sites (presumably b/c privacy
       | features), giving rise to the perspective of separating-out
       | extant web apps into containerized Electron apps in the future
       | (where those aren't already eg MS Teams et al), so by chance we
       | can get rid of the Js ballast and recent CSS atrocities and
       | return to a healthy competitive browser landscape.
        
       ___________________________________________________________________
       (page generated 2022-07-14 23:00 UTC)