3 ms·

Should we do things in 2018 how we did them in 1998 just because it sort of worked in 1998? I say this as somebody who’s usually quite conservative in operation

Should we do things in 2018 how we did them in 1998 just because it sort of worked in 1998? I say this as somebody who’s usually quite conservative in operations.

coldtea 8y ago
>Should we do things in 2018 how we did them in 1998 just because it sort of worked in 1998? Well, if it ain't broken, don't fix it.
- the_new_guy_29 8y ago
  Broken - no, tedious and resources consuming - hell yes
- crehn 8y ago
  There’s a very fine line between painfully cumbersome and broken.
- rsyntax 8y ago
  Just curious, do you still have/use a Nokia cell phone?
  - ForHackernews 8y ago
    Funnily enough, I had to send my smartphone in for repair recently, and I popped my SIM card back in my old Nokia phone that I'd kept in a drawer -- it works great. It's a 10+ year old device and the battery has lasted all week.
  - EpicEng 8y ago
    No, but my old one still works, unlike my last 8 smart phones.
    - wsy 8y ago
      And still you use the smart phones daily, not the 'working' Nokia.
      - EpicEng 8y ago
        It's not binary. Robustness is something we lost. Yes, I am more happy (maybe? Perhaps I now just have another way to waste my time and be interrupted) with my smartphone, but I (we) lost something in the transition. That's the point; you're adding complexity and some people want to pretend that there's no trade off.
        wsy 8y ago
        I agree, there is always a trade-off, and it is good to make it as explicit as possible.
  - coldtea 8y ago
    Yes, helped me skip the whole "attention drainage", "mobile detox", "missing the concern while looking at your screen", "stolen privacy" thing...
darkarmani 8y ago
> because it sort of worked in 1998 Is "sort of worked" better than "only works until the next version of docker and docker's next new, new storage layer"? If you need to add 100x the moving parts and hidden interactions to solve some hard problems then your hard problem just got harder. You've just kicked the can down to production.

Should we do things in 2018 how we did them in 1998 just because it sort of worked in 1998? I say this as somebody who’s usually quite conservative in operations.

coldtea 8y ago

>Should we do things in 2018 how we did them in 1998 just because it sort of worked in 1998? Well, if it ain't broken, don't fix it.

the_new_guy_29 8y ago
Broken - no, tedious and resources consuming - hell yes
crehn 8y ago
There’s a very fine line between painfully cumbersome and broken.
rsyntax 8y ago
Just curious, do you still have/use a Nokia cell phone?
- ForHackernews 8y ago
  Funnily enough, I had to send my smartphone in for repair recently, and I popped my SIM card back in my old Nokia phone that I'd kept in a drawer -- it works great. It's a 10+ year old device and the battery has lasted all week.
- EpicEng 8y ago
  No, but my old one still works, unlike my last 8 smart phones.
  - wsy 8y ago
    And still you use the smart phones daily, not the 'working' Nokia.
    - EpicEng 8y ago
      It's not binary. Robustness is something we lost. Yes, I am more happy (maybe? Perhaps I now just have another way to waste my time and be interrupted) with my smartphone, but I (we) lost something in the transition. That's the point; you're adding complexity and some people want to pretend that there's no trade off.
      - wsy 8y ago
        I agree, there is always a trade-off, and it is good to make it as explicit as possible.
- coldtea 8y ago
  Yes, helped me skip the whole "attention drainage", "mobile detox", "missing the concern while looking at your screen", "stolen privacy" thing...

darkarmani 8y ago

> because it sort of worked in 1998 Is "sort of worked" better than "only works until the next version of docker and docker's next new, new storage layer"? If you need to add 100x the moving parts and hidden interactions to solve some hard problems then your hard problem just got harder. You've just kicked the can down to production.