This is ghastly (RT @ManishEarth)
11
47
1
199
Haha, at first I thought that sounds horrible. But then I remembered all the networking code in Firefox is in the netwerk/ folder. And after 5 years on working on it that seems absolutely normal to me. 🥴
1
10
… … … is this … … dutch??
2
1
i think there's a "good" reason for that, perhaps something about some old system not allowing folders with the name "network"? I distinctly recall there being a story about this but I don't remember what it was @davidbaron may know
2
2
Replying to @ManishEarth @mcclure111 @ValentinGosu @ProfBeeman
It was a full rewrite of the networking code. Both needed to coexist for a while. The old code was in "network"... and the new code was never renamed after the old code was removed. This was probably around 1999 or 2000...

Jan 7, 2019 · 12:23 AM UTC

1
4
Replying to @davidbaron @ManishEarth @mcclure111 @ValentinGosu @ProfBeeman
My preferred solution to this issue is another full rewrite of the networking code, with both coexisting for a while, with the old code in "netwerk" and the new code in "network".
1
4
It doesn't need that dramatic a rewrite. The old code was designed to be the scheduler for the entire system... since back in Netscape 1, before Javascript, that made sense... but by 1999 it was messing up the design of the whole browser, as I understood it.
1
4
more replies