Boston Linux & UNIX was originally founded in 1994 as part of The Boston Computer Society. We meet on the third Wednesday of each month at the Massachusetts Institute of Technology, in Building E51.

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] EOMA68 Computer



On Wed, 20 Jul 2016 17:18:51 +0000
Mike Small <smallm at sdf.org> wrote:

> IngeGNUe <ingegnue at riseup.net> writes:
> > 
> > * It is easier to repair because it's less of a hassle to obtain and
> > swap parts
> > * When there is a problem, you won't be throwing out the entire
> > machine  
> 
> Repair I'm puzzled about. It doesn't seem to me that most keep their
> machines long enough for repair to be a consideration except perhaps
> the hard drive. That's modular now. I don't think the repair issue is
> currently driving the waste so much as Wirth's Law.  My experience is
> consistent with his numbers in the white paper: "if the computer was
> not connected to the Internet it could continue to be used for its
> designated tasks until it suffered major component failure (possibly
> in 8 to even 15 years time)," though I dislike the "if the computer
> was not connected to the internet" part. At some point you could
> imagine repair shops coming back because of modular design but it's a
> distant point from where we are now.

I'm guessing from the opinions expressed above, I'm guessing you're
over 21. Once upon a time, before they grew up, I had college-age
triplets, each with their own laptop. Between ages 18 thru 21, not one
of those laptops lasted more than 1.5 years. Hard drives, power jacks,
broken hinges, cracked screens, busted cases. Two have graduated
college (they're 23 now), and both of those walk around with incredibly
busted computers because I won't pay for another one, and neither will
they.

Also, the computers of 2000-2008 were much more robust than today's
thin, light, cut glass ornaments that pass for laptops. I bought two
laptops in 2006, and except for a bad wifi card caused by a bad
replacement attempt by me, they work perfectly.

SteveT

Steve Litt 
July 2016 featured book: Troubleshooting Techniques
     of the Successful Technologist
http://www.troubleshooters.com/techniques



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org