Home Creators Posts Import Register Favorites Logout

Content

Hey! Thank you guys so much for all of the kind words on the new video (and thanks to everyone who gave me feedback along the way, it really helped!)

I'll be starting work on some bonus Patreon-exclusive "appendices" soon covering both the dotnet95 project and the video itself, and I'd love to open the floor to you guys: do you have any questions you'd like me to answer or specifics you want me to cover? Lemme know in the comments and I'll try to address everything!

Comments

Winksplorer

1. Why use elmo to represent .NET in the video? 2. What were the inspirations for the video's movie-like parts? 3. Are there any plans currently to port .NET back even further to Windows 3.1, DOS, or even some other OSes like ancient versions of Linux or Solaris?

reminon

Dos would be interesting!

IoI xD

If you were insane enough to backport further versions of .NET to win95, how far do you think you could go? How far do you think you *would* go?

nthli.v

Obligatory "But does it run Doom?" (It's Win95, ofc it does, but does it run on dot net?)

nthli.v

In a more serious question: Considering your trouble with the debugger, was there at any point a moment where you thought you'd write one yourself? Or was that not in the cards?

nthli.v

Another one: Did you have specific programs in mind to want to support while building it?

_Maki

What are some of the most interesting programs you backported using that?

WamWooWam

Where are the streams Matt?!??!!11! In seriousness though, one of the coolest things about this for me was watching the progress "live" over time, so I'm wondering if this is something you plan to do for future projects?

Willow Bracker

Any novel issues with the dotnet debugger or no

dennis quiad

Are you going to submit a patch to get Microsoft to fix their stupid bugs?

Casey Blackburn (Twitch Apex Stats)

Not related directly to dotnet95, but what are the factors that make certain .NET frameworks unavailable on certain versions of Windows? Is it the lack of certain Windows APIs for .NET not existing in earlier versions? What allows .NET Core truly run crossplatform where the other .NET Framework versions failed to make this a reality.

Joel

Completely ridiculous and only tangentially related question - but what are you using to run Windows 95? PCem? 86Box? QEMU? Real hardware?

QPrompt Teleprompter

Just wanted to say: I feel watching your videos makes me a better developer. Anything experience that you think might make another person say that, I think would make for valuable content; even if at the end we're here for the stories.

Bubbadega

I wonder how Microsoft engineers attached a debugger to JIT'd code, like to debug when their JIT compiler screwed up, for example. I wonder if there is/was some tool/technique that would have saved you from having to step instruction-by-instruction in that debugger for days

Bubbadega

(this whole video is very impressive by the way, and I respect you for hunkering down and getting 'er done)

IoI xD

How many Win32 functions did you backport? Just the one?

Gordinator

1. You kind of mentioned in your video that you backported .NET 3.5 all the way back to Win95. If this is true, this is HUGE. (Truth be told, I don't think you focused enough on the impact dotnet95 has, brushing it off as something really minor). 2. How reliable is compatibility? You only showcased your own software running on win95 lol