Same, Asphyxia tutorials were considered very good back in the day for democoding in x86 asm. I think they were included in "Programmer's Heaven", a CD full of (obviously) programming guides, tutorials and technical manuals https://archive.org/details/Programmers_Heaven_InfoMagic_Mar...
The sad part is that this setup is probably slower and laggier running on top end machines of today than turbo c running on the actual legacy hardware back in the day.
It's actually pretty close in speed, and quite a bit faster to compile larger code bases. The key benefit is being able to debug while the program is running in VESA modes, something you couldn't do in Turbo C or similar environments.
This seems like such a needlessly kneejerk reaction just to speculate and rag unfairly on anything modern. Couldn't you have actually done some testing and research first?
Maybe - if you're just looking at keypress to character on screen. But you're missing a ton of other advancements - higher resolution screens, better colors for syntax highlighting, intellisense, robust debugging, and, of course, access to the internet for help that you need. Back in the day I had a printed copy of Ralf Brown's Interrupt List that I just had to muck with and pray I got it to work without hanging my computer. With this if it hangs, no big deal.
So, yes, the raw response rate from key press to phosphors being illuminated on the screen might be less, but the overall productivity of a developer is probably and order of magnitude more.
Then again, I did learn to program from the online help in Turbo Pascal and Turbo C++, so maybe there's something to those systems.
There's something really fun about programming directly for a DOS machine. Mucking around with the interrupts, copying whole off screen rendered pages to the video RAM to show the new page, needing to think about RAM consumption, diving into assembly to optimize routines (probably not needed anymore), palette changes to simulate animation. Some of those constraints really help to promote creativity.
I recorded a couple video tutorials doing this with vim and openwatcom C. I never published them though.
I kind of want to start a channel for that sort of thing but haven't really decided on a format and keep going back and forth on it. I've built up a fair amount of unpublished footage at this point.
Just start, you can always change the format later.
By the way, there seem to be two main groups of programming-related channels on YT. One are terribly serious and a bit boring because of monotonous voice and in general, well, not much is going on. On the other end of the spectrum you got pure entertainment and almost no knowledge transfer (maybe except inspiration) like Dani. It would be great to find some sweet spot somewhere in between, for people with ADHD like me who quickly get bored and need some emotions in the video but at the same time want to learn something and not just waste their time watching half-baked attempts at crazy game ideas.
This would be very cool, I love these kind of videos. Perhaps you can find the right format as you building up your channel. There are lots of Youtubers shaping their channels over time to improve, imho the most important part is to start and get the content public.
http://qzx.com/pc-gpe/index.php