4 ms·
You don't have to go to a 'research' programming language to find one bursting with opportunity for enlightenment. Ruby offers a path to that just as it offers
by vinceguidry 12y ago
You don't have to go to a 'research' programming language to find one bursting with opportunity for enlightenment. Ruby offers a path to that just as it offers a useful career. Its object model is a sight to behold, a thing of sublime beauty. Everything that should be an object is an object, you can treat code as data almost as fluidly as you can in the homoiconic Lisp dialects.
It's got the solid library support you need to code at whatever level of abstraction you're inclined to do in your domain, and the possibilities for refactoring and metaprogramming are just limitless.
You don't have to compromise when you use Ruby, so long as you're not in a domain that requires cutting-edge performance, Ruby will take care of whatever it is you need to take care of while preserving the ability to abstract, redefine, and redesign.
Ruby is the ultimate in object-oriented languages, every law and technique invented by greybeards in the seventies works better when done in Ruby. Lots of design patterns that require overly verbose naming and hideously unreadable and hard-to-maintain implementations in other languages have eminently readable idiomatic expressions in Ruby as well as clear paths to refactoring to them.
Ruby's biggest weakness is not a Ruby weakness at all, it's the fact that gradual typing hasn't been well-defined mathematically yet enough to be able to usefully include it in Ruby. Once it has, I think Ruby will be the go-to option for just about everything save embedded applications. I can't think of anything that would make my life more awesome than being able to easily refactor to static typing.
- plinkplonk 12y ago"Ruby is the ultimate in object-oriented languages," There is this small thing called smalltalk. With that said, claiming Ruby is the ultimate 'enlightenment language' is a little mindboggling. I vote for javascript ;-) That said, it is a great article. Matt Might writes very well and has a lot of insight. Fwiw he doesn't include Ruby in his list of advanced languages, but does call it a 'hot' language.
- vinceguidry 12y agoI didn't say it was the ultimate enlightenment language, I said it was the ultimate object-oriented language. There's no such thing as an ultimate approach to enlightenment. Smalltalk's nice, but Ruby's nicer. There's a reason one's more popular than the other.
- deleted 12y ago[deleted]
- pjmlp 12y agoSmalltalk was already out of the scene when Rails happened, nothing to do with Ruby features.
- rimantas 12y ago> nothing to do with Ruby features. How about this part: > Its creator, Yukihiro “Matz” Matsumoto, blended parts of his > favorite languages (Perl, Smalltalk, Eiffel, Ada, and Lisp) > to form a new language that balanced functional programming > with imperative programming. Taken from https://www.ruby-lang.org/en/about/ https://www.ruby-lang.org/en/about/ . Being out of the scene does not mean that it could no longer inspire.
- Igglyboo 12y agoYes and that reason is Rails, not because ruby is more "enlightened" than smalltalk.
- vinceguidry 12y agoWhy didn't they write Rails in Smalltalk?
- rdc12 12y agoArgument based on popularity doesn't prove your notion, it is nothing other then the fact that it is popular. https://yourlogicalfallacyis.com/bandwagon https://yourlogicalfallacyis.com/bandwagon
- mattgreenrocks 12y agoEnlightenment comes from exposure to alternate paradigms and being forced out of your comfort zone. When you must do without, you will learn, and you will be ready to rely on alternate approaches to problems. Example: I thought I understood the importance of decoupling policy from implementation, but Haskell reminds me frequently that I often overlook this detail when hacking. Rather than tying the side effects (send this HTTP request) to the algorithm that produces what I need to send, I should split them apart, and have a tiny bit of glue code for them both. It's also worth examining and trying out a particular language community's values to see if they mesh with yours. I found it hard to stay with the Ruby community because of certain stances that are made concerning program design. Everything seems tailored for easy, rather than simple. I learned a lot from Ruby, but I never found the metaprogramming/DSL creation to be particularly inspiring. I've made some pretty wacky/cool stuff with it, I just got bored with it ultimately -- it felt like it was piling more things on for people to learn, rather than actually abstracting things away.
- vinceguidry 12y ago> I never found the metaprogramming/DSL creation to be particularly inspiring. I've made some pretty wacky/cool stuff with it, I just got bored with it ultimately -- it felt like it was piling more things on for people to learn, rather than actually abstracting things away. DSL creation is all about firming up your domain model. If all you're doing is shifting complexity around, then sure, you won't get anything from the easy refactoring/metaprogramming. But if you're gradually learning more and more about how concepts work outside of programming and inside the underlying business, (Ruby works best when you're supporting a revenue-generating business rather than something more abstract) then you're actually getting somewhere. So what you do is you leave your complex methods where they are and think really hard about exactly what it is you're trying to do, what semantics you need to have. Then when you do refactor/redesign, the language you're using to create your classes isn't arbitrary, it's well-thought out and reflective of something that is needed. Ruby does seem tailored for easy rather than simple, I'll give you that. But you don't have to accept that lying down. Simplicity is well within the ability of the programmer to attain, he doesn't have to rely on the community.