Hey lets get rid of the PC's we bought for 500 bucks 2 years ago and replace them with $2000 Macs! We'll save a ton of money on... umm.. Yay they match the decor in the computer room!
You'll save money on support (Macs cost less to support), and on eventual replacement costs (Macs have historically had a longer usefull life), amoung others.
Still, I agree with your point. Replacing all their computers right now just to get this grant probably isn't worth it. They might want to replace a few, and maybe start transtioning other computers to linux/unix. Hopefully they wounldn't have to give up MS overnight. Like any addiction, going cold turkey brings withdrawall pains.
With such a huge disparity in boot times, you can only assume the rest of the OS functions (or disfunctions) proportionately. For example, I can assume that if it takes 0.2 seconds to load Office XP on Windows XP, it will take over a minute longer on RedHat. Oh, that brings me to my next point:
Nope, you can't. If the boots did the same things in the same order you could make that assumtion, but then it would be the same OS. Also, you didn't mention if this was a first start up (keygeneration runs), or if fsck ran...
You can't run Office XP on RedHat.
That's a feature. Trust me.
I shouldn't be writing this, but I can't mod you to oblivion, so...
My guess is that a copyright only protects that particular set of pixels. Apple's (and other) desktops are rapidly gaining scaling and other functions, and the design patent probably allows them more flexibility with protecting the look of their trashcan. I mean, if MS were to implement an inverse vector algorithm or something they could probably argue that they didn't copy Apple's stuff, but they did copy the design. This protects that.
Can't mail servers become more intelligent, after all who sends 100 emails a day in one big batch from a hotmail account?
My mother. That's how long her general address book is, and on occasion she has major news that she puts out to everybody. (When she moves for instance.)
Different problem. The 'mythical man month' problem deals with how a coordinated group effort to solve a serial (or semi-serial) problem can't just be solved by throwing people at it; the coordination and deserialization muck things up. This deals with finding a solution to either a single-node problem or a parallel problem, using massive *uncoordinated* effort. Since the problem does not have to be deserialized, and the results do not have to be coordinated, the affects never come up.
Not that you can actually implement the full functionality of standard HTML tables in CSS.
You're not supposed to: HTML tables still exsist, and can be manipulated via CSS. Just don't use tables when the data isn't tabluar... (Like using it for layout.)
There are a few table-based layouts that you cannot duplicate with CSS, but very few, and there would be less if certain browsers *cough*IE*cough* would fix their CSS support.
They seem to follow them exactly: if you say they included everything but (...) they include the (...) Imagine if someone had said it includes everything but an atomic bomb! Do you really want them giving out atomic bombs? Be careful!
No, you wouldn't, and not just because/. is a bunch of Linux zealots. The fact that he is using a Linux only computer *is* interesting, because most don't regard Linux as ready for that. Even most of the people on this site probably keep a Windows partition around for some things. Everyone knows you can run only Windows if you want; saying that would only be fishing for trouble.
It's an interesting comment. The other way is a valid troll.
My guess is he means Apple's 'command' key. Though I'd like to know what he is doing if he never uses it. It's used for the keyboard shortcuts: copy, paste, quit, switch programs...
Ok, mostly true, but there are some reasons to have a private jornal publicly accessable.
Try this: I write to and read my journal from home, work, or on the road. The work firewall has a habit of disconnecting SSL conections occasionally. And on the road I'm never sure what type of connection I will find.
There's nothing private in the journal, so I don't mind if others read it. Still, Google hasn't found it yet, and I doubt anyone else has. It's public so I can see it easily. Also, the blog software (I use Blosxom) helps me organize my thoughts: I can catagorize, and it keeps track of the dates for me.
I've checked my blog from the machine it's hosted on instead of just reading the file. It's easier. Public, to me, == easier to find and use. That's all. I can refer to it from any computer with an internet connection. That's useful to me, and why I set it up. If anyone else sees it (or not) I don't care.
I've had the unfortunate experiance of having people forward spam to me so that I can tell them if it is possible or not. Managed an 11, after the auto-whitelist reduced it. Family, so I couldn't just ignore the idiot.
Agreed, though SpamAssassin has one feature that is real usefull for this: the score is embedded in the email header in a row of '*'. This can be used to reduce the amount of skimming you have to do: I find I never get a false positive that rates above 13, so I/dev/null (or uce@ftc.gov) everything above that, and skim the rest. This gets rid of the worst spam without my intervention, and reduces the amount I need to skim to 10-20 messages a day.
It is in fact blaming the victim for the software's flaws. Maybe this will turn microsoft more towards making sure their products are more secure from the start if this info gets around enough. Yes, I know Billg's "Trusted Computing" plan is rather new, but they sure seem to get caught with their pants down often.
Ok, but given that the current generation of software has flaws, other than telling customers to install the patches, how are they supposed to fix problems?
Not that I use Microsoft software anywhere I can avoid it, but your comment is more generally applicable.
You'll save money on support (Macs cost less to support), and on eventual replacement costs (Macs have historically had a longer usefull life), amoung others.
Still, I agree with your point. Replacing all their computers right now just to get this grant probably isn't worth it. They might want to replace a few, and maybe start transtioning other computers to linux/unix. Hopefully they wounldn't have to give up MS overnight. Like any addiction, going cold turkey brings withdrawall pains.
15 calls, at two minutes a call, is an extra 30 minutes.
Figure an hour-hour and a half for a 'normal' dinner.
And maybe an extra minute of 'distrubance' time for each call...
Three hours sounds fairly close, actually.
RadioShack telephone recorder: $80
Recording medium: $1.50
Legal evidence in a court of law: priceless.
(Just be sure you, or they, mention that the call is being recorded... Not nessisary in all states.)
But the cost of the call itself would then be a limiting factor. Or haven't you priced a call to Bombay recently?
Safari's got that ;-).
You know, I think I agree. Well, execpt the want to die part.
Ok, I'll feed the Troll...
Nope, you can't. If the boots did the same things in the same order you could make that assumtion, but then it would be the same OS. Also, you didn't mention if this was a first start up (keygeneration runs), or if fsck ran...
That's a feature. Trust me.
I shouldn't be writing this, but I can't mod you to oblivion, so...
That's either demoware or shareware, depending on you definitions. Many companies do this.
My guess is that a copyright only protects that particular set of pixels. Apple's (and other) desktops are rapidly gaining scaling and other functions, and the design patent probably allows them more flexibility with protecting the look of their trashcan. I mean, if MS were to implement an inverse vector algorithm or something they could probably argue that they didn't copy Apple's stuff, but they did copy the design. This protects that.
But hey, IANAL, so what do I know.
My mother. That's how long her general address book is, and on occasion she has major news that she puts out to everybody. (When she moves for instance.)
Hmm, I like it. The 'Government Security Program'. Presumably 'Secure' in the same way Palladium is 'Trusted'.
Different problem. The 'mythical man month' problem deals with how a coordinated group effort to solve a serial (or semi-serial) problem can't just be solved by throwing people at it; the coordination and deserialization muck things up. This deals with finding a solution to either a single-node problem or a parallel problem, using massive *uncoordinated* effort. Since the problem does not have to be deserialized, and the results do not have to be coordinated, the affects never come up.
You're not supposed to: HTML tables still exsist, and can be manipulated via CSS. Just don't use tables when the data isn't tabluar... (Like using it for layout.)
There are a few table-based layouts that you cannot duplicate with CSS, but very few, and there would be less if certain browsers *cough*IE*cough* would fix their CSS support.
Correctly word your bug reports!
They seem to follow them exactly: if you say they included everything but (...) they include the (...) Imagine if someone had said it includes everything but an atomic bomb! Do you really want them giving out atomic bombs? Be careful!
Of course, they also say that in "Indiana Jones and the Last Crusade". ;-)
You only tell the admins about unexpected occurences. This is normal operating procedure.
No, you wouldn't, and not just because /. is a bunch of Linux zealots. The fact that he is using a Linux only computer *is* interesting, because most don't regard Linux as ready for that. Even most of the people on this site probably keep a Windows partition around for some things. Everyone knows you can run only Windows if you want; saying that would only be fishing for trouble.
It's an interesting comment. The other way is a valid troll.
My guess is he means Apple's 'command' key. Though I'd like to know what he is doing if he never uses it. It's used for the keyboard shortcuts: copy, paste, quit, switch programs...
What country are you living in? The people Congress fears the most are those pay for their ad campaigns.
Ok, mostly true, but there are some reasons to have a private jornal publicly accessable.
Try this: I write to and read my journal from home, work, or on the road. The work firewall has a habit of disconnecting SSL conections occasionally. And on the road I'm never sure what type of connection I will find.
There's nothing private in the journal, so I don't mind if others read it. Still, Google hasn't found it yet, and I doubt anyone else has. It's public so I can see it easily. Also, the blog software (I use Blosxom) helps me organize my thoughts: I can catagorize, and it keeps track of the dates for me.
I've checked my blog from the machine it's hosted on instead of just reading the file. It's easier. Public, to me, == easier to find and use. That's all. I can refer to it from any computer with an internet connection. That's useful to me, and why I set it up. If anyone else sees it (or not) I don't care.
Ahh! Success! An easy to use system at last!
(I really did like the Apple II. Especially the IIGS. Macintosh just about caught up in System 8.)
I've had the unfortunate experiance of having people forward spam to me so that I can tell them if it is possible or not. Managed an 11, after the auto-whitelist reduced it. Family, so I couldn't just ignore the idiot.
At least it was easy to debunk.
Agreed, though SpamAssassin has one feature that is real usefull for this: the score is embedded in the email header in a row of '*'. This can be used to reduce the amount of skimming you have to do: I find I never get a false positive that rates above 13, so I /dev/null (or uce@ftc.gov) everything above that, and skim the rest. This gets rid of the worst spam without my intervention, and reduces the amount I need to skim to 10-20 messages a day.
Ok, but given that the current generation of software has flaws, other than telling customers to install the patches, how are they supposed to fix problems?
Not that I use Microsoft software anywhere I can avoid it, but your comment is more generally applicable.