Recent searches
Search options
Today in “men explain technical concepts to women who have more specific and deeper knowledge”:
* I was whinging about a page that required Chrome (which is, by definition, NotAFreakingWebPage because SomeRandomBullshit piped to port 443 does not a web page make).
* I was told that Chrome and Safari shared an underlying library.
Which: I was on the Safari team for 5-1/2 years, including the time when Google forked from WebKit, which was in 2013.
So.
@deirdresm Ugh. So sorry you had to endure that bullshit.
As for me, I’m looking forward to the first motherfucker who tries to mansplain Web browsers to me. Poor bastard won’t know what hit him.
@lisamelton That's because you're a Girl Who Started Two Web Browsers and are therefore more awesome than I am.
(This one was trying to be helpful, so I'd give him half a cookie.)
Edit: started one plus a working on project I remembered as being partly a web browser. And Netscape.
@deirdresm @lisamelton
Started zero web browsers, now feeling severe imposter syndrome
I don't recommend doing a whole one, but doing a little toy one is actually a cool kind of project that teaches about parsing something complex.
I'm actually doing something different right now, inspired by how Memoji might be put together.
Like this could be:
Hair + zero width joiner + wavy type + zero width joiner + blue
Etc.
@deirdresm @deirdresm @lisamelton
That’s delightful! Be sure to ping me if you ever get it working.
Parsing is a barrel of fun, but if I were actually going to write a toy web browser, I think the thing I’d most like to explore is the kind of optimizations that go into making a mutable DOM performant in the presence of such a convoluted layout engine. The box model & CSS are terrifying enough from the user side!
@inthehands The thing to remember is that writing a "small" Web browser is actually more complicated than writing a "small" operating system. 
Trust mom on this one.
@lisamelton @deirdresm Oh, I believed you on this point even before you posted it!