Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Perl programmer, using Emacs (Score 1) 359

I use Emacs, mostly. For editing files as root or over SSH I often use vi(m). I still want to switch to vim for all my editing for a few months, just to see if I can get used to it. Don't think I will convert to vim, but I think the only way to get used to an editor (and have non-biased opinion about it) is to use it for a few months (and RTFM, of course). On Windows, several years back, I used TextPad mostly.

Comment Re:Books like.... (Score 2) 283

A lot of best practices for Perl are good programming practices in general. Of course there are (plenty) of exceptions, but that's the case with other languages as well. One thing one wants to avoid is to program Python in Haskell or Pascal in C, for example.

As for hard to read (for a beginner) have a look at Haskell, for example.

Python's fame is that it "reads like pseudocode". That's nice, but utterly fails if a programmer has no good feel for algorithms. Pascal used to have the same fame. A few years back I had to reimplement a Pascal program into Perl. One of the pieces of code was 100+ lines. After some studying it turned out to be a variant of bubble sort. At the end few lines reversed the sort order (!). It could be replaced with a few lines of Perl. And no, not because I write short and cryptic code. The code could've been written way shorter in Pascal as well, even when implementing a sort manually.

Comment Re:Yes, Perl is indeed dead and rotting (Score 2) 283

Same here. I am a freelance Perl programmer and for the past 12+ months have been very busy with coding in ... Perl. More so than when Perl was considered the "glue that holds the web together". And no, it isn't maintenance of old code.

A number of people who left Perl and declared it dead are the ones that couldn't program in Perl to begin with (never learnt the language, thought it could be learned by trial and error), and most likely still can't in whatever they consider fashionable right now.

Comment Re:Bugger (Score 1) 61

My disaster plan is keeping track of each apt-get install xxxxx and write down how I configured what I installed afterwards. And then there are still surprises, like how Apache changed its defaults going to 2.4 (IIRC). It's a lot more work compared to install new version and rsync -avh from backup, but all those notes I keep come in handy when I have to install something for a customer in a VM, etc.

Comment Re:Bugger (Score 1) 61

Ah, yeah, should. In my experience the safe way, however, is to have taken notes during the previous install, doing a fresh install, and install and configure everything using those aforementioned notes (which now and then requires some research to get it right due to changes, and hence updating notes). Of course photos, movies, music, etc. can be safely restored from backup.

Slashdot Top Deals

Make sure your code does nothing gracefully.

Working...