Recovering interrupter with occasional relapses, lover of spreadsheets, blogger, programmer, adept debugger, conjurer of analogies, and probably other things.
Ruby has an elegant syntax and allows for very expressive DSLs. Look to various languages that have cribbed RSpec syntax, even those fail to match the expressive DSL. All of which is to say there's something envious about Ruby
Further, Ruby on Rails is an amazing tool for moving from prototype to product.
It's also a language that trusts the programmer (which is a blessing and a curse). You can go so far as to re-open a class to adjust implementation details. (Very similar to advising functions in emacs lisp and I believe other lisps). You could go so far as to store Ruby class defs (or modules) in a database and mix those into your running application. (Is that a good plan? Probably want to not give just anyone that power.
I see Ruby as the child of Lisp and Smalltalk with an upbringing by Perl. Lisp and Smalltalk come from a theoretical era, when computational power was expensive. They are both thought exercises in what could be. And Ruby benefits from their endeavors and presents itself in the vein of a C-based language, meaning it uses the same-ish declaration syntax as many languages (Python, JavaScript, etc).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ruby has an elegant syntax and allows for very expressive DSLs. Look to various languages that have cribbed RSpec syntax, even those fail to match the expressive DSL. All of which is to say there's something envious about Ruby
Further, Ruby on Rails is an amazing tool for moving from prototype to product.
It's also a language that trusts the programmer (which is a blessing and a curse). You can go so far as to re-open a class to adjust implementation details. (Very similar to advising functions in emacs lisp and I believe other lisps). You could go so far as to store Ruby class defs (or modules) in a database and mix those into your running application. (Is that a good plan? Probably want to not give just anyone that power.
I see Ruby as the child of Lisp and Smalltalk with an upbringing by Perl. Lisp and Smalltalk come from a theoretical era, when computational power was expensive. They are both thought exercises in what could be. And Ruby benefits from their endeavors and presents itself in the vein of a C-based language, meaning it uses the same-ish declaration syntax as many languages (Python, JavaScript, etc).