The Hotdog web browser and browser engine • Hacker News Board

Re: The Hotdog web browser and browser engine

#111

Post by bntyhntr » Tue, Apr 20, 2021, 3:23 PM UTC

ktpsns wrote: post #98

tediousdemise wrote: post #78

Love the food-centric naming conventions for all the components. Can we take a moment to appreciate themed naming conventions in software ecosystems? It’s a great conversation starter, and it’s something that will keep us smiling even when things get serious.

I also like it, despite I have to admit: As a vegan person, I would not like to contribute to software parts named after sausage ;-)

I am not a vegan, but I have had vegan (not imitation meat!) sausages that were absolutely delicious! But I admit the likely connotation is pretty meaty

Re: The Hotdog web browser and browser engine

#112

Post by heterodoxxed » Tue, Apr 20, 2021, 3:48 PM UTC

NeoVeles wrote: post #60

jan_Inkepa wrote: post #55

Earlier quoted context omitted.

> Maybe if enough of these "minimal browsers" show up, people might even realise that basic HTML and CSS is quite sufficient for a lot of things and start creating simpler, more efficient sites, thus dissolving the monopoly. I feel like some initiative to establish a super 'light' version of the html/css specs might be a very good thing...browsers are so far gone out of the hands of individual coders or even small te…

This is something I had been pondering. Rather than making a new 'standard' based on a new technology and thus expanding the standards base with complexity, we can go the other way. Make a specification based on old tried and tested tech. Thinking something like a set HTML/CSS specs that can be implemented fairly easily. It is a spec that is essentially something a website can be built to knowing that end browsers/us…

| a set HTML/CSS specs that can be implemented fairly easily

That could then be heavily optimized and used for cross-platform apps instead of the bloated, kitchen sink approach of Electron.

Re: The Hotdog web browser and browser engine

#113

Post by rekabis » Tue, Apr 20, 2021, 3:49 PM UTC

The product’s naming conventions make me think this would have been an ideal post for the first of April. It certainly gave me a good chuckle.

With that said, we need more independent web browsers. Good for them.

Re: The Hotdog web browser and browser engine

#114

Post by yjftsjthsd-h » Tue, Apr 20, 2021, 3:55 PM UTC

warpech wrote: post #86

jmercouris wrote: post #67

Earlier quoted context omitted.

It depends by what you mean. Do you mean Command line accessible version? If so, there are several that work in terminals. Do you mean text only? If so, there are several browsers that can do this for you :-)

Care to provide some working examples? Many that can be found on Google appear to be working prototypes that are not actually usable.

Depends on your idea of "usable" of course:), but w3m?

Re: The Hotdog web browser and browser engine

#115

Post by sumtechguy » Tue, Apr 20, 2021, 3:55 PM UTC

damagednoob wrote: post #109

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.

I used to do this. Now I use 'boring' names. My funny joke is not very funny anymore spin 2 years on (even then it was only slightly funny). Then you end up with a lookup chart for what does what. When if I had just used 'normal boring' names in the first place I would not be trying to remember what object 'funnyname' does vs 'movedatatodb' object name.

Re: The Hotdog web browser and browser engine

#116

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

commandlinefan wrote: post #104

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?

Sonoran dogs are amazing. Definite contender for best drunk food in the world. https://en.wikipedia.org/wiki/Sonoran_hot_dog

Re: The Hotdog web browser and browser engine

#117

Post by coldpie » Tue, Apr 20, 2021, 4:06 PM UTC

eitland wrote: post #35

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…

I've been arguing this for a while: I want a browser that deliberately cannot run random scripts; only from a vetted source. That source will contain stuff like autocomplete and htmx or similar. If something doesn't work with that it asks you if you want to enable "bloat mode - warning: unsafe" and I the user chooses it enables a full browser engine.

NoScript goes a pretty long way to being what you want, while still being usable. You can whitelist scripts per-domain, so you can still block the garbage while making the site functional.

Re: The Hotdog web browser and browser engine

#118

Post by gwittel » Tue, Apr 20, 2021, 4:08 PM UTC

mynameisash wrote: post #2

I was really hoping that this was some sort of reboot of the HotDog[0] HTML editor by Sausage Software[1]. [0] https://archive.org/details/tucows_194462_HotDog_Professiona... [1] https://en.wikipedia.org/wiki/Sausage_Software

I had hoped this as well. I spent so much time in that program building web sites long ago. We have a plethora of excellent dev oriented editors today, but a purpose built one can be so much better by simplifying workflow.

Re: The Hotdog web browser and browser engine

#119

Post by coldpie » Tue, Apr 20, 2021, 4:08 PM UTC

Daegalus wrote: post #21

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…

honestly, I have been toying with the idea of building a web browser project that has no JavaScript. just completely ignores the script tag or any JavaScript related things. like onclick, and other attributes.

You will get nowhere, the web is unusable without JS. Try running Firefox with JS disabled sometime.

You can use a plugin like NoScript to control what scripts run, it's a pretty decent compromise.

Re: The Hotdog web browser and browser engine

#120

Post by esprehn » Tue, Apr 20, 2021, 4:14 PM UTC

sanxiyn wrote: post #49

fartcannon wrote: post #38

Does it pass the Acid3 test? I haven't thought about that in a long time. Not since I was using Konqueror + khtml engine.

Fat chance. It doesn't implement any CSS selectors at all. Servo passed Acid2 in 2014: https://research.mozilla.org/2014/04/17/another-big-mileston... This is really far behind.

It doesn't appear to implement any standards at all, even self contained ones like the HTML parser: https://github.com/danfragoso/thdwb/blob/655eac96e4faa141cb4...