The Hotdog web browser and browser engine • Hacker News Board

Re: The Hotdog web browser and browser engine

#101

Post by visiblink » Tue, Apr 20, 2021, 1:29 PM UTC

michalstanko wrote: post #88

Cthulhu_ wrote: post #64

Earlier quoted context omitted.

They break them on purpose so people will switch to Chrome. And the worst part is, there's no evidence (yet?) that there's malice behind it. Maybe we'll get a whistleblower at some point, but that'll only happen when their income no longer covers buying off their conscience.

What exactly is broken in Firefox on YouTube or Gmail? I'm not a heavy Firefox user, but when I try it every once in a while, I've never noticed anything broken on any of the Google's sites, even Maps and Docs worked just fine - but then, maybe I wasn't trying out some advanced features.

My wife and I have had a fanless PC hooked up to our TV since 2011.

Firefox is the only browser we use and we watch Youtube every day. If it broke, I'd know about it or hear about it.

It never breaks.

Re: The Hotdog web browser and browser engine

#102

Post by 5350-uiop-1130 » Tue, Apr 20, 2021, 1:31 PM UTC

i thought it was related to the old hotdog code editor. think i used that to learn html back in the early noughties.. better, simpler days - i really miss them.

Re: The Hotdog web browser and browser engine

#103

Post by girvo » Tue, Apr 20, 2021, 1:32 PM UTC

brabel wrote: post #43

userbinator wrote: post #10

It's great to see yet another attempt at writing a web browser --- and I say this as someone who has been (slowly) working on one myself. The browser is far from stable, spec-compliant, or even really useful, but, I'm slowly working on bringing more features and supporting more sites. When the specs are constantly churning in order to keep one gigantic company's browser an effective monopoly, maybe it isn't really th…

The idea of "minimal browsers" is a popular one and there are thriving communities based on this idea: Gopher is a dead simple text-based protocol: https://en.wikipedia.org/wiki/Gopher_(protocol) Project Gemini is a slightly more powerful protocol for the small web: https://gemini.circumlunar.space/ The tilde (~) community, which makes the small web social: https://tilde.club/ I recommend you have a look at James Tom…

I learned about Gopher at the same time I learned about the World Wide Web, in a kids book about Cyberspace in 1996 or so (I was a six year old!).

It’s been fun revisiting it as an adult!

Re: The Hotdog web browser and browser engine

#104

Post by commandlinefan » Tue, Apr 20, 2021, 1:47 PM UTC

2muchcoffeeman wrote: post #85

I’m a bit disappointed by the naming convention. There is mayo and sauce components. Mayo is not a typical hotdog condiment and sauce seems a bit generic. And then there is gg. What about sausage, sauerkraut or onion?

I beg to differ - my wife always puts mayo on hot dogs. She's Mexican, though - maybe it's a cultural thing?

Re: The Hotdog web browser and browser engine

#105

Post by xbar » Tue, Apr 20, 2021, 2:11 PM UTC

5350-uiop-1130 wrote: post #102

i thought it was related to the old hotdog code editor. think i used that to learn html back in the early noughties.. better, simpler days - i really miss them.

That's what I expected to find.

Re: The Hotdog web browser and browser engine

#106

Post by marcthe12 » Tue, Apr 20, 2021, 2:13 PM UTC

ktpsns wrote: post #100

marcthe12 wrote: post #50

Earlier quoted context omitted.

First Debian is a distro composed of several third party software. The closest equivalent to browsers in scope in Xorg and that has gone in maintaince for being unmaintainable. Web browsers could be simplified if designed differently(internal architecture). We browser are monolithic programs but with stuff like nodejs, gjs, web view, pwa, etc. , Parts of browser must really become system library (that has some stabil…

Interesting idea, but what would be the advantage of having, for instance, the javascript engine running as a system daemon? This reminds me of Windows Script Host, which was some similar idea but didn't make it. What we see instead are JITs or VMs such as the JVM, node or any other language (such as raku or julia) which just work standalone, in the same way as a browser does.

Is engine prob is better of a s a system lib. The Daemon are for stuff like service workers from pwa, they are already boardline apps(notifications for example). The biggest advantage of the system lib style is you can effectively share with native program. It also standard cross platform. A not so bloated nodejs and electron setup.

Re: The Hotdog web browser and browser engine

#107

Post by bmn__ » Tue, Apr 20, 2021, 2:28 PM UTC

michalstanko wrote: post #88

Cthulhu_ wrote: post #64

Earlier quoted context omitted.

They break them on purpose so people will switch to Chrome. And the worst part is, there's no evidence (yet?) that there's malice behind it. Maybe we'll get a whistleblower at some point, but that'll only happen when their income no longer covers buying off their conscience.

What exactly is broken in Firefox on YouTube or Gmail? I'm not a heavy Firefox user, but when I try it every once in a while, I've never noticed anything broken on any of the Google's sites, even Maps and Docs worked just fine - but then, maybe I wasn't trying out some advanced features.

> What exactly is broken in Firefox on YouTube or Gmail?

Performance. That makes the sabotage so insidious!

https://tech.co/news/google-slowed-youtube-firefox-edge-2019...

https://addons.mozilla.org/addon/disable-polymer-youtube

Re: The Hotdog web browser and browser engine

#108

Post by losvedir » Tue, Apr 20, 2021, 2:38 PM UTC

swsieber wrote: post #29

creshal wrote: post #24

Earlier quoted context omitted.

> When the specs are constantly churning in order to keep one gigantic company's browser an effective monopoly, maybe it isn't really that important to follow them so closely... The notion breaks as soon as your users want to use youtube or gmail, which for some mysterious reason keep insisting on using all these useless "standards" even though they have no benefit to the user.

Youtube and gmail will mysteriously break for people on Firefox too, so it's not that much worse. /sarcasm (sort of...)

Regular Firefox user here with a YouTube Premium account. I use it all the time and have never had any issues.

Re: The Hotdog web browser and browser engine

#109

Post by damagednoob » Tue, Apr 20, 2021, 2:40 PM UTC

als0 wrote: post #74

> ketchup (html parser and DOM Tree builder) mayo (css parser and Render Tree builder) mustard (UI Toolkit, events and OpenGL) sauce (requests, cache and filesystem) bun (css layout calculator) Off topic, but I've encountered some more serious projects that used strange nouns to name their components. I've never figured out why, but it usually results in me spending more time cross-checking what each component does.…

Engineers think they are being cute when they do this. In reality it hampers new devs because you can't just look at a component and have an idea of what it's doing. I've been on projects like this and after a year I was still second-guessing myself.

Re: The Hotdog web browser and browser engine

#110

Post by throwaway823882 » Tue, Apr 20, 2021, 3:14 PM UTC

2muchcoffeeman wrote: post #85

I’m a bit disappointed by the naming convention. There is mayo and sauce components. Mayo is not a typical hotdog condiment and sauce seems a bit generic. And then there is gg. What about sausage, sauerkraut or onion?

Dill pickle, tomato, peppers, relish.