I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
Did anyone ever do "Web Development over RDP"? I've never heard of that.
I mean, back in the early 90s you could connect your terminal to a remote machine and edit the files manually, but once browsers kicked off on home PCs, development switched to them too.
As for powerhouse computers handling thousands of terminal connections... my memory of university is somewhat different, with connections being too slow to complete a login in 20 minutes if a lot of people were using up resources. It wasn't down to the network, usually, but to other users running heavier applications on the shared system.
RDP is Windows Telnet Equivalent. Unlike Telnet, it's bandwidth needs are huge in comparison. We we do web development remotely everything rendered in the browser has to be sent back to remote client. It doesn't do the browser rendering per se, it just sends the images back at same rate browser renders.
I worked for 12 years inside IBM itself as software developer. I can assure you that any of their mainframes or midrange computer easily handled hundreds or even thousands of dumb terminals. There are two reasons for this 1. No company does I/O better than IBM 2. 3270 and 5250 don't resend entire screen everytime, the just send changes.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Did anyone ever do "Web Development over RDP"? I've never heard of that.
I mean, back in the early 90s you could connect your terminal to a remote machine and edit the files manually, but once browsers kicked off on home PCs, development switched to them too.
As for powerhouse computers handling thousands of terminal connections... my memory of university is somewhat different, with connections being too slow to complete a login in 20 minutes if a lot of people were using up resources. It wasn't down to the network, usually, but to other users running heavier applications on the shared system.
RDP is Windows Telnet Equivalent. Unlike Telnet, it's bandwidth needs are huge in comparison. We we do web development remotely everything rendered in the browser has to be sent back to remote client. It doesn't do the browser rendering per se, it just sends the images back at same rate browser renders.
I worked for 12 years inside IBM itself as software developer. I can assure you that any of their mainframes or midrange computer easily handled hundreds or even thousands of dumb terminals. There are two reasons for this 1. No company does I/O better than IBM 2. 3270 and 5250 don't resend entire screen everytime, the just send changes.