'think highly' => sentiment
this post.958 karma · joined March 9, 2014
'think highly' => sentiment
this post.Nonetheless the thinness of the book and the foreword about applications and real world math are very promising. Maybe I should try it out. Any thoughts from someone who has read it?
1. You can use virtually any language to write clean code
Not sure if I agree with this, though it may well be true. I just know there are some things like Brainfuck where it's designed to be impossible. I realize that language is created specifically for the purpose of making a coder say "WTF", but perhaps there are other languages that are not designed to be so that are really nearly impossible to write good code in.
2. Perl lends itself to unreadable code
If you stick to Modern Perl you still might end up with things like `wantarray` in your code so I guess this is kind of true. You need to be judicious in your use of code.
Some languages lend themselves more easily to writing clean code, like I feel about Go or if you hate the Go type system, Ruby. Even in Ruby I feel like metaprogramming is ripe for misuse.
It's a tough thing to talk about. I don't feel like I wholeheartedly disagree with your sentiment which seems to be "some languages lend themselves to bad code" and subsequently that Perl lends itself to bad code but there is plenty of ambiguity in these thoughts.
To quote myself from a recent discussion:
I think some languages do make it easy to write convoluted code, but through judicious use of coding standards (including a helping of common sense [don't be clever where you can at all avoid it, which IME is ~~almost~~ all the time], code linters, and so on) I think how you use a language plays a huge part in code maintainability.
For instance, I've heard PHP get shit on pretty badly all around the web, but I've worked at PHP shops that had nice, clean codebases, and my current Perl codebase is, in many ways, nicely structured. That's not to say there aren't some hairy codepaths that could use refactoring, but I really think that kind of thing, again, can happen in almost any language.
> This beloved guide is now completely updated for Perl 5.22.
I've been working with Perl since about 5.20 and am on 5.31 or 5.32 and haven't noticed many breaking changes FWIW.
:D
Basically, I think of it as a "geowiki" - a wiki where each entry has an address and a lat/lng associated with it. Here's a screenshot: https://i.imgur.com/RiCiuDi.png
I went on the radio on a call-in show, I advertised it on the local city Reddit and their discord server, but it didn't catch on - at all. Except for a couple of vandals who deleted all the entries :)
It was fun, but it would have been a lot more fun if people had actually used it. I still might try to get it off the ground again, but I don't know how off the top of my head.
[1] What does disaster ready mean? It means that the site uses very little resources for the browsing operation. It is all static HTML/JS/CSS and uses cgi-bin (!) for the admin side/adding a new listing.
For instance, I've heard PHP get shit on pretty badly all around the web, but I've worked at PHP shops that had nice, clean codebases, and my current Perl codebase is, in many ways, nicely structured. That's not to say there aren't some hairy codepaths that could use refactoring, but I really think that kind of thing, again, can happen in almost any language.
Modern Perl using Moose is pretty nice to develop in. I find it much easier to express things in Perl than in Go, but I am not an expert in either language despite having several years practice with the former and a couple of years with the latter.
http://modernperlbooks.com/books/modern_perl_2016/
I'd say the biggest issue with Perl is that modules on the CPAN are slowly going stale, and that my understanding is that there is a lot of Perl (C) and XS (C FFI) code that is not actively maintained or necessarily properly developed (including, I believe, parts of the Perl runtime itself). This can lead to segfaults with who knows what behavior.
Take this with a grain of salt: I've never been a good C programmer.
An aside: one of my coworkers is a founder of MetaCPAN, which is a great site.
nchelluri@grugbarn:~/dev/hello $ cat > hello.go
package main
import "fmt"
func main() {
fmt.Println("hello world")
}
nchelluri@grugbarn:~/dev/hello $ go build
nchelluri@grugbarn:~/dev/hello $ strip hello
nchelluri@grugbarn:~/dev/hello $ ./hello
hello world
nchelluri@grugbarn:~/dev/hello $ du -h
1.4M .It's like a step-by-step guide to solving your problem.
Unfortunately, all of the IRC logs I used to browse went offline with GDPR. GDPR, California's privacy act, etc. are all well-meaning but IMO poorly implemented.
I'm currently using an X1 Carbon ThinkPad Gen 4 with a 4K screen and it is pretty nice too. It's a step up both performance wise and size wise from the MacBook.
makes sense, intuitively. if you can go play and explore, the memories will reflect it. hide and seek, tag, capture the flag, scrimmages of hockey/basketball/football/soccer will take place. this is a fundamentally fertile area for a young brain to take intellectual nourishment from its environment.