glaze VS old-new-win32api

Previously in the Glaze library, you would need to write out your key names along with the member object pointers. However, as of version 1.8.0, these key names are now optional. If the keys are not provided the member variable name will be reflected for serialization/deserialization. I'm even more excited about this reflection than the previously announced pure Clang reflection, because it works well with user customization and supports non-aggregate, non-default constructible, and non-constexpr types.

BEVE fully supports JSON messages. The Glaze C++ JSON library allows users to use the same API to encode/decode to either JSON or EVE binary. Glaze also encodes/decodes directly into your C++ structures and standard library containers, making it easy to use without additional copies.

I would either look at https://github.com/eyalz800/zpp_bits or https://github.com/stephenberry/glaze. FYI, glaze both supports json and binary.

Glaze is a software that uses artificial intelligence to create realistic images from text descriptions. It is based on Stable Diffusion, an open source framework for image synthesis using diffusion models. Glaze claims to offer enhanced model training with minimal style interference by using a technique called ControlNet1.

I ended up adopting this approach in some test code https://godbolt.org/z/GKW8Preva when I was thinking about adding automatic enum serialization/deserialization to stephenberry/glaze. But there are too many limitations.

Alternatively, use a preexisting library for binary serialization and deserialization. If you’re trying to serialize your own stuff, glaze is a good option since it supports both json and binary serialization/deserialization. https://github.com/stephenberry/glaze

This parse file has some of the chunk simd processing: https://github.com/stephenberry/glaze/blob/main/include/glaze/util/parse.hpp

Do you have any recommendations?

I assume this is the one you’re talking about https://devblogs.microsoft.com/oldnewthing/

I was curious, went to the end (page 699!) and it’s pretty interesting. But obviously it’s hard to find the important ones.

Not quite. DOS was just the bootloader for Windows 9x.

While Windows 95's kernel didn't have the full feature set of NT, it still was more sophisticated than DOS.

Source: https://devblogs.microsoft.com/oldnewthing/?p=24063

Some registry keys also have The Old New Thing posts by Raymond Chen [1] /s

[1] https://github.com/mity/old-new-win32api#registry

Lucky you, Raymond Chen did an overview in his blog series "Inside STL". You can view it here: https://devblogs.microsoft.com/oldnewthing/

Yes, Raymond Chen describes such fixes in [several blog posts](https://devblogs.microsoft.com/oldnewthing/) and in his book The Old New Thing. Check the old posts, back at the beginning. There are posts about to which lengths they went to ensure buggy applications still worked after an update or a fix.

https://learn.microsoft.com/en-us/archive/blogs/larryosterman/ https://learn.microsoft.com/en-us/archive/blogs/ https://devblogs.microsoft.com/oldnewthing/

A couple of blogs as an example: - Raymond Chen - https://devblogs.microsoft.com/oldnewthing/ - Pavel Yosifovich - https://scorpiosoftware.net/ - Adam Sawicki - https://asawicki.info/index - Matt Pettineo - https://therealmjp.github.io/ - Scratchapixel - https://www.scratchapixel.com/

https://devblogs.microsoft.com/oldnewthing/