- 12,996
- 31,282
Imagine now that in order for your program to work, you have to write custom code for each and everyone of them. He wants developers to do this, instead of using the libraries that abstract that for us. So imagine for a second the inane amount of work that entails. Imagine that if you bought a video card that was released AFTER your program is made, your program crashes, because it is not coded to initialize such video card, and his solution is "Release a new version of your program to account for this."
That is the level of absurdity he is saying.
I don't think that's what he's saying at all, if you look at the second video, he's more advocating for a unified architecture kind of thing between all hardware, so they all work on the same fundamental instruction sets, and using SOCs as an example of this in action.
The issue is, obviously, it's in no hardware makers interest to do that. They would rather make just more code on top of code.
Regarding word typers today being slower than word perfect, so what? Can wordperfect of 1995 do any of the million things the current word processor can? The answer is no. If all the downside for it is a minor graphical delay when pressing a keyword, then it is a tradeoff that works in favor of the modern software.
No offense, but this is exactly what he talks about how people constantly make excuses for things, and why he felt the need to compare 1995 to 2018 (when the 2nd video was made).
No, WP 1995 can't do any of the million things the current word processor can. Now tell me, when you use a modern word processor, do you use those millions of things? His point here was: what you could accomplish in 1995 can also be accomplished today, but the experience of accomplishing that task is considerably worse today than it was in 1995 and there's no reason whatsoever that should be the case given modern hardware capabilities.
Adobe is the worst out of them all. It has Creative Cloud, which is fragile, slow, and spams the fuck out of your system with a bunch of random shit. I switched to an older, pre-CC version and also use Affinity Photo in its place.
Adobe's worst crime is is still doesn't do multicore anything. Compressing 1gb of JPG to a small size takes well over 1 minute 41 seconds. The same operation in Affinity Photo takes....16 seconds.
Such as this earlier post from

As for the terminal -- As I saw it, the point of the video isn't how to raster text super fast or anything. The point of the video is that the terminal is spinning cycles and performing slowly for no reason whatsoever, because in order to raster the text on the terminal, it has to go through countless windows sub-systems to do so, when almost none of it is needed. And even so, in the end, you can't do simple basic things that are nice such as changing the font in the terminal (unless you go through a registry hack unless the font is specifically a terminal font), or format things like 2/4 byte characters properly. So despite being bloated, and spinning more and more cycles to accomplish the same task as his terminal, it doesn't even do a good job of it from a computing side of things.
Last edited: