3 ms·

But it's true. Developing modern code on a Apple 2 is unproductive. It's suboptimal, and worse. Maybe you don't want to use the word "unproductive," and that's

by smabie 6y ago

But it's true. Developing modern code on a Apple 2 is unproductive. It's suboptimal, and worse. Maybe you don't want to use the word "unproductive," and that's fine. But larger screens, faster computers, and more expressive programming languages all contribute to increased productivity over the older alternatives.

the_af 6y ago
> Developing modern code on a Apple 2 is unproductive Are we talking about developing modern code on an Apple 2 now? If so I misunderstood the parent post, because they were using the past tense. In any case, consider this: how do you feel about your current suboptimal, unproductive hardware & software of choice right now? Your current programming language and monitor resolution cannot be used to code. It's simply not possible to be productive with them. Think I'm exaggerating? Ok. Fast forward a few years and let's talk about this again. Maybe you'll understand my frustration...
- smabie 6y ago
  No, I mean, it can. It's just going to (probably) be less productive than what exists in the future. All I'm saying is that the productive/unproductive dichotomy isn't useful and we should instead talk about productivity as a continuum.
  - the_af 6y ago
    > All I'm saying is that the productive/unproductive dichotomy isn't useful Then we agree! I was pushing back against the notion that one cannot be productive unless using a { 5K monitor; three-monitor setup; mechanical keyboard; $YOUR_FAVORITE_TECH_GADGET HERE }. In other words: it's not "time to upgrade your monitor" ;)