dblohm7

14 ms·

181.
by dblohm7 4y ago
You make it sound like Mozilla is pushing back for no reason. They have pretty valid security and privacy concerns.
182.
by dblohm7 4y ago
Building similar integrations will require, in your words, "focusing elsewhere." You can't have both.
183.
by dblohm7 4y ago
Apparently they are keeping that under cover for competitive reasons: https://twitter.com/skrishna/status/1635998864531439617
184.
by dblohm7 4y ago
That's fair, but how is that any different than async I/O on any other OS?
185.
by dblohm7 4y ago
> The article also felt like Rust does it this way because all these other projects which came before it did it this way. Someone originated the technique and no one questions its validity, without seeing if there was an alternative meth
186.
by dblohm7 4y ago
> Also, I've heard a lot of praise about Microsoft's networking integration which made things like mounting network drives possible and reliable as early as Windows 2000. But of course, if you refuse to use the recommended APIs
187.
by dblohm7 4y ago
That's how things have always been done at Mozilla (I spent several years there dealing with Windows-specific stuff for Firefox)... I kinda wonder if Rust inherited a lot of that attitude from there.
188.
by dblohm7 4y ago
Good god. I like nothing about this piece. I hate the claim that Windows networking is "duct-taped" in. I hate that they're using undocumented stuff. I hate that they're trying to shoehorn Windows into a Unix-y model; in
189.
Tales from Debugging Subreddit(old.reddit.com)
1 points by dblohm7 4y ago|0 comments
190.
by dblohm7 4y ago
That only works when you're copying to the same OS. You run the change of entering into a world of hurt if your new device runs on a different platform.
191.
by dblohm7 4y ago
This reminds me of an email my CEO sent out in 2008, where he jacked up parking fees at the office "because of the economic downturn." Unfortunately for him, another email he sent out not five minutes before was proudly boasting a
192.
by dblohm7 4y ago
https://learn.microsoft.com/en-us/windows/win32/api/dxgi/nf-...
193.
by dblohm7 4y ago
I wonder how Stylo (Firefox's style system adopted from Servo) compares.
194.
by dblohm7 4y ago
Windows 95 was still DOS-based and DirectX was just beginning to take off; many of the most popular games of that era ran on DOS. (I remember that the best way to run the original release of Warcraft II was to set its shortcut to "DOS
195.
by dblohm7 4y ago
> Really surprised that FF is only 4% market share now: what did I miss? The explosion of mobile.
196.
by dblohm7 4y ago
> and aren't investing too much in rewriting parts of FireFox in Rust. False. You haven’t been paying attention.
197.
by dblohm7 4y ago
> Why hasn't the world coalesced around WebKit? iOS is not the entire ecosystem. Blink dominates everywhere else.
198.
by dblohm7 4y ago
Tailscalar here. There were a few things going on with that issue you mentioned; one of them is the way the wrapper library was written, the other was with some stuff in the GUI client that was happening on a background goroutine but should
199.
by dblohm7 4y ago
> Other times, they may threaten to estrange or cut off their children. In some cases, they will do that (although they will often spin it as if the child ended the relationship). I was one of those cases. After years of repeatedly being
200.
by dblohm7 4y ago
I did write a little bit! Here's an oldie but a goodie: https://dblohm7.ca/blog/2016/01/11/bugs-from-hell-injected-t...
201.
by dblohm7 4y ago
I did write a little bit! Here's an oldie but a goodie: https://dblohm7.ca/blog/2016/01/11/bugs-from-hell-injected-t...
202.
by dblohm7 4y ago
> But I think the OS should try to reserve more space for the swap file before it starts returning ENOMEM to the "commit memory" system calls like Windows seems to be doing (judging from the blog post)... One could just as easi
203.
by dblohm7 4y ago
I used to take point for Mozilla's efforts dealing with third-party interference in our binaries. Browsers are ripe targets for this kind of shit. The stories we could tell...
204.
by dblohm7 4y ago
That Stack Exchange answer is kind of weird in the sense that it conflates different things. You can have demand paging without overcommitting (as NT does); the kernel simply needs to assure that there is somewhere to commit a particular
205.
by dblohm7 4y ago
> I suppose it technically improves stability, but the cause seems like a flaw in the Windows operating system, if I'm understanding correctly. It's not a flaw at all, when you understand what is going on. Part of the issue is
206.
by dblohm7 4y ago
(Former Mozilla engineer who can speak Windows) > Maybe Mozilla didn't understand Windows's memory management strategy until now. That is part of it. A lot of FLOSS engineers come from a Linux background and tend to assume that
207.
by dblohm7 4y ago
I worked there as an engineer for just under 9 years. Google does not give Mozilla engineering its marching orders.
208.
by dblohm7 4y ago
They're not getting rid of the old blocking API, though.
209.
by dblohm7 4y ago
https://news.ycombinator.com/item?id=32470615 https://news.ycombinator.com/item?id=32469581
210.
by dblohm7 4y ago
(Tailscalar here) Most of the Tailscale client’s functionality is implemented as a daemon called tailscaled which is in the OSS repo. It’s the GUI front ends for Windows, MacOS and iOS that are not.

More ›