Live data from Hacker News

Gosub – An open-source browser engine

github.com

131–140 of 173 posts

Re: Gosub – An open-source browser engine

#131

Earlier quoted context omitted.

The "optimised search and unlimited browsing" isn't really a statement, it is the expanded form of the acronym gosub. As I said, I don't really like it, but this is what we have now... :/ But I can definitely see where you are coming from.

if you don't like it. And people are also telling you they don't like it, then why do you insist on having it be an acronym?

The acronym was basically there from Day 1, I am not the Person who came up with it and I also wasn't there at Day 1.

Re: Gosub – An open-source browser engine

#132

Since this compiles to web assembly and is modular I wonder if this will use the wasm component model in the future. It would be interesting to be able to use pieces of this from other languages.

I highly doubt that. At least not in a native way. However, you could make an adapter from the native interface to wasm components. Would be interesting to look into!

Re: Gosub – An open-source browser engine

#133

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.

no, it probably wouldn't. if people are doing it for fun, they don't want to sit in meetings with strong personalities telling them how to do it. they enjoy coding, they enjoy thinking through interesting things, they don't enjoy taking orders and doing things a certain unfulfilling way just because somebody else prefers it that way. usually you have to pay them for putting up with that kind of thing.

Re: Gosub – An open-source browser engine

#135
post #96
post #81

Earlier quoted context omitted.

Isn't this how generative models are supposed to be used? Instead of generating a sub-par (no pun intended) logo myself, I get a model to build one for me. It is the same as using any computer software to achieve the goal - human is providing the inputs and hardware and software are generating the output.

> Isn't this how generative models are supposed to be used? Might be, or better just use the name as the logo. At this initial stage no one expects to see a good branding I guess. I've recently seen lots of low effort, sketchy looking projects using "sub-par" quality AI generated assets...and in turn when I see these kinds of images used in some project it really just shows off "put least effort to get things done" m…

"put least effort to get things done"

Some would say that's the mark of a great engineer.

Re: Gosub – An open-source browser engine

#137
post #124

Earlier quoted context omitted.

Instead of generating a sub-par (no pun intended) logo myself, you should PAY to someone to make a logo, instead of stealing work from other people.

Using AI to generate a logo is no more stealing than asking a designer to make a logo. A designer will pull ideas from prior art.

That said, can't AI iteratively edit a picture? Then it can accumulate lots of input and one couldn't say input was small.

Re: Gosub – An open-source browser engine

#138
post #81

Earlier quoted context omitted.

Isn't this how generative models are supposed to be used? Instead of generating a sub-par (no pun intended) logo myself, I get a model to build one for me. It is the same as using any computer software to achieve the goal - human is providing the inputs and hardware and software are generating the output.

Instead of generating a sub-par (no pun intended) logo myself, you should PAY to someone to make a logo, instead of stealing work from other people.

It's a glossy 3D emblem which aren't drawn today, it's like stealing sand from a desert.

Re: Gosub – An open-source browser engine

#139
post #33

As a BASIC programmer from the 1980s, thank you for that heart attack.

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 macros and inline assembly. I called it GOSUB/RETRACE.
Post reply on HN