News for hackers. Stuff that matters.
Re:After 1 minute on my modem (2016) by userbinator on Saturday January 14, 2017 @11:52AM (#13399242)
On the other hand, as long as the latency is similar, the SSH experience is pretty much the same regardless of bandwidth --- the exception being commands that produce plenty of output.

Which might not even be such a bad thing - I would not like going back to programming in an environment where I have to triple-check every variable to see if I can shave off a couple of kilobytes, either.

That might be part of why I've found newer programmers seem to write more complex and inefficient code than older ones, who tend to come up with simple and efficient solutions naturally. I think everyone should experience using and programming in a constrained environment, if only to train this skill of what's efficient and what isn't.

Re:After 1 minute on my modem (2016) by handyman5 on Saturday January 14, 2017 @01:29PM (#13399766)
You are not controlling for the programmer's age as a variable. An equally valid explanation could be that newer programmers have less experience to draw from, where older programmers have more experience and know what works and what doesn't. Or, alternatively, newer programmers might just be a much larger pool of people, and perhaps more people stop programming as they get older than start, so that the average skill of an older programmer is much higher than you might otherwise expect (since all the low-skill programmers quit when they were younger).
Re:After 1 minute on my modem (2016) by hedora on Saturday January 14, 2017 @04:26PM (#13400651)
This. My day-to-day code has probably doubled in efficiency every 2-4 years since the mid 90's.

Granted, a decade of that was chasing hardware trends, but the earlier optimizations stack too.

Re:After 1 minute on my modem (2016) by krylon on Saturday January 14, 2017 @04:17PM (#13400600)
> I think everyone should experience using and programming in a constrained environment

FWIW - when I can, I like to to use a - relatively - resource-constrained machine to test my code on, so performance hiccups one would not even notice on a high-end desktop PC become obvious. I used to use a SparcStation for that, but it went the way of all earthly possessions. So now, I use a Raspberry Pi, and an old laptop (it has a "Built for Windows Vista" sticker, so it must have been built before 2009/Q3) for this purpose. It is a luxury I have when programming in my spare time, to use this as the bar - if I cannot get a program to run reasonably well on those machines, I consider it a failure (or a candidate for optimization, when I am in the mood...).