Comments by "OpenGL4ever" (@OpenGL4ever) on "ThePrimeTime" channel.

@RetroPcCupboard Knowing assembler helps you understand what the compiler produces and how high-level languages work. I think this is very valuable knowledge, it's like Latin for languages.
18
Then I have a question. I've also heard that Intel would like to throw out some things. But if a CPU has, say, 8 cores, would it be possible to just throw those things away at 7 cores and keep them at just one core? Especially the old stuff that was used in the DOS era was never written for multicore CPUs anyway. This old software would therefore only need this one full-fledged core.
18
@segueoyuri No! Finding the bug required two requirements, the first was skill, the other was pure luck. The evil code was already included in Debian Testing, for example, and no one noticed it yet. If the German Microsoft developer (-> skill) hadn't worked on it on his flight back (-> luck) to the USA, it wouldn't have been noticed and the code would have ended up in Debian stable later. There was no one who discovered the evil code when committing to Debian Testing.
5
@jaysistar2711 That is not a useful explanation. Because you could have switched to Windows NT and benefited from the larger software offering. Free software would be an argument for Linux. Or a new platform where everything is still growing and where you can get involved. Or that you need an OS that is similar to Unix. That would also have been a reason in favor of Linux at the time. Linux and the ecosystem around it were not as developed back then as it is today.
2
@jaysistar2711 Linux was definitely in its infancy. Kernel 2.0 was only released in mid 1996, at which time Windows NT 4.0 was also released. There wasn't even a proper graphical desktop environment for a Linux system. Gnome 1.1 and KDE 1 came much later. And simple Window Managers are not comparable to the desktop in Windows NT or Win 95. NTVDM was available since Windows NT 3.1 and this could run some DOS and 16 Bit Windows applications.
2
@betag24cn No, 3dnow! is obsolete and got removed from newer AMD CPUs. There was an agreement about the SSE family of instruction sets, thus 3dnow! was no more needed and it was incompatible with SSE.
2
@betag24cn AMD K10 was the last CPU generation from AMD that supported 3dNow!
2
@betag24cn You're welcome.
2
You might also search for "The Intel 80386, part 1: Introduction Raymond Chen" and read part 1 to n.
1
@TheUAoB The reason he gave was Windows 95. Because if Windows 95 is the problem, then you can simply switch to Windows NT. At that time, Linux was still in its infancy.
1
I love x86! ❤ I also love to program in x86 assembly. x86 is my childhood, I grew up with it. I like even 16 Bit Real Mode assembly. In its days it was great, it saved a lot of memory. And 32 bit protected mode and then 64 bit long mode followed.
1