4 ms·
Agreed. His background is Perl after all, so the idea of 'one way to do something' and 'readable code' is extremely foreign to him. I'd take his advice on progr
by RyanZAG 13y ago
Agreed. His background is Perl after all, so the idea of 'one way to do something' and 'readable code' is extremely foreign to him. I'd take his advice on programming with a grain of salt.
- BugBrother 13y ago"It is a Perl guy, so ignore his opinion" :-) I learned more about you than about Dominus with that comment. Here is a link to his well received book, by the way: http://hop.perl.plover.com/book/ http://hop.perl.plover.com/book/ (But the book you should probably look at to understand the world better, is "Perl best practices".) Edit: fuzzix -- you are certainly right about most useful modern books, I was making a point to what I comment on. The idi.. cough.. Which insinuated that readable code is an unknown concept to typical Perl programmers.
- fuzzix 13y agoI would look at Modern Perl before Perl Best Practices. While Perl::Critic bases much of its criticism on PBP, quite a bit of it turned out to be not so useful.
- RyanZAG 13y agoNo - my statement is pretty clear. Someone who likes Perl is not going to be appreciative of 'one way to do something' and 'readable code'. Those properties are the basis for modern language design and they are properties that most people want in a language. Taking his opinion means also taking his assumption that the properties of Perl ('interesting code') is a good property for a language to have. Hence my advice to take any opinion from a Perl guy as coming from a Perl guy - don't disregard it, but make sure you don't inadvertently put Perl in your language design. Because Perl in your language design is going to give you unreadable code. If you're going to argue that Perl is readable code then I'm going to have to disagree with you extremely after having been in a position to maintain some Perl code before.
- BugBrother 13y ago>>[Perl is not readable] >>after having been in a position to maintain some Perl code before. Sigh... You "supported some code" and know how modern Perl looks like?! :-) Could you carefully explain e.g. the problems with Moose and the latest [syntax] extensions you find on CPAN? To start with. Making wild claims like that without support makes you seem like a language war troll or a complete asshat. To be taken seriously, show that you know what you make such big claims about. Edit: And since you have nothing to say about the subject matter -- what is it in the Python culture that brews such fanatic language war trolls? (I assume you're a Python guy?)
- RyanZAG 13y agoYou do realize you're making this in defense of someone starting a language war, right? You may be in the wrong thread. Or its only bashing a modern language when you're bashing Perl?
- BugBrother 13y ago>>You do realize you're making this in defense of someone starting a language war, right? No, I am questioning your specific claims about things you obviously have no clue about. That was a pathetic attempt to change the subject. I stop waiting for a serious answer from you now. Bye. Edit: And if you're a high schooler, sorry if I'm brusque. There is too much of this language war garbage on HN, I want to keep the quality up.
- scott_s 13y agoIf you want to keep the quality up, then please be more civil.
- BugBrother 13y agoYou're totally correct. I have just been trolled too much. The first few dozens of times I was polite.
- Consultant32452 13y agoTo me I think he's clearly qualified to make all sorts of judgements about Perl. For opinions on Java, I'll look to people who have written well reviewed 500+ page books on Java.