I've noticed for some time that it seems whenever comcast dns is not working (and this is *very* frequent, for periods of 15 seconds to a minute, as often as not), that neither do any other dns servers. I ran a test just now, periodically doing lookups through comcast and through 4.2.2.1, and there appeared to be a very high correlation between failures of the two. At the same time, I was also running a ping out to google, and it never missed a beat.
This would suggest that either comcast is proxying dns traffic, or does some weird traffic shaping on port 53.
If you want to do text templating, but are turned off by JSP, you might want to take a look at Jamon. Jamon templates can received typed parameters, support template inheritance, and a wealth of other features. It's very much inspired from perl's Mason.
(what the hell were they thinking?!) and went downhill from there.
While there are certainly legitimate complaints about overloading the left-shift operator, it is definitely preferable to most of the alternatives. The old printf-family is a set of errors waiting to happen:
printf("Take 20% off\n");// oops printf("Hello %s\n");// oops printf("You owe $%.2f\n", amount);// Lets hope amount is a float.
It would of course be possible to avoid this without overloading by requiring calls like:
Successful open source projects simply do not fork. Why? Because there's no interest and it's way too difficult with large scale software. There is one GNOME, one KDE, one Apache, one Linux kernel, one GNU Compiler Colection, one OpenOffice, etc.
Parsing is expensive. There's a reason why syntax highlighting doesn't go beyond heavy regexing.
It's worth noting that in Eclipse (and from what I gather, most other IDEs), the assistance provided is done not on the basis of a full file reparse each time something new is typed. Rather, the IDE keeps the parse around after the initial parse, and when it notes that a portion of the document has changed, it usually is able to get away with just reparsing a small area around what was changed, and modify it's parse tree accordingly.
I used to try being as anonymous as possible, because, like the poster, I did not want to face the wrath of the spam monster. However, when my work address, which was on published aliases, started getting hunted in earnest by the spam monster, I was finally forced to look into Baysian filters (I chose spamprobe, but there are plenty of other good ones as well). The pleasant surprise was that they work extremely well. So well, in fact, that I've really just stopped worrying about how many spammers get my email address. It's not that the monster is gone, but it is trapped in soundproof box in another room that I never go into. Silly monster.
Employers want experience, not just book learning. However, they aren't (always) particularly picky about whether you got paid while gaining that experince. Need experience in Foo? Find an open source project using Foo that interests you, and start contributing. Something small at first - just a simple patch. After the project maintainers start getting to know you (through your code), they'll likely start letting you contribute in more substantial ways.
I would recommend Jamon, which is for Java what HTML::Mason is for Perl. Rather than "throwing variables over a wall" from java code to templates via a context object (basically a hash map), templates declare themselves to expect certain arguments, which are passed to them from Java code. For example, HelloWorld.jamon might contain:
<%args> String name; </%args> Hello <% name %>!
This would be called from java as
new HelloWorld().render(System.out, "Taco");
Any java types can be passed to a template (primatives and objects). Templates can both inherit from and call other templates. Everything is staticly type-checked at compile time. Automatic template recompilation is supported during development, and in production, no reflection is used.
I personally wouldn't see anything wrong with going after people who download music and/or movies, provided it was done in a reasonable way, instead of trying to use civil courts to bully, intimidate, run roughshod over various rights (fair use, privacy, etc), and so forth.
By contrast, this appears to be a reasonable civil action, taken only after attempts at negotiation have failed.
It's just a shame that JSF is, at least out of the box, built on top of JSP. There are some much nicer alternatives out there (Jamon and Tea come to mind), but the industry seems set on using a tepmlating language with no static type checking, and a poor ability to factor templates.
> You can create servlets using Groovy. ... but you might be happier creating them in Jamon, which lets you combine the convenience of a templating language with all of the type-safety that you would expect in a Java environment.
Pair programming is not only less efficient, it is 4 times less efficient. Every time you interrupt a programmer's train of thought you are losing time more certainly than when he picks up his Coke for a drink.
I've done some pair programming, and I have to disagree here. It's true that the "passenger" will interupt the "driver", but it will not necessarily interrupt the train of thought. Indeed, frequently comments will be along the lines of "why not just do instead?". Moreover, the "passenger" can often help keep track of the big picture, allowing the "driver" to focus on details without getting lost.
This is not to say that pair programming is perfect. For certain drudge work, it's definitely not efficient. Even with two coders who respect each other and get along well, it can be very emotionally draining. But I've almost never felt that my pairing partner and I could have developed *and debugged* code more efficiently by working separately. Indeed, we tended to write remarkably bug-free code when we had a "second pair of eyes".
One thing that I think is necessary for pair programming to work well - both developers need to be as "egoless" as possible. Only when each person can truly listen to and fairly evaluate the others comments while in "the heat of battle" will pair programming work well.
I personally know an individual (a dentist) who has successfully used telemarketing. He employs one woman who works from home cold-calling people to get their teeth cleaned. Telemarketing has been the most successful method of getting new patients that he has ever tried. Additionally, the woman doing the job benefits from well paying at-home employment.
I don't think anyone denies that telemarketing can be effective from a marketing standpoint, or that it generates jobs. That alone isn't enough to justify an activity. The thing is, most dentists who want to drum up business do so by placing adds in yellowpages, on TV, radio or in newspapers. These may yield less customers per dollar spent, but it is a fairer way to reach people - these are all places where people have agreed to receive advertising, because it helps pay for the medium. When someone uses my phone to advertise to me, they are effectively abusing a loophole in the phone system in order to advertise to me at my expense. <<insert obvious spam analogy here>>
The fact that Dave Barry is encouraging people to abuse the same loophole to "harass" telemarketers is precisely his ironic point.
- HTML::Mason
The nicest web application framework I've ever worked with. The development model and application flow is incredibly well thought out. The little "gotchas" wherein one has to do something strange are orders of magnitude fewer than every other framework I've worked with.
Mason is definitely a wonderful templating framework - it has good scoping and excellent support for modularization of content. For those who prefer working in Java, but are not happy with JSP, an excelent templating framework to look at (and one inspired by Mason) is Jamon.
Slashdot Mirror
I've noticed for some time that it seems whenever comcast dns is not working (and this is *very* frequent, for periods of 15 seconds to a minute, as often as not), that neither do any other dns servers. I ran a test just now, periodically doing lookups through comcast and through 4.2.2.1, and there appeared to be a very high correlation between failures of the two. At the same time, I was also running a ping out to google, and it never missed a beat. This would suggest that either comcast is proxying dns traffic, or does some weird traffic shaping on port 53.
If you want to do text templating, but are turned off by JSP, you might want to take a look at Jamon. Jamon templates can received typed parameters, support template inheritance, and a wealth of other features. It's very much inspired from perl's Mason.
This isn't all that different from tempting programmers to write
and expect i to be 9 instead of 7.While there are certainly legitimate complaints about overloading the left-shift operator, it is definitely preferable to most of the alternatives. The old printf-family is a set of errors waiting to happen:
It would of course be possible to avoid this without overloading by requiring calls like:But that is definitely going to cut down on productivity, both in writing and reading code.By contrast, the streams approach taken in c++ is type-safe, extensible, and easy to use. Perfect? No. Better than most alternatives? Absolutely.
Not to mention one Emacs, one XEmacs.
Parsing is expensive. There's a reason why syntax highlighting doesn't go beyond heavy regexing.
It's worth noting that in Eclipse (and from what I gather, most other IDEs), the assistance provided is done not on the basis of a full file reparse each time something new is typed. Rather, the IDE keeps the parse around after the initial parse, and when it notes that a portion of the document has changed, it usually is able to get away with just reparsing a small area around what was changed, and modify it's parse tree accordingly.
I used to try being as anonymous as possible, because, like the poster, I did not want to face the wrath of the spam monster. However, when my work address, which was on published aliases, started getting hunted in earnest by the spam monster, I was finally forced to look into Baysian filters (I chose spamprobe, but there are plenty of other good ones as well). The pleasant surprise was that they work extremely well. So well, in fact, that I've really just stopped worrying about how many spammers get my email address. It's not that the monster is gone, but it is trapped in soundproof box in another room that I never go into. Silly monster.
Employers want experience, not just book learning. However, they aren't (always) particularly picky about whether you got paid while gaining that experince. Need experience in Foo? Find an open source project using Foo that interests you, and start contributing. Something small at first - just a simple patch. After the project maintainers start getting to know you (through your code), they'll likely start letting you contribute in more substantial ways.
By contrast, this appears to be a reasonable civil action, taken only after attempts at negotiation have failed.
It's just a shame that JSF is, at least out of the box, built on top of JSP. There are some much nicer alternatives out there (Jamon and Tea come to mind), but the industry seems set on using a tepmlating language with no static type checking, and a poor ability to factor templates.
> You can create servlets using Groovy.
... but you might be happier creating them in Jamon, which lets you combine the convenience of a templating language with all of the type-safety that you would expect in a Java environment.
check out a satellite phone -- the price has gone down in price.
Note, however, that the price has gone up in quality.
I've done some pair programming, and I have to disagree here. It's true that the "passenger" will interupt the "driver", but it will not necessarily interrupt the train of thought. Indeed, frequently comments will be along the lines of "why not just do instead?". Moreover, the "passenger" can often help keep track of the big picture, allowing the "driver" to focus on details without getting lost.
This is not to say that pair programming is perfect. For certain drudge work, it's definitely not efficient. Even with two coders who respect each other and get along well, it can be very emotionally draining. But I've almost never felt that my pairing partner and I could have developed *and debugged* code more efficiently by working separately. Indeed, we tended to write remarkably bug-free code when we had a "second pair of eyes".
One thing that I think is necessary for pair programming to work well - both developers need to be as "egoless" as possible. Only when each person can truly listen to and fairly evaluate the others comments while in "the heat of battle" will pair programming work well.
I don't think anyone denies that telemarketing can be effective from a marketing standpoint, or that it generates jobs. That alone isn't enough to justify an activity. The thing is, most dentists who want to drum up business do so by placing adds in yellowpages, on TV, radio or in newspapers. These may yield less customers per dollar spent, but it is a fairer way to reach people - these are all places where people have agreed to receive advertising, because it helps pay for the medium. When someone uses my phone to advertise to me, they are effectively abusing a loophole in the phone system in order to advertise to me at my expense. <<insert obvious spam analogy here>>
The fact that Dave Barry is encouraging people to abuse the same loophole to "harass" telemarketers is precisely his ironic point.
The nicest web application framework I've ever worked with. The development model and application flow is incredibly well thought out. The little "gotchas" wherein one has to do something strange are orders of magnitude fewer than every other framework I've worked with.
Mason is definitely a wonderful templating framework - it has good scoping and excellent support for modularization of content. For those who prefer working in Java, but are not happy with JSP, an excelent templating framework to look at (and one inspired by Mason) is Jamon.