My Toshiba Tecra 8100 has a P3-650MHz, 128MB of RAM, a 12GB hard drive, DVD-ROM, and a 15.whatever-inch display. It comes with two worn-out batteries and the original media to install Windows NT Workstation 4.0 (it has Debian sarge installed on it). I purchased it in June of 2000, so you're pretty close, considering that it was pretty top-end at the time.
I'd do that, but my law school textbooks make EE textbooks seem both exciting to read and physically lightweight. You'd die from either the impact or the material within. EE is better than law for anyone with a bit of sanity remaining.
Lawyers and coders have a lot in common, but with lawyers the stakes of ego disputes are much higher. You file a complaint, he files an answer, and you go on with the war. With coding, you write some code, he fucks it up, and then you go back and fix it. It sucks, but usually nobody gets the death penalty or has to come up with $10 million to pay the awarded damages.
If the patent office runs a MS database, then MS isn't the only person who can get in through a back door and insert retroactive patents. Not even close.
Not to mention that the article itself sucks. It's informative, yes, but I really can't imagine anyone but Mort or Neil Goldman (from Family Guy) writing it.
Demand to face your accuser in court. If a police officer takes the stand, tell the judge to strike everything he says as hearsay and repeat your request that you face your accuser. If they do bring the camera in, accuse it of being uncooperative by not answering your questions, and ask the judge to jail it for contempt.
I bought all my computers, except for the laptop that was a high school graduation gift on account of my college costs being less than zero due to scholarships. As to crashing "their own car," I sincerely doubt that any significant majority of today's teenagers are buying their own cars without any help from mom and dad at all.
This wizard will guide you through the process of installing DesktopBSD on your computer. Please take the time to carefully through all texts and explanations because improper settings can cause data loss.
Yep. Grammar notwithstanding, that's totally worry-free and friendly stuff, right there.
I agree with you to a large extent. My parents, and my father in particular, treated me as an intellectual equal. They knew when to lay down the law, but frankly they didn't have to all that often because I respected them and they me.
On a side note, I find American Beauty to be a bunch of self-indulgent crap. But side notes aren't important.;-D
I absolutely agree that children should have a computer in the house. But it should not be their own. That said, this is all getting into arguments about parenting. Can't we argue religion or politics, instead?:P
I credit early exposure to computers for my expertise with them now. I am a more efficient and more effective person because it doesn't take me any real effort to use a computer. Nobody in the generation my kids will be a part of should be deprived of that, but neither should they be deprived of the opportunities to learn pride in hard work and responsibility. Too many kids today are deprived of one or both of these.
Parents who give their children laptops, sports cars, and the like are not treating them as equals. They are treating them more like pets. Moreover, parents who do treat their kids as equals tend to do so by lowering themselves to the kids' level, rather than vice versa. Look at all the parents who party with their teenagers, or the one mother who was caught having sex with all her teenage son's friends at parties she would throw for them. That's what it means to treat your children as equals, for most parents.
And for the parents who really want to treat their children as equals - treat them like adults! If they want a laptop, they should get a job and buy one. That's what an adult would do, unless your vision of adulthood is being a trophy wife.
Bad handwriting is less a sign of laziness than are poor spelling, improper capitalization, improper spacing, improper punctuation, and incomplete sentences.
Thanks for the pointer on the IO2. It looks interesting, at the very least.
I have both a desktop and a laptop. Take either away, and my lifestyle wouldn't work out. I take my laptop to class and take notes (copious notes - 2,000 lines or more of plain text for a semester in one class) on it. I can't read my own writing, and I can type extremely fast, so it works out really well for me. Additionally, I go to the law library and study there most of the time, taking more notes on my laptop. Then I upload them to my desktop (actually, I use Unison to synchronize both machines to a server located elsewhere - nerdiest law student, EVAR) and compile them into study outlines from there.
Try doing any of that with pen and paper, even if you can write fast enough to keep up with the professor and still read your own writing.
As to the actual point of this article - buying laptops for kids in high school or earlier - I am not a fan of the idea, for a lot of reasons. But the one that I'm going to mention right now is this: High schoolers are, on average, less mature than college kids are, and tend to lose and break anything that's remotely portable. It's bad enough that they're out crashing the family car, don't send them out with a $2,000 laptop to bust up, too. Your kids can use your "family PC." Kick them off if you need it. If they want their own computer, they should buy one. It's a really good time to learn priorities and responsibility, and you shouldn't spend money to deprive them of the opportunity.
For a group of people who crucify each other over the correct number of spaces to indent code by, you would think that more attention to detail would be paid when it comes to proper nouns where there actually is a right way and a wrong way to do it.
I never said you should ignore the spaceflight portion. I only said that the problems we have all occur during the transition parts. Let's simplify the analogy a bit, in fact, and say that procedure calls are expensive and work() itself is cheap. If you can optimize the procedure call (make launch and re-entry safer) without affecting how work() is done, then you should. (Whether you can inline work(), i.e. do all the things you can do in space on the ground, is outside the scope of this discussion.)
Your entire point seems to erroneously rest on the assumption that I meant spaceflight itself should be ignored when solving transition problems. That's not the case at all, and I apologize for misleading you to believe that. The simple truth is that spaceflight is relatively safe, and if you can make getting there and back safer without sacrificing the spaceflight itself and its safety, then you should.
The analogy is sound, if you take note of that one caveat.
That's precisely why it does matter that most spaceflight-related deaths occur not in space. You're safe when you're in space, it's the transition that kills people. Failing to recognize that would lead you to focus on solving the least important problems.
Here's an analogy that most here should appreciate:
(Forgive the lack of indentation. Ecode sucks donkey balls.) If you were profiling that code, you would focus on optimizing work, because that's where most of the computation time goes. It isn't nearly as helpful to say you're going to optimize foo.
So far no American accidents in space have been fatal. We've had one fire on the pad before liftoff, one explosion during liftoff, and one single-vehicle in-air collision on re-entry. No Americans have died while actually in space, unless I totally missed something.
Slashdot Mirror
My Toshiba Tecra 8100 has a P3-650MHz, 128MB of RAM, a 12GB hard drive, DVD-ROM, and a 15.whatever-inch display. It comes with two worn-out batteries and the original media to install Windows NT Workstation 4.0 (it has Debian sarge installed on it). I purchased it in June of 2000, so you're pretty close, considering that it was pretty top-end at the time.
I've noticed that my urine stream is much snappier since I got Tiger.
I'd do that, but my law school textbooks make EE textbooks seem both exciting to read and physically lightweight. You'd die from either the impact or the material within. EE is better than law for anyone with a bit of sanity remaining.
There are no coders who are great people. ;)
Lawyers and coders have a lot in common, but with lawyers the stakes of ego disputes are much higher. You file a complaint, he files an answer, and you go on with the war. With coding, you write some code, he fucks it up, and then you go back and fix it. It sucks, but usually nobody gets the death penalty or has to come up with $10 million to pay the awarded damages.
Who wants a martini? *shakeshake*
Just please, no butter martinis.
If the patent office runs a MS database, then MS isn't the only person who can get in through a back door and insert retroactive patents. Not even close.
Not to mention that the article itself sucks. It's informative, yes, but I really can't imagine anyone but Mort or Neil Goldman (from Family Guy) writing it.
I suspect that they spend most of their time finding all the non-duplicate, insightful articles that have been submitted so that they can reject them.
Demand to face your accuser in court. If a police officer takes the stand, tell the judge to strike everything he says as hearsay and repeat your request that you face your accuser. If they do bring the camera in, accuse it of being uncooperative by not answering your questions, and ask the judge to jail it for contempt.
Who posts their e-mail address in the main story summary on Slashdot? Mark of THE CITY. That's who.
I bought all my computers, except for the laptop that was a high school graduation gift on account of my college costs being less than zero due to scholarships. As to crashing "their own car," I sincerely doubt that any significant majority of today's teenagers are buying their own cars without any help from mom and dad at all.
Yep. Grammar notwithstanding, that's totally worry-free and friendly stuff, right there.
I agree with you to a large extent. My parents, and my father in particular, treated me as an intellectual equal. They knew when to lay down the law, but frankly they didn't have to all that often because I respected them and they me.
;-D
On a side note, I find American Beauty to be a bunch of self-indulgent crap. But side notes aren't important.
I absolutely agree that children should have a computer in the house. But it should not be their own. That said, this is all getting into arguments about parenting. Can't we argue religion or politics, instead? :P
I credit early exposure to computers for my expertise with them now. I am a more efficient and more effective person because it doesn't take me any real effort to use a computer. Nobody in the generation my kids will be a part of should be deprived of that, but neither should they be deprived of the opportunities to learn pride in hard work and responsibility. Too many kids today are deprived of one or both of these.
Does anyone have the BT link for this? ;-D
Parents who give their children laptops, sports cars, and the like are not treating them as equals. They are treating them more like pets. Moreover, parents who do treat their kids as equals tend to do so by lowering themselves to the kids' level, rather than vice versa. Look at all the parents who party with their teenagers, or the one mother who was caught having sex with all her teenage son's friends at parties she would throw for them. That's what it means to treat your children as equals, for most parents.
And for the parents who really want to treat their children as equals - treat them like adults! If they want a laptop, they should get a job and buy one. That's what an adult would do, unless your vision of adulthood is being a trophy wife.
Bad handwriting is less a sign of laziness than are poor spelling, improper capitalization, improper spacing, improper punctuation, and incomplete sentences.
Thanks for the pointer on the IO2. It looks interesting, at the very least.
I said "on average." I used the term "college kids" for a reason.
I have both a desktop and a laptop. Take either away, and my lifestyle wouldn't work out. I take my laptop to class and take notes (copious notes - 2,000 lines or more of plain text for a semester in one class) on it. I can't read my own writing, and I can type extremely fast, so it works out really well for me. Additionally, I go to the law library and study there most of the time, taking more notes on my laptop. Then I upload them to my desktop (actually, I use Unison to synchronize both machines to a server located elsewhere - nerdiest law student, EVAR) and compile them into study outlines from there.
Try doing any of that with pen and paper, even if you can write fast enough to keep up with the professor and still read your own writing.
As to the actual point of this article - buying laptops for kids in high school or earlier - I am not a fan of the idea, for a lot of reasons. But the one that I'm going to mention right now is this: High schoolers are, on average, less mature than college kids are, and tend to lose and break anything that's remotely portable. It's bad enough that they're out crashing the family car, don't send them out with a $2,000 laptop to bust up, too. Your kids can use your "family PC." Kick them off if you need it. If they want their own computer, they should buy one. It's a really good time to learn priorities and responsibility, and you shouldn't spend money to deprive them of the opportunity.
For a group of people who crucify each other over the correct number of spaces to indent code by, you would think that more attention to detail would be paid when it comes to proper nouns where there actually is a right way and a wrong way to do it.
At least you got over your drinking problem.
I never said you should ignore the spaceflight portion. I only said that the problems we have all occur during the transition parts. Let's simplify the analogy a bit, in fact, and say that procedure calls are expensive and work() itself is cheap. If you can optimize the procedure call (make launch and re-entry safer) without affecting how work() is done, then you should. (Whether you can inline work(), i.e. do all the things you can do in space on the ground, is outside the scope of this discussion.)
Your entire point seems to erroneously rest on the assumption that I meant spaceflight itself should be ignored when solving transition problems. That's not the case at all, and I apologize for misleading you to believe that. The simple truth is that spaceflight is relatively safe, and if you can make getting there and back safer without sacrificing the spaceflight itself and its safety, then you should.
The analogy is sound, if you take note of that one caveat.
Here's an analogy that most here should appreciate:(Forgive the lack of indentation. Ecode sucks donkey balls.) If you were profiling that code, you would focus on optimizing work, because that's where most of the computation time goes. It isn't nearly as helpful to say you're going to optimize foo.
I still want my kids' first words to be "daddy" or even "ugly" than "motherfucker." Call me old-fashioned.
So far no American accidents in space have been fatal. We've had one fire on the pad before liftoff, one explosion during liftoff, and one single-vehicle in-air collision on re-entry. No Americans have died while actually in space, unless I totally missed something.