Earlier quoted context omitted.
Wow, that thread is horrible. It's just flamebait from both sides. From metroholografix: > I fear that webkit can not be salvaged > How about all the huge OSX vulnerabilities that have been discovered? > You are so out of touch with the state of cybersecurity that it's terrifying. Not only that, but you insist on this nonsensical adversarial attitude towards me when I'm spending my personal time trying to inform you.…
Hey there. Can you point at something in my reddit posts that is inaccurate or plain wrong? I agree that my tone could be better but notice the difference between my first post to him and my subsequent replies. It's hard to maintain a civil attitude when I am immediately accused of being a shill. Nevertheless, I think I have provided enough useful information to him. Notice how he responds each time. You wrote that y…
Show HN: Next Browser native on Linux
101–110 of 117 posts
Re: Show HN: Next Browser native on Linux
#102Earlier quoted context omitted.
Hey there. Can you point at something in my reddit posts that is inaccurate or plain wrong? I agree that my tone could be better but notice the difference between my first post to him and my subsequent replies. It's hard to maintain a civil attitude when I am immediately accused of being a shill. Nevertheless, I think I have provided enough useful information to him. Notice how he responds each time. You wrote that y…
My impression was that with the switch from (UI)Webview to WKWebKit the webview is put in a sandbox automatically. At least the rendering is now out-of-process. Do you know anything about that?
Re: Show HN: Next Browser native on Linux
#103Very nice, we need more of that. There's also qutebrowser [1], but none of these are usable without a proper adblocker implementation. [1] https://qutebrowser.org
Qupzilla also was a nice one until they killed it and migrated the code to KDE (triple facepalm).
Re: Show HN: Next Browser native on Linux
#104A lot of the focus seems to be on making the browser easily extendable which is great, but can extensions interact with/modify the contents of web pages rather than the browser itself? I am not seeing it in a quick browse through the docs, and that is kind of the main point of most browser extensions.
to answer your question, yes
Re: Show HN: Next Browser native on Linux
#105It seems like every time a new browser comes out, the immediate question is, "what does the extension ecosystem look like?" Since Next's website says that its goal isn't to be a massively popular, omnipresent browser, the answer to that question is probably always going to be "worse than Chrome/Firefox." Even if I'm writing my own extensions to fill in that gap, I'm fine dipping into Lisp for lower-level functionality or to customize the browser itself, but for higher-level stuff I'd like to see browsers use existing standards rather than have 3 different APIs to do roughly the same things.
As a user, it's very tough for me to justify doing any browsing, even just experimentally, outside of Firefox where I have UMatrix and Ublock. And while I'm sure you'll put in a great adblocker eventually, it probably won't be as good as UMatrix and Ublock, because the stuff you're building won't have the same level of widespread scrutiny that those extensions get.
Nowadays I feel more and more like most browser extensions ought to be written in a way that is roughly as cross-platform as the web itself.
Re: Show HN: Next Browser native on Linux
#106Earlier quoted context omitted.
Hey there. Can you point at something in my reddit posts that is inaccurate or plain wrong? I agree that my tone could be better but notice the difference between my first post to him and my subsequent replies. It's hard to maintain a civil attitude when I am immediately accused of being a shill. Nevertheless, I think I have provided enough useful information to him. Notice how he responds each time. You wrote that y…
My impression was that with the switch from (UI)Webview to WKWebKit the webview is put in a sandbox automatically. At least the rendering is now out-of-process. Do you know anything about that?
Re: Show HN: Next Browser native on Linux
#107It seems pretty interesting, especially the mouseless part. I tried [Vimperator]( http://vimperator.org/ ) on Firefox for a while, but it seems the web was really hard to use without a mouse. I might give it a try again
Re: Show HN: Next Browser native on Linux
#108What if a browser was built like Emacs is built? With low-level rendering core exposing almost everything to scripting in Lisp, and the entire UX written in Lisp, fully customizable? It appears that Next goes in this direction. I don't know if gtk-webkit allows to script it very deeply, e.g. enough to expose DOM and write extensions in Lisp. It would also be great to have something like the Emacs's customization fram…
Ever since I started using Org Mode in the Android app "Orgzly" and in Visual Studio Code, I've been wishing a lot more was written so it could take advantage of Lisp. Mostly because I'm selfish and want more of Org Mode's features supported in more places, but also I'm super impressed by Emacs' scripting/control abilities. I'd also like to see vim with a mode specifically for Org Mode. But that sort of idea is very…
Re: Show HN: Next Browser native on Linux
#109I see no one mentioned luakit ( https://luakit.github.io/ ). From the site: "Luakit is a highly configurable browser framework based on the WebKit web content engine and the GTK+ toolkit. It is very fast, extensible with Lua, and licensed under the GNU GPLv3 license. It is primarily targeted at power users, developers and anyone who wants to have fine-grained control over their web browser’s behaviour and interface."
Re: Show HN: Next Browser native on Linux
#110I see complaining about GTK on your first link - have you heard of Qt?