3 ms·
Yes, I was wondering where they were rasterizing to. Although of course the most long-lived way is to just P/Invoke straight into user32.dll to bring up a windo
by pjc50 4y ago
Yes, I was wondering where they were rasterizing to. Although of course the most long-lived way is to just P/Invoke straight into user32.dll to bring up a window.
(The last time I wrote a 3D rasterizer was in 1996, and I had to type my dependencies in from paper into Borland Turbo C)
- actionfromafar 4y agoYou remember that demo where someone made an EXE from C# and made it run on Windows 3.1? I wish there was some streamlined way (config of VS Code?) of doing that, not as extreme, but building regular Win32 apps without the .NET runtime, but with the C# language. Like how you can still use modern C++ but target just Win32. That would be I think, an awesome compromise of power. C# is a really great language all on its own, without the .NET standard library.
- pjc50 4y agoI'd forgotten about that, do you have a link handy? It might be doable in MSBuild. I might actually have a use case for this as well, after battling problems of self-contained apps. The "AOT" compiler is basically "run the JIT upfront".
- actionfromafar 4y agohttps://www.hanselman.com/blog/net-everywhere-apparently-also-means-windows-311-and-dos https://www.hanselman.com/blog/net-everywhere-apparently-als...
- bob1029 4y agoA bitmap that is then encoded to the client as jpeg or x264 data across the websocket. The hard part is making the pixels get to the human eyeballs. I handwave that away with the browser. Imagine a very primitive version of stadia.