With a web app, you also download your code with every single page. Graphics. HTML. Javascript. Every single time. Yeah, or you could try caching stuff locally on the client machine. This can easily be done with expire-tags or similar. I'd also considering using inline CSS and JavaScript instead of linking them in externally as files. Surely this will reduce the network load. One could also use AJAX where applicable in order to keep pages from refreshing too often. This would also make the app quite snappy. Nope, you're definitely thinking backwards. Go ahead and use inline CSS and JavaScript during initial development, because it's simpler to debug, but once that's done, put it in a separate file. You're correct that there will initially be more overhead because the browser has to make several different connections to download each file, but these are all static files. The browser will cache them locally, and when you go to a different page that uses the same CSS or JavaScript code, the browser will just use its local copy, instead of requesting those files again. The browser may ask the server for information about the files, and compare their last-modified timestamp to the date on the files in the cache, then only reload if the file has changed.
Another thing the grandparent mentioned is that "you download your code with every single page", and while this is true of the HTML component of it, the actual logic that runs behind the scenes is not downloaded, and depending on what you're doing, that could be quite a bit larger. For example, I've got about 3,000 lines of Perl code to generate my home page (not because it needs to be that complicated, but because I was bored, and kept adding new features, because I could - it's my personal site, I can to do that if I want). That's not including the actual content.
You're absolutely right about browser compatibility. It was a problem 5-10 years ago; the problem is now mostly solved. Write valid HTML and check it with the W3C Validator, and it'll work on pretty much anything. CSS is a huge pain in the ass (the CSS validator doesn't help, because your errors are still valid code, they just don't do what you meant), but maybe you can hire somebody to build that for you. Sure, you may run into glitches here and there, and you should test all of your CSS and JavaScript in at least Firefox, Opera, Safari, IE6 and IE7, but compare that to testing a GUI application in WinXP and Vista, plus Mac OS X and Linux if you build for those platforms as well.
You really see no difference between a) dying and b) living forever in a paradise? Presumably he meant, what benefits are there to the believer BEFORE death (and in particular, before procreation)?
Yes, in your case, you're correct. Still, the parent poster is also correct - spammers definitely do use dictionary attacks. No web site is required; they use lists of registered domains, without bothering to look for a web site (although if you have a web site, they'll also spider it looking for e-mail addresses).
Check your logs. If you run Sendmail, grep for "User unknown" (I'm not familiar with other MTAs).
"Give beer to those who are perishing, wine to those who are in anguish; let them drink and forget their poverty and remember their misery no more." Proverbs 31:6-7 (NIV)
I defy anyone to find a better passage to take out of context.
However, right of first sale doesn't apply in the same way to computer software or musical works as it does to books. Then how is my local public library able to offer computer software and musical works?
That's interesting, I've been with Cingular for about a year and a half and haven't had a problem. I honestly don't remember for sure if I've ever gotten spam from them - if I have, it certainly hasn't been more than 3 or 4 times, total.
but hey, that is not my country so fuck it up as much as you wish, as long as you keep a sane foreign policy of "hand off".... Um, yeah, we'll uhh, get right on that.
Exactly how does iTMS drive iPod sales? Simple: some people want the convenience of being able to buy music online. Assuming Apple didn't license Microsoft's WMA DRM, if the iTMS didn't exist, it would not be possible for iPod users to play music they bought online, thus making the iPod less attractive to people who want to be able to buy music online.
This sounds like another reason we should hop on the Open Source file formats. With this ruling, you can't even pay the man for licensing, lest there be another "submarine license" for more money. Man, who wants to make MP3 encoders now? Doesn't matter. Opening the source code won't protect you from submarine patents. Ogg Vorbis might be covered by a patent, that the people who created Ogg Vorbis aren't even aware of, and whoever owns that patent could sue you for infringement, and win.
Have you tried Learning Perl on Win32 Systems? Windows users wouldn't benefit from the Minimal Perl approach, because they don't have the background it builds on. This book starts at the beginning.
It's a matter of some puzzlement to me that the loathesome homunculous that is PHP supplanted Perl as the preferred language for non-ASP web programming. PHP is friendlier for beginners in two important ways: first, perl borrows heavily from existing C and UNIX syntax; anyone who already knows C and wants to calculate tomorrow's date will feel right at home with localtime(), but the newbie will find PHP's date functions far easier, for example. Also, perl's syntax is vastly more complex than PHP's, and language syntax isn't something you can just look up in a reference when you're not sure what something does. In PHP, once you learn the basics, anything you see that you don't understand, you can just look up the function name. In Perl, when you see something you don't understand, chances are you don't even know what you're looking at.
What are the chances that Norton Internet Security will uninstall itself gracefully via the Add/Remove Programs control panel? (I certainly plan to set a System Restore checkpoint before trying it!) Try that first, but if it doesn't work, SymNRT (download) is the answer.
ClamWin doesn't scan files in real-time as they come in; you can set it to run a full scan every night or something, but that's not really ideal.
My personal recommendation, which others will certainly disagree with, is to run Norton AntiVirus without any of the other Symantec/Norton crap. Google makes a 6-month trial of NAV available as part of Google Pack. I suggest that after your current 6-month trial expires, you uninstall all your Symantec/Norton software, re-enable the Windows Firewall, and use Google Pack to install Norton AntiVirus. After 6 months of that, if you're satisfied with the results, you can choose to either uninstall it and reinstall it for another 6-month trial period, pay Symantec to renew it, or (the best option) go out and buy NAV 2007 (just NAV, not SystemWorks or Internet Security or anything else, even if they try to give you the rest for free).
If neither of the employees having sex on a desk had been warned by IBM for similar previous violations, the cases may be quite distinct on that fact alone. Yeah, that's what I was just thinking - IBM claims that this guy got caught a few months ago and was warned that if it happened again, he could be fired. It happened again, and he was fired, just like they said. So, maybe with the couple that was having sex, it was the first time, and in addition to being transferred, they were also warned that they could be fired if it happens again, but it hasn't happened again, and that's why they haven't been fired.
If that couple had been previously warned, and were transferred (instead of fired) on the second offense, then this guy has a case. If that was their first offense, then he's got nothing.
Slashdot Mirror
Yeah, or you could try caching stuff locally on the client machine. This can easily be done with expire-tags or similar. I'd also considering using inline CSS and JavaScript instead of linking them in externally as files. Surely this will reduce the network load. One could also use AJAX where applicable in order to keep pages from refreshing too often. This would also make the app quite snappy. Nope, you're definitely thinking backwards. Go ahead and use inline CSS and JavaScript during initial development, because it's simpler to debug, but once that's done, put it in a separate file. You're correct that there will initially be more overhead because the browser has to make several different connections to download each file, but these are all static files. The browser will cache them locally, and when you go to a different page that uses the same CSS or JavaScript code, the browser will just use its local copy, instead of requesting those files again. The browser may ask the server for information about the files, and compare their last-modified timestamp to the date on the files in the cache, then only reload if the file has changed.
Another thing the grandparent mentioned is that "you download your code with every single page", and while this is true of the HTML component of it, the actual logic that runs behind the scenes is not downloaded, and depending on what you're doing, that could be quite a bit larger. For example, I've got about 3,000 lines of Perl code to generate my home page (not because it needs to be that complicated, but because I was bored, and kept adding new features, because I could - it's my personal site, I can to do that if I want). That's not including the actual content.
You're absolutely right about browser compatibility. It was a problem 5-10 years ago; the problem is now mostly solved. Write valid HTML and check it with the W3C Validator, and it'll work on pretty much anything. CSS is a huge pain in the ass (the CSS validator doesn't help, because your errors are still valid code, they just don't do what you meant), but maybe you can hire somebody to build that for you. Sure, you may run into glitches here and there, and you should test all of your CSS and JavaScript in at least Firefox, Opera, Safari, IE6 and IE7, but compare that to testing a GUI application in WinXP and Vista, plus Mac OS X and Linux if you build for those platforms as well.
Oh yeah, and also, by default ntpd won't accept a one-hour jump; it will assume something has gone wrong and won't accept the new time.
No, because then anything that uses UTC will be wrong, which might be worse than having the displayed time be wrong.
Because then everyone would have passports, and then everyone could visit another country more easily, and we can't have that!
NTP only synchronizes UTC. Your timezone is an offset from that, which has nothing to do with NTP.
If you run NTP, you still need a patch, or your clock will be wrong, by precisely one hour.
Yes, in your case, you're correct. Still, the parent poster is also correct - spammers definitely do use dictionary attacks. No web site is required; they use lists of registered domains, without bothering to look for a web site (although if you have a web site, they'll also spider it looking for e-mail addresses).
Check your logs. If you run Sendmail, grep for "User unknown" (I'm not familiar with other MTAs).
On IRC
"Give beer to those who are perishing, wine to those who are in anguish; let them drink and forget their poverty and remember their misery no more."
Proverbs 31:6-7 (NIV)
I defy anyone to find a better passage to take out of context.
I'm not sure I want them to pirate anything else after being told my changed copy was genuine.
That's interesting, I've been with Cingular for about a year and a half and haven't had a problem. I honestly don't remember for sure if I've ever gotten spam from them - if I have, it certainly hasn't been more than 3 or 4 times, total.
Thank you.
Best remake EVER
Perl:
foreach my $key (reverse keys %foo) {
print "$key = $foo{$key}\n";
}
PHP:
foreach (array_reverse($foo) as $key => $value) {
print "$key = $value\n";
}
Software patents are a huge problem.
Did you mean to say there's no joy in PHP?
SymNRT (download) will remove all the remaining bits and pieces of whatever Symantec/Norton crap is still there.
Have you tried Learning Perl on Win32 Systems? Windows users wouldn't benefit from the Minimal Perl approach, because they don't have the background it builds on. This book starts at the beginning.
#!/usr/bin/perl
($n,$s)=('phroggy',join'', map{(sort split'','b_jl msepr$hyacn"otg.')
[$_]}map ord()-97=>split'' =>'shfmfrajitkpstguofniabcedlfqkdcodhpnb')
and print eval $s for(0..6);
What are the chances that Norton Internet Security will uninstall itself gracefully via the Add/Remove Programs control panel? (I certainly plan to set a System Restore checkpoint before trying it!) Try that first, but if it doesn't work, SymNRT (download) is the answer.
ClamWin doesn't scan files in real-time as they come in; you can set it to run a full scan every night or something, but that's not really ideal.
My personal recommendation, which others will certainly disagree with, is to run Norton AntiVirus without any of the other Symantec/Norton crap. Google makes a 6-month trial of NAV available as part of Google Pack. I suggest that after your current 6-month trial expires, you uninstall all your Symantec/Norton software, re-enable the Windows Firewall, and use Google Pack to install Norton AntiVirus. After 6 months of that, if you're satisfied with the results, you can choose to either uninstall it and reinstall it for another 6-month trial period, pay Symantec to renew it, or (the best option) go out and buy NAV 2007 (just NAV, not SystemWorks or Internet Security or anything else, even if they try to give you the rest for free).
If that couple had been previously warned, and were transferred (instead of fired) on the second offense, then this guy has a case. If that was their first offense, then he's got nothing.