4 ms·
Some great stuff here in the comments for you, but don't get caught up in decision paralysis. The truth is no matter which you learn it will create a foundatio
by jwecker 17y ago
Some great stuff here in the comments for you, but don't get caught up in decision paralysis. The truth is no matter which you learn it will create a foundation for you to (if you're interested) pick up other languages and/or frameworks. Get one solidly under your belt. None of the languages/frameworks are perfect- all will have you scratching your head (or banging it on the table) from time to time. Some will be a better foundation than others (Ruby and Python would both be great here).
So don't spend too much more time thinking about it. If you just need someone to just tell you where to dive in so you can really get going here you go: If you have or plan on growing a beard- Python/Django. If you plan on staying clean shaven and dressing smartly- Ruby/Rails. When you've mastered the current choice and have a nice career going, go ahead and master the other(s).
- colbyolson 17y agoI don't understand, why does one need a beard for Python/Django? Is Ruby/Rails more hip?
- ashleyw 17y agoI think he was referring to Rails being very structured, and Django giving you the flexibility to do it your way. It depends on your tastes; I prefer Ruby/Rails.
- jamesbritt 17y agoI don't have (or want) a beard, but prefer Ruby/Ramaze. Luckily, in both Python and Ruby there are many choices for Web dev, so don't let that drive the language choice.
- weaksauce 17y agoI personally think he was being more tongue in cheek than anything. Basically if you need someone to tell you what to do here is an arbitrary metric for you to base your decision off. Beards.