- Windows Internals, Parts I and II

- Windows 10 System Programming, Parts I and II

- Windows Kernel Programming, Second Edition

- Programming Windows, 5th and 6th Editions

Surely you mean leanest and meanest :P

I'd also say that tooling on Windows is simultaneously better and easier to use than on Linux; the noob case of green play button in an IDE is taken care of, but if you want detailed performance and memory profiling, record-replay debugging, hot-reload, all of this is straightforwardly available on Windows.

Oddly enough the open-source nature of the latter kind of takes away some of the thrill. Eerything is just... there, whereas with Windows there's always quite a bit of digging and investigation involved. Or maybe this is Stockholm syndrome; I dunno.

??? We don't need any AI for this.

Start with separated sewage/wastewater and stormwater drains. Then accredited and highly scrutinised wastewater treatment and discharge into water bodies (or see below for a high-tech solution). As for clean water to the home, direct those stormwater drains to new reservoirs which sustain freshwater aquatic life. Protect aquifers from over-drainage, and build pipelines from water-abundant regions to water-scarce regions.

To reclaim waste water or treat unknown water sources back to potable/semiconductor standards we have ultrafiltration, reverse osmosis, UV treatment, pH adjustment, fluoridation, desalination, softening (which is generally obviated by RO...). This is basically Singapore's NEWater.

Good sanitation is a financial and political problem. The engineering has been solved for decades now.

People had bad experiences on Vista because they tried to run Windows Aero on 2001 hardware, and hardware vendors for once strong-armed MS into certifying their half-decade-old hardware as 'ready for Vista'.

And in my opinion, the most slept-on: the fact it runs on the CLR and direct access to .NET objects and types which means access to P/Invoke and thence the Windows API. One can write business logic in the fast language and write a nice CLI wrapper around that in the natural shell language, and not worry about painful FFI unlike everyone else trying to fit Python or Bash into whatever world they're using.

The typical counter to this will be: PowerShell is verbose, PowerShell used `curl` as an alias to Invoke-WebRequest instead of the Real Thing™. Neither are real arguments.

But maybe that's because I'm the sucker, and since PowerShell is more verbose it costs me more tokens than the terseness of Unix shells. Oh well.

[1]: https://en.wikipedia.org/wiki/Agni-V?wprov=sfla1

I think the key idea is fixed minimum/maximum boundaries for a lot of astrophysical phenomena—stellar protium fusion, the Chandrasekhar limit, Tolman–Oppenheimer–Volkoff limit, etc.

Most desktop OS compositors provide a void** buffer that can be blitted to. Sure, this buffer will probably end up going through the compositor which does GPU hardware acceleration anyway, but it is definitely possible to shrink the application-side stack without relying on D2D/GLUT/GLEW/GLFW/SDL/WGPU in this case.

On Windows: CreateDIBSection and BitBlt

On macOS: CALayer and CATransaction commit

Not sure about Linux, too many stacks involved.

> If a brown dwarf is right on the edge of stardom would it start protium fusion in only the part of itself that is the right pressure

The nuclear cross-section of protium fusion in astronomical bodies is determined by temperature, pressure, and density. These variables are in turn dictated by the total mass of the object in question. Brown dwarfs never have sufficient mass for protium fusion, so they never undergo any protium fusion whatsoever. This is a hard-and-fast boundary for stardom.

> or would that ignition precipitate a pressure wave through the entire body forcing fusion to begin everywhere

The three variables above are not uniformly distributed throughout the body; there is a maximum at the centre, and fusion only happens here. Even in the Sun, about 99% of the fusion happens within about a quarter of the radius from the centre. The temperature drops rapidly thereafter, reducing the nuclear cross-section of the proton-proton chain to essentially zero. At the photosphere (surface), the temperature is ~5777 K, which is a decidedly Earthly temperature (lightning bolts are ~ 30000 K). So no, fusion does not happen everywhere.

Now, we need to discuss star formation and why brown dwarfs have never experienced protium fusion at any time in their lives. Star formation is still a very active area of research, debate, and fitting models to empirical study, and this is especially true for the detailed interior and structure of protostars and pre-main-sequence stars; hence, this is going to be quite surface-level (pun not intended).

Collapsing molecular clouds form stars. The total mass of a given cloud (or a particular region of it) sets an upper bound on the resultant object, because the total mass dictates the gravitational potential energy and hence the terminal velocity of the matter, and hence the rate of matter infall at the centre before the cloud dissipates. If the mass is low enough, the central object will become a brown dwarf, or even a large gas giant and a 'rogue planet'.

As the gas cloud collapses, the central region increases in density, temperature, and pressure, but no fusion occurs yet. Conservation of angular momentum forms a circumstellar disc, and material continues to fall onto the central region. As long as this infall continues, the central region is called a protostar. At some point the mass of protostar crosses the boundary needed for deuterium fusion; if the infall stops here, the result is a brown dwarf. If this infall continues, the mass increases beyond the boundary (~80 Jupiter masses) needed for protium fusion, and protium fusion can begin. When the infall stops and the circumstellar disc largely dissipates, the result is a pre-main-sequence star.

Note that both these very young pre-stellar objects are not yet at hydrostatic equilibrium, and are still comparatively rarefied (or 'puffy') compared to main-sequence stars; they are still collapsing, and the temperature, density, and pressure at their cores continues to increase. Only when this equilibrium is achieved and gravitational collapse is halted do stars begin life on the main sequence.

Now, it should be evident why brown dwarfs never experience protium fusion: at no point in their lives have they ever had any region in their interior hot, dense, or hyperbaric enough to have a high enough nuclear cross-section for protium fusion. At their formations, they were simply not massive enough; they continue to collapse, which admittedly provides a considerable power output—surface temperatures are ~1000 K. The largest brown dwarfs experience deuterium/tritium/lithium fusion into helium, but this also stops over time.

(Side note: in my opinion the word 'brown dwarf' is a bit of a misnomer, because look at how bright molten iron (~ 1500 K) is even in broad daylight[1]; now imagine an object ten to twenty times the radius of Earth, emitting this much heat from every square millimetre. If you approached a 'new' brown dwarf it would cast a lot of light.)

[1]: https://commons.wikimedia.org/wiki/File:Scunthorpe_Molten_St...

> (1) discard (fast but not a great user experience)

What are we discarding here, and why is it fast but not a great user experience?

> (2) primitive synthesis

I assume this is retriangulating clipped triangles that are now no longer triangles?

> reverse transformed clipping rectangle

Which spaces does this reverse transformation map from and to? I assume the clipping rectangle here is the triangle's AABB in raster space (or as you say, barycentric space).

> integer fixed point, but that is historical — modern fixed point can be handled with careful control of the fp unit in the mantissa

So we are no longer doing 16.16 fixed point, but tweaking the FP representation itself?

> The major issue is regenerating the Z and the 1/Z values for the new vertices

Why is this a major issue?

> deferred attribute synthesis rasterizer

I assume this means attributes are perspective-correct interpolated in raster space.

> the Sun is 3.33e5 as massive as Earth.

Look at Barnard's Star[1], which is actually a fusing red dwarf star: it is not much bigger than Jupiter.

[1]: https://en.wikipedia.org/wiki/Barnard%27s_Star

The exact model limit is unclear, but the physics modelling is relatively straightforward.

At least on Windows, the most you get is a scare screen saying 'this app is from an unidentified developer'. I know what I'd rather have.