This is so cool! I'm someone for whom emacs has steadily expanded its role in my computing life, but who will never adopt a text-based browser as a daily driver.
Looking forward to the stable 4.0 release when I'll be prepared to use Nyxt and hope it can replace Firefox / Chromium as much as possible for me.
smartmic 6 hours ago [-]
I also tried Nyxt, but I never stuck with it. I believe there are different UI contexts depending on the goal. For example, browsing the web is a different task and experience than editing text. That's why it comes naturally to me to use a mouse- and keyboard-driven application, Firefox in my case, for browsing and Emacs for anything text-related.
In other words, using the purely text-driven Emacs interface to browse multimedia web pages does not feel natural to me.
izhak 8 hours ago [-]
The guys behind have decent lisp and hacking skills and zero to none product thinking. The project is around for a while but the complete lack of ability to think about users or from the users perpective makes it a dead end
Personally, I'll use and donate to it once it can run uBlock, not before.
jnpnj 7 hours ago [-]
I think there's a lack of understanding. If Nyxt is trying to be the emacs of web browsers, it's very much removed from the "product mindset", it's more about somehow coherent capabilities than a product with market and users. Kinda like linux.
mickael-kerjean 7 hours ago [-]
This kind of articles / project is exactly why I love HN. I am not much a marketing person but have enough basics to understand that if something does not appeal to me, that's because I'm not the target and as a emacs fanboy this kind of tools 100% appeal to me.
skeezyboy 2 hours ago [-]
i agree but it hasnt stopped emacs or linux for that matter
anthk 6 hours ago [-]
These are not the target for Nyxt. Think about Emacs. Or, for vi/nvi/vim people, Luakit/Vimb.
bowsamic 8 hours ago [-]
Can you elaborate? In what ways have they failed their users?
deadlypointer 7 hours ago [-]
How does it stack up in terms of security? To me the idea of hackability is a bit conflicting with all the security features of modern browsers. The web is basically the main attack surface today, so I wouldn't use a niche browser engine.
hnlmorg 5 hours ago [-]
That’s a good question to ask.
In terms of the browser itself, it’s not niche browser engine. The engine is Chromium (via Electron) by default, though WebKit is also supported as a compile time option.
So that should bring the same safeguards in terms of sandboxing from drive-by attacks.
Then risk here is code that has execution permissions outside of that sandbox. But here, that’s no different to running any kind of untrusted code (eg shell script, ELF, etc) on your local machine.
tetris11 6 hours ago [-]
I would use it if it supported ublock origin
camdroidw 6 hours ago [-]
And umatrix
ironmagma 7 hours ago [-]
So now we have Next, Nuxt, and Nyxt. What’s noxt?
lelanthran 5 hours ago [-]
> So now we have Next, Nuxt, and Nyxt. What’s noxt?
Well there's still two more vowels[1], so at a guess ... Naxt and Nixt?
--------------------------------
[1] I've never understood why 'Y' is not a vowel.
benchly 4 hours ago [-]
We were taught in grade school that the vowels were "A, E, I, O, U....and sometimes Y" without any real explanation. I count that as our first lesson about the convoluted complexities of the English language.
skeezyboy 2 hours ago [-]
>I count that as our first lesson about the convoluted complexities of the English language.
I dare say its made up as it goes along
smartmic 5 hours ago [-]
Nzxt.
anthk 6 hours ago [-]
Ironically the Guix build it's broken.
iLemming 8 hours ago [-]
Does it finally work on Macs without weird rituals? I love the idea of using only Linux, but I'm too stupid to deserve an employer who'd let me live my dreams. I'm just happy I'm not forced to use Windows.
In other words, using the purely text-driven Emacs interface to browse multimedia web pages does not feel natural to me.
Personally, I'll use and donate to it once it can run uBlock, not before.
In terms of the browser itself, it’s not niche browser engine. The engine is Chromium (via Electron) by default, though WebKit is also supported as a compile time option.
So that should bring the same safeguards in terms of sandboxing from drive-by attacks.
Then risk here is code that has execution permissions outside of that sandbox. But here, that’s no different to running any kind of untrusted code (eg shell script, ELF, etc) on your local machine.
Well there's still two more vowels[1], so at a guess ... Naxt and Nixt?
--------------------------------
[1] I've never understood why 'Y' is not a vowel.
I dare say its made up as it goes along