Why Go? Use Racket

Re:Why Go? Use Racket by vvpan on Thursday March 12, 2015 @03:09PM (#9193033)

It's a chicken and egg problem, but the real reason for me to use Go vs Racket is that learning the former will further my career significantly, while latter won't at all. Sad, but true.

[ Parent | on HN ]

Re:Why Go? Use Racket by sheepmullet on Thursday March 12, 2015 @04:28PM (#9193635)

It is incredibly sad and reflective of a broken industry.

One of the major advantages of Go is that it is easy to learn for existing programmers as there are very few different abstractions/features.

Yet plenty of companies are now requiring prior experience in Go, erasing most of the benefits of using Go.

[ Parent | on HN ]

Re:Why Go? Use Racket by sheepmullet on Thursday March 12, 2015 @05:07PM (#9193928)

...use your words... not your down votes

[ Parent | on HN ]

Re:Why Go? Use Racket by michaelsbradley on Thursday March 12, 2015 @03:45PM (#9193289)

It depends. Learning Racket and the design methodology taught by Felleisen, et al. could help you become a better programmer in general, and thus significantly further your career.

How to Design Programs, Second Edition

http://www.ccs.neu.edu/home/matthias/HtDP2e/

[ Parent | on HN ]

Re:Why Go? Use Racket by vvpan on Thursday March 12, 2015 @04:38PM (#9193715)

Sure, I agree. But the impact is much less direct. Most interviews go like this: "Have you worked with Angular?". And you just don't really need to be a very good programmer to have a well-paying job.

[ Parent | on HN ]

Re:Why Go? Use Racket by kod on Thursday March 12, 2015 @03:51PM (#9193331)

I'd certainly be much more likely to hire someone who had worked through How To Design Programs

[ Parent | on HN ]