It's true that the complexity of these kinda projects are enormous, but considering chrome/webkit's monopoly in the browser space, I feel we should always welcome and appreciate alternative efforts...regardless of the project's outcome. P.S. the website and the probably AI generated logo is giving a sketchy vibe about the project :)
Gosub – An open-source browser engine
81–90 of 173 posts
Re: Gosub – An open-source browser engine
#82Is anyone working on something like that?
Re: Gosub – An open-source browser engine
#83It's true that the complexity of these kinda projects are enormous, but considering chrome/webkit's monopoly in the browser space, I feel we should always welcome and appreciate alternative efforts...regardless of the project's outcome. P.S. the website and the probably AI generated logo is giving a sketchy vibe about the project :)
>P.S. the website and the probably AI generated logo is giving a sketchy vibe about the project :) certainly some reasoning would be more constructive than a smiley face, because I looked at the website, I looked at the logo[0] - I didn't share the same feeling. Certainly it could be AI generated, but why 'sketchy'? Is it something to do with your own personal feelings on AI use, or just the aesthetic in general? I g…
I already gave the reasons there.
> I didn't share the same feeling.
Just a personal opinion.
Re: Gosub – An open-source browser engine
#84Re: Gosub – An open-source browser engine
#85Earlier quoted context omitted.
> develop a fully compatible browser engine Do we need more "fully compatible" engines? I could imagine there are use cases for browser engines that work with just parts of the specification, particularly the most common ones used in the wild.
Just as a data point, the YouTube app on most TVs and devices is a stripped down browser only supporting exactly the HTML/CSS/JS needed to run the big picture client. By tighter integration with the final product, the browser can provide specialized elements or APIs to simplify the actual application code. I think it's used a few other places as well.
Even the old pre-tvOS Apple TV apps were kinda web apps - XML and JavaScript delivered over HTTP
Re: Gosub – An open-source browser engine
#86Earlier quoted context omitted.
No, the website isn't AI generated. There might be some parts of it, though, like general structure of the website and structure of texts. Yes, the initial logo design was generated by AI, however the current logo was made by a designer from the AI's draft. I don't know if it is a compliment that my website design skills match the ones of AI or if it is more an insult
> I don't know if it is a compliment that my website design skills match the ones of AI or if it is more an insult Neither, it has nothing to do with design. I just wanted to point out that putting an AI generated logo, and writing vague statements like "optimised search and unlimited browsing" seems unprofessional to me.
Re: Gosub – An open-source browser engine
#87Earlier quoted context omitted.
The byte stream is one of the first components that was written. Probably It wouldn't be written nowadays. The browser is quite modular, so in the end you can completely out out of that system.
That’s good to hear. I’m excited to see you’ve got a good html parser. That’s worth a lot just by itself.
Re: Gosub – An open-source browser engine
#88Earlier quoted context omitted.
"GOSUB" is the syntax used to call subroutines (functions) in BASIC: http://retro-basic.com/manual/GOSUB.html
Thanks for the pointer. And it makes it doubly confusing. Doesn't a reference to an obsolete, pre-modern language tarnish the reputation of Rust? Doesn't the creator of this project fear lawsuits from the legal team at The Basic Foundation?
Re: Gosub – An open-source browser engine
#89I was hoping for a small embeddable engine to finally replace Electron. The build on Windows ends up being 55MB, not too bad but still too large for simple apps. Is anyone working on something like that?
Re: Gosub – An open-source browser engine
#90I was hoping for a small embeddable engine to finally replace Electron. The build on Windows ends up being 55MB, not too bad but still too large for simple apps. Is anyone working on something like that?
Lateron, we might have some compile time flags to reduce memory usage in cost of a bit of speed. Most Electron apps don't require that big oomf performance on the startup, since everything is locally and can be cached in a better way.