No adblock is a show stopper for me, but they have a campaign on Indie Go Go with adblocking as one of the goals https://github.com/atlas-engineer/next/issues/32 https://www.indiegogo.com/projects/next-browser-nix-support#...
I’ve been going pretty strong with a host based blocker. I mention this in case you really want to use Next and are willing to try a different blocking approach :)
I know it’s not as comprehensive as extension based blocking, but it seems solid.
No adblock is a show stopper for me, but they have a campaign on Indie Go Go with adblocking as one of the goals https://github.com/atlas-engineer/next/issues/32 https://www.indiegogo.com/projects/next-browser-nix-support#...
I’ve been going pretty strong with a host based blocker. I mention this in case you really want to use Next and are willing to try a different blocking approach :) I know it’s not as comprehensive as extension based blocking, but it seems solid.
We've been leaning towards using Webkit's integrated content blocking rules, but we weren't sure how effective it would be, thanks for the feedback!
Well, the Lisp part is for the reprogrammability of it all, the inspectability. You can on-the-fly edit a compiled version of Next, which is pretty cool I think!
Isn't there some popular language with the same capabilities? Is it a Lisp speciality?
Nowadays it's usually called 'hot reload' and everybody hype about how cool is that in React Native and Flutter.
A 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.
I like the idea but it doesn't go anywhere near far enough.
I feel like the web has become that "City of Destruction" that is talked about in "Pilgrim's Progress"; something like 95% of the bytes transferred are just junk.
I am not at all interested in "seeing the content the way the created intended it", I really would rather decompose it into a semantic graph and then put it together to show me what is relevant.
That means no Javascript. If I have to have a malware player so I can use the junkware of the day I'll use Chrome.
Hi there, bit of a lisp fanatic so excited to see this. Just some questions:
I'm not very knowledgeable about browser architecture, and my search foo is failing at a first try, could you provide a couple of links on what you mean by "controller"?
My second question is probably dependent on the first, but:
are you worried that using xml-rpc is going to be a bottleneck?
last question: I'm a little worried about the note on the installation page to modify the kernel for a userland app to change root, could you reassure me that I'm just an ignorant fool that simply doesn't understand whats going on here?
these might seem adversarial, but I promise, I'm actually really excited for this, I just want to understand whats happening. I'm grabbing a copy of the source and will definitely be sifting through it over the holidays, good luck!
Congratulations! It won’t be ready for primetime until there’s a good adblocker — but now that it runs on Linux, folks like me can work on an adblocker for it.
I’m really excited for you & for your browser. I was a contributor to your Indiegogo campaign & was really bummed to see it fall short of the mark (although no doubt nowhere near as bummed as you were); it’s great to see that you’ve managed to move ahead nonetheless.
I like the idea but it doesn't go anywhere near far enough. I feel like the web has become that "City of Destruction" that is talked about in "Pilgrim's Progress"; something like 95% of the bytes transferred are just junk. I am not at all interested in "seeing the content the way the created intended it", I really would rather decompose it into a semantic graph and then put it together to show me what is relevant. Th…
There are basically two ways to do that. Decompose final page, that is composed usually by internal Javascript these days. Or decompose the page structure, which is usually a bunch of API calls, requests, and some data transformation. The former is simpler, the latter is good potential use case for programmable browsers like Next.
A 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
Great, thanks. My Lisp skills are very rusty but I think I'll give this a shot.