As part of Project Drawbridge, the Windows kernel introduced the concept of Pico processes and Pico drivers. Pico processes are OS processes without the trappings of OS services associated with subsystems like a Win32 Process Environment Block (PEB). Furthermore, for a Pico process, system calls and user mode exceptions are dispatched to a paired driver.
Pico processes and drivers provide the foundation for the Windows Subsystem for Linux, which runs native unmodified Linux binaries by loading executable ELF binaries into a Pico process's address space and executes them atop a Linux-compatible layer of syscalls.
There are several areas we didn't have time to cover. I fully expect Seth to get these folks in the studio and geek out. STL, it's time for another round of C9 Lectures! If you want to check out C++/WinRT, go here: https://github.com/microsoft/cppwinrt
Outstanding answer, Gov. I expected no less :) Thanks, guys! Appreciate the sage advice.
I've ended up going for the NetGear Nighthawk gigabit wireless router (ordered before I saw this...), but I will definitely get the high speed switch for wired connections. Unfortunately, I don't know yet what bottleneck the optical converter will present (my hope is that it is minimal...).
I hope folks find this useful and, even more importantly, understand that just knowing if a destination is reachable is not enough to move forward with network-intensive operations in your apps. The chances of leaving your customers in a wait-state are too high!
Know before you go! :)
Kudos to Oni Obi, a developer on my small quality engineering team, for constructing the nuget packages and for figuring out the VSIX problem (it's non-trivial to design VSIX packages for C++ components...), which enabled me to post to the gallery.
Really nice to see this old school approach finally materialize in 2015. We often talked about filming meetings and sharing them on C9, but we never got around to pulling it off (and frankly never figured out how to make it an enjoyable experience for viewers...).
Great work, Immo et al! Looking forward to more of these. API reviewing is currently one of the things we do on my not-so-new team. Great learning here!
@james: Well, experience is a rather important property of, well, most everything we do, including using development tools (languages, IDEs, debuggers, designers, compilers, etc...)...
Providing developers with a great experience while coding, debugging, building, designing, etc... is sort of the whole point. Not that you'll agree, but it's probably too bad that IDE doesn't actually stand for Integrated Development Experience... because in practice it absolutely does.