dblohm7

The closest thing is a special APC enqueued via QueueUserAPC2 [1], but that's relatively new functionality in user-mode.

[1] https://learn.microsoft.com/en-us/windows/win32/api/processt...

I can confirm that kenrose is an actual human being :-)

Oh geez, it's been long enough that I don't really remember the specifics. In the hundreds, for sure.

I’d rather be told “no” than end up in detention.

> This is no criticism of the Firefox team, just the reality that my priorities are not their priorities.

I am a former Mozilla Corporation employee, so I am more willing to criticize the current state of MoCo culture as a whole...

> They don't necessarily have the bandwidth or interest in accepting other people's/teams' vision or contribution.

I would say it really depends on the nature of the patches being contributed; if they are not inconsistent with project goals and not excessively burdensome, I'd hope that they in theory would be considered.

However, I will say that MoCo culture was already much different by the late 2010s than it was in the early 2010s. When I joined MoCo in 2012, there were multiple managers I interacted with who openly valued community interaction and encouraged their reports to set quarterly goals relating to mentoring external contributors. IMHO that encouragement had died off by the late 2010s.

Put it this way: there are a lot more than “a few dozen” engineers working on Firefox.

I'm dealing with a lot of this right now. The product managers working on the Windows App SDK just cannot seem to fathom the notion that not all Win32 apps are written in .NET or C++. I've got a GUI written in Go that I'm adding WinUI3 features to, but I pulled that off _despite_ their SDK, not _because_ of their SDK.

The irony of all of this is that WinRT is built atop COM, which should allow it to bind with any language that supports a C-based FFI on Windows. But then they add all this XAML codegen crap that's C++ or C#-only, pulling us in too deep.

> I do not feel this has held me back professionally. I have been loved by management and peers in all of these jobs.

If only your experience was universal in that regard! I once had that role in an early-career job -- but I was looked down upon by peers and management because I was doing mostly maintenance work. The "good" developers, in their minds, were the ones shipping the most new features -- the irony being that those features would then blow up out in the field, at which time they landed on my desk to turn them into production-worthy code.

Yet many age discrimination suits against tech companies _don't_ succeed...

Great comment, Mike, and thank you!

It really resonates with me because during my university years, I myself had a poor social network. As soon as I started interviewing, I was like, “WTF is this?!” whereas some better connected peers seemed to somehow “just know” how to be prepared to interview. There definitely wasn’t equal access.

Thanks for trying to make things better!

Firefox has used Servo's rendering and styling components for years now.

The Canadian system is much better.

[1] https://en.wikipedia.org/wiki/Nav_Canada#History

** N64 has entered the chat

I would argue that such intentional changes to language isn't "evolution" at all. Sure, language evolves, but not by some kind of edict.

Yeah, that new content management system is awful too -- it doesn't grok preprocessor stuff at all, so sometimes you get nonsensical struct definitions, kernel-mode structs instead of user-mode structs, etc.

What really annoys me these days is that if you search for a Win32 API on Google, it will always come up with the -A variant, not the -W variant. I don't know if they've got something weird in their robots.txt or what, but I find it bizarre that an API whose guidelines desire developers to use the -W variants in all greenfield code, instead returns the legacy APIs by default.

Yup. At the time, third-party DLL injection was one of the single biggest causes of Firefox stability issues.

Don't use DLL injection -- use extension APIs. Too many products use DLL injection as a golden hammer.

I'm the engineer who spearheaded adding the blocking technique outlined by OP. Security vendors are some of the worst offenders when it comes to injecting buggy DLLs into processes.

> And if we read the associated bug (https://bugzilla.mozilla.org/show_bug.cgi?id=1322554) we can see this is described as "policy decision", and this entire section of the code isn't exploit mitigation, but rather intended to block broken third party programs from injecting their buggy and poorly written DLLs into Firefox and causing bugs that users report to Mozilla.

Indeed -- in fact, I was tech lead for an entire project dedicated to dealing with this situation (InjectEject).

Third party DLLs injected into browser processes cause all kinds of crash spikes.

The browser is Firefox, and I'm the engineer (no longer at Mozilla) who spearheaded the development of this. AMA.

> So? "The rules need to be changed because the wrong people keep winning" sounds very suspicious to me.

That's not what they're saying. In Canada, we can easily end up with parliamentary majorities for parties that have less than 50% of the popular vote. Sometimes substantially less.

This is good news. His government has been dysfunctional for some time now. It's unfortunate that he held on for so long, as we needed a government ready to deal with Trump yesterday.

An editorial from Dec 19 (gift link):

https://www.theglobeandmail.com/gift/eca53705d5e7568f5ed88c7...

This is true, but I'd love to see something happen to force Canadian provinces's hands to improve this.

To dream the impossible dream...

> Microsoft, then a tiny fraction of what it is now, took $400 million from IBM in co-developing OS/2 and put the profit from that money into Windows 3.0

The timing didn't happen the way you're describing it. There are numerous accounts of the tale of how David Weise and Murray Sargent got Windows running properly in protected mode as an unauthorized, personal side-project.

https://news.microsoft.com/2000/09/10/i-found-a-cool-little-...

Albertans will "rat" (pun-intended) each other out for stuff like this.

Respectfully, I think you're missing the point. Windows uses idioms like that too (though usually via filling an initial field with the size of the structure in byte), but GP's point of an Ex-style API would be to completely eliminate kludges such as runtime type fields at the beginning of structs and move to something safer.

The real problem is dogma and cargo culting.