4 ms·
I learned python first, and I have the same complaint about ruby. When I was attempting to learn ruby, the subtle differences between blocks, procs, and proc.n
by recursive 14y ago
I learned python first, and I have the same complaint about ruby. When I was attempting to learn ruby, the subtle differences between blocks, procs, and proc.news, or whatever they are, seemed arbitrary and required too much thought to understand for my taste. In my brief exposure to ruby, that was symptomatic of a general trend in the language that there seemed to be many ways to accomplish a task, without a clear reason for the distinction. That's fine if you're writing code, but imo that's a feature that makes reading a language more difficult.
- masklinn 14y ago> When I was attempting to learn ruby, the subtle differences between blocks, procs, and proc.news, or whatever they are, seemed arbitrary As well as blocks not being first-class objects. Especially knowing a smattering of Smalltalk, that still feels weird.
- VeejayRampay 14y agoYou don't have to learn every single way to achieve a task though. Just sticking to simple blocks will solve 95% of the issues for you. If you want to get into more detail, Ruby will grow with you. I've sincerely yet to explicitly use lambdas or Procs and I've been coding Ruby through Rails for a few years now.
- recursive 14y agoLike I said, that's fine if you’re only writing code. It doesn't stand up so well if you need to read code also. The author of the code could use any feature the language provides.