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.
badlogic|3 years ago
nils-m-holm|3 years ago
sli|3 years ago
pridkett|3 years ago
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.
AceJohnny2|3 years ago