I spent two years at a company where I barely could use Perl on real applications.

I started on a new job last January. It is *only* Perl.

Just trying to get a feel on the situation -- by 'last January', do you mean Jan 2004, or Jan 2005? If it's Jan 2005, I'd agree -- I've flagged short non-contract work as a reason for not hiring someone.

Yesterday I was approached by another company wanting to hire me. They made it clear from the start that my salary would be higher and that I would have everything I would need. (basically, they have 150 employees, and none of them is using Perl ATM; yet, they suddenly realized they need a Perl programmer for a project they've inhereted).

If they're coming to you, you might have more leverage than you think. And the company is small enough, that they might have flexibility in their benefits and other terms.

I'm turning down this offer, for a bunch of reasons (one of them being the fact that I just started this new job and it doesn't feel right abandoning it so soon).

I'm a firm believer in going with your gut feeling. I personally don't like leaving in the middle of a project. But, if someone is specifically coming after you, you might ask them how often the offer is good for, as they might be willing to give you time to wrap up your responsibilities. (and hell, they may even look at that favorably, if they're not in a time crunch)

But the main reason I'm turning it down is this: It's Perl related, but it's not just Perl (actually, I'd say only 50% of it is Perl and the rest is stuff I really don't care about) and I like what I have right now.

You've also made the assumption that the two aren't mutually compatable. If they're trying to recruit you, they might be able to bring you on as a half time employee, or for consultation, etc. (although, there are other issues with consultation, as you're a different class of employee), Obviously, working two jobs may not be practical, if they're located hours apart, and they don't allow telecommuting, and there might be issues with moonlighting at your current job.

The fact that I'd be making extra money sure sounds great, and there is some chance that I'll regret this decision in the future, of course, but I'm actually turning money down for Perl.

I was wondering if there's anyone else here doing this, abdicating from money for doing what they like, that being Perl programming.

I've left well paying jobs, but not because of the tools I was using. (although, I did get fed up with the tools, and had even bought my own laptop, just so I could use my prefered editor) ... and I was later told I was getting paid less than the people slacking off in the department. As much as you like one tool, I don't think it's a reason to leave or stay with a job, as it's being short sighted, to assume that it's always going to be best thing for the job. (I like Perl, but I'm not going to do everything in Perl.) I would say most of the factors in my choice of jobs are, in no particular order:

• comfortable level of pay. (not living paycheck to paycheck)
• enjoying the work. (challenging, but not that sink-or-swim feeling)
• belief in the company's goals. (I prefer to work for education/non-profit)
• commute time. (which is part of the stress issue).
• working with people I get along with. (I don't have to be best friends, but a dumbass manager or co-worker can ruin things)
• learning opportunities. (a chance to learn new things, not just repetitive tasks).

There are probably other things, but these come to mind. Personally, I've left (or been fired from) jobs for personel reasons (in every one of the 4 instances in the last 11 years). However, I'm currently financially well-off, so money isn't a major consideration. I would give up my current job if I could get out of consulting, even if it is long-term consulting, assigned to a government agency.