wil VS XQuartz

Even then, MFC and C++/CX were the only productive ways to use it from Microsoft SDKs.

.NET isn't as convenient as VB 6 was, fully embracing COM as the VBX replacement model, technically introduced in VB5, but still some stuff was lacking.

Then there is Delphi and C++ Builder.

It beat me that having doubled down on COM since how Longhorn went down, and Windows team getting their way doing avoiding .NET to take over, they hardly managed to create nice tooling as the competition.

Editing IDL files with a Notepad like experience, manually merging generated code, and a couple of frameworks that barely go beyond yet another way to do AddRef/Release/QueryInterface and aggregation.

Meanwhile D-BUS, XPC and AIDL, provide much better dev experience.

Pity that Borland products are kind of tainted due to mismanagement decisions, otherwise maybe fixing COM dev experience would already been seriously taken by VS team.

Ah, nowadays WIL is probably the best approach when having only to consume COM.

https://github.com/microsoft/wil

Have a look at WIL for a C++ library used by Microsoft themselves, including kernel development.

I'm digging for more information and it looks like Microsoft's created a way to handle the problems I'm trying to address with this: https://github.com/Microsoft/wil/wiki/RAII-resource-wrappers

Since we are on this subject, those that need a nice C++ library to deal with COM in VC++, are better served with WIL.

Not since Vista.

https://docs.microsoft.com/en-us/cpp/build/reference/kernel-...

> Creates a binary that can be executed in the Windows kernel. The code in the current project gets compiled and linked by using a simplified set of C++ language features that are specific to code that runs in kernel mode.

And then there is WIL, https://github.com/microsoft/wil

https://community.osr.com/discussion/291326/the-new-wil-libr...

> First off, let me point out that this library is used to implement large parts of the OS. There are hundreds of developers here who use it. So unlike, uh, some other things that get tossed onto github, this project is not likely to wither and die tomorrow.

> There are, however, only a handful of kernel developers working on the library, so the kernel support has been coming along much slower. I'd like to expand the existing kernel features in depth ....

> Plus C++ standard library can't be used anyway and auto pointers aren't really that much of a concern at the kernel level

https://github.com/microsoft/wil

"Ah, but that isn't used on the Windows kernel" would be the expected reply, well

https://community.osr.com/discussion/291326/the-new-wil-libr...

"Microsoft's toolchain does not ship a copy of the STL that works in kernel mode. Partly this is because the kernel's CRT doesn't support C++ exceptions. (And partly this is because I/O is wildly different in kernel, so you'd have to rewrite the implementation of all the I/O libraries.)

But for kernel developers, wil ships a subset of an STL implementation. To avoid conflicting with the real STL, it's available under the wistd namespace. The rule of thumb is that wistd::foo is a drop-in replacement for std::foo."

Windows is a mix of legacy C code, which started to be migrated into C++ around the Vista time (hence /kernel in VC++) and .NET/COM (WinRT is basically COM with some extras).

Modern kernel code makes use of WIL.

https://github.com/microsoft/wil

brew install --cask xquartz

Or install from the project homepage [1]. Then just launch the X11 app. Note that it does require the application to be built for Mac - it’s not an emulator, just an implementation of the X11 APIs.

[1] https://www.xquartz.org/

I’ve recently spent some time working with terminal emulators in raw mode on macOS. While I chose to handle key events using escape codes, and found it seriously difficult (even gave up) to process the shift modifier key. However, I came across xquartz [1], which seems to do similar things as mentioned in the article. Would detecting shift key state have been trivial using such a library?

[1] https://github.com/XQuartz/XQuartz

The contents are rendered through gtk/cairo which not only goes through https://www.xquartz.org/ but also doesn't use GPU rendering (it was experimental 3 years ago, maybe better now). The main issue seems to be that neither Inkscape nor gtk people have much low level Darwin experts or time available to invest in debugging the whole rendering stack. See for example https://gitlab.com/inkscape/inkscape/-/issues/1614 and all the other referenced issues for all the gory details.

I live in a mezzanine studio using a M1 macbook for a workstation (writing/editing) and my old laptop with openbsd as a local server. I play music from that obsd server upstairs, which thus fills the whole room down to my desktop through the plugged-in speakers. My hosted library plays fine with mpd and ncmpcpp, and I just figured out it's not so difficult to use mpv to play streamed youtube videos, since firefox in XQuartz streaming from xenocara is way too slow anyhow.

There is an alternative: I ended up using Xquartz to give me an X11 environment and then running StumpWM as my tiling window manager. I used this for all my productive stuff, running full screen in MacOS, then a quick keypress got me back to the Mac environment.

I also used Xquartz. Emacs was better for me though because capturing text output and documenting what I captured was so much easier than X-window.

Link

I used a Mac for router software testing for over 20 years. I ran a shell on my mac either through Emacs (on occasion) or X-quartz with terminal connections to a dozen or more routers, linux and or Windows systems. In all that time, I opened the terminal on my mac maybe 5 times.