Live data from Hacker News

Gosub – An open-source browser engine

github.com

151–160 of 173 posts

Re: Gosub – An open-source browser engine

#151
post #73

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 :)

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 love the logo and I love the name. Sounds like a polarizing logo; that's a good thing. I remember having similar thoughts to this other person when Google first launched their search engine with their "ugly rainbow" logo. You're good.

Re: Gosub – An open-source browser engine

#152

Earlier quoted context omitted.

They say BASIC programmers never die, the just GOSUB and never RETURN.

Trivia: at least in some BASICs (QBasic, QuickBasic, FreeBASIC) it's not necessary for every GOSUB to be matched with a RETURN, since the GOSUB is a single 'call' instruction that pushes onto the stack (and RETURN is a single 'ret' instruction, hence GOSUB-RETURN is highly efficient!) so it gets removed when you exit the function if you didn't RETURN, like alloca(). I actually re-implemented GOSUB this way using macr…

In Wang BASIC, there was the "RETURN CLEAR" statement which cleared the stack up to and including the most recent GOSUB call frame. This includes any FOR loop frames that were push on the stack in the subroutine before the GOSUB. This was intended to be used for handling error conditions.

https://www.wang2200.org/basic_comparison.html#retclear

Re: Gosub – An open-source browser engine

#154

I 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?

The smallest app built with Tauri is 500 KB.

[1]: https://tauri.app [2]: https://syntax.fm/show/821/is-tauri-the-electron-killer/tran...

Re: Gosub – An open-source browser engine

#155
post #126

Earlier quoted context omitted.

Because Servo is run by others with a different agenda that came from a billion dollar company that gets hundreds of millions from a trillion dollar company and they decided to dropped it. The political effort to get to a place where you can shape the project is a huge mountain to climb and unlikely. Starting your own project you can set the agenda and pace and truly create your vision. The people who want to do the…

Why not fork it then? You don't need to be able to set the agenda for a project if you just fork it and rename it: you can now set the agenda for your fork and ignore the other project, while not having to spend time reinventing the wheel.

As if that wouldn't end up with the same style of "why don't you just" comments?

Re: Gosub – An open-source browser engine

#157

Earlier quoted context omitted.

Agreed. Honestly, wasn't the whole purpose of open source to be kinda free for all ( the followers, the inventors, the grinders... you name it ). Why does everything I read lately start with a 'should'. I am making a mental note to self.

Try replacing "should" with "wouldn't it make more of a positive change in the world if" and see how that leaves you feeling.

Wouldn't it make more of a positive change in the world if you went and did something useful instead of posting snarky comments on Hacker News?

Re: Gosub – An open-source browser engine

#158

I 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?

Yes, we're working on that over at https://github.com/DioxusLabs/blitz (alpha release imminent). Our TodoMVC example is current ~20mb with a standard release builds, but comes down to 7.2mb with some compiler flags like -Oz and LTO enabled (these numbers of from macOS). And we plan to allow fine grained configuration of the feature set, so if you don't need certain image formats or layout algorithms or networking sup…

Ohhhh...this is so awesome. Fits the most common app usecase for plain HTML+CSS rendering library and not a humongous browser for developing offline apps and its terrific that something like blitz exists.

Re: Gosub – An open-source browser engine

#159

Earlier quoted context omitted.

There are long lasting bridges made of stone, concrete and in the right climates, even wood. Not to mention rope when it suits the purpose. Each material has its own qualities, which means its own pros and cons in a given context. This naive belief that there will be one language to rule them all (and is name is ignores history and the world outside of programming in a rather silly way.

> There are long lasting bridges made of stone, concrete and in the right climates, even wood. Not to mention rope when it suits the purpose. I'd be fine with someone building a new browser out of stone, concrete, wood, or even rope. Just don't build it out of C/C++ because those languages aren't memory safe.

Rust is a risk-reduction strategy. It is not a risk-elimination strategy.

There are risk-reduction strategies one can follow with C++, which offer some fraction of the reduction that Rust does (opinions vary on the value of the fraction). Rust enforces risk-reduction strategies, which in some contexts may be of value all by itself.

Language choice does not eliminate risks in software.

Re: Gosub – An open-source browser engine

#160

Earlier quoted context omitted.

There are long lasting bridges made of stone, concrete and in the right climates, even wood. Not to mention rope when it suits the purpose. Each material has its own qualities, which means its own pros and cons in a given context. This naive belief that there will be one language to rule them all (and is name is ignores history and the world outside of programming in a rather silly way.

Nobody is saying that. But to continue your analogy, do you not think that in a world where all the bridges are made of wood it would be notable to say that a new bridge is made of steel? Of course there are impressive projects made with C. But we generally don't build large bridges out of wood anymore do we.

> do you not think that in a world where all the bridges are made of wood it would be notable to say that a new bridge is made of steel?

Notable, sure. But it could turn out to be Tacoma Narrows bridge.

We never did build large bridges out of wood, I think. For the right context, wood is still a preferred material for some bridges.

Post reply on HN