awesome-talkscurated list on GitHubRecommends
Under “Functional Programming”
To Clojure and back: Writing and rewriting in Ruby by **Phillip Mendonça-Vieira** (RubyConf 2016) 33:16
0:00 / 0:00
RubyConf 2016 - To Clojure and back: writing and rewriting in Ruby by Phill MV
Confreaks
42K subscribers • 84 videos on Hallway • Conference channel
- Recommended by 3 people: 2 in engineering communities and 1 curated list.
- Presented by Phillip Mendonça-Vieira
- An opinion. It argues one side of a question engineers disagree on.
Intermediate. Assumes working knowledge.
12K views9 years ago3 recommendations
Programming languagesSoftware designLisp and ClojureRubySoftware architecture
Phillip Mendonça-Vieira shares the experience of building a startup app in Clojure and eventually rewriting it back to Ruby.
RubyConf 2016 - To Clojure and back: writing and rewriting in Ruby by Phill MV Act 1 - State of Grace After many years of Ruby, we built our app in Clojure, why not. Clojure is a breath of fresh air. Learn a lisp today! Act 2 - The Fall It's harder to succeed when you're in a new and different ecosystem. How Clojure contrasts with Ruby. Act 3 - The Wilderness Rewriting your app is a bad idea but we did it anyways. How we came to that decision. Act 4 - Reconciliation How I write Ruby has changed: a discussion.Why it's here
3 people recommend thisWhat people say. Recommended as an insightful talk on the trade-offs of adopting Clojure in a startup and the decision to rewrite in Ruby.
Moments people linked to
u/afhammadin r/Clojure • Recommends
To Clojure and back: writing and rewriting in Ruby
u/fagnerbrackin r/Clojure • Recommends
The experience of a Ruby developer on a startup that used Clojure initially and then rewrote it using Ruby again
u/daveliepmannin r/Clojure • Mentions
On “Simple Ain't Easy, but Hard Ain't Simple: Leaving Clojure for Ruby”
1. I think it's worth looking at what people said that Phillip characterizes as calling him "incompetent". He admitted to biting off more than he could chew: his first Clojure app was his first experience with functional programming on immutable data structures, *and* with the JVM, *and* with lisp, *and* with the "small, composable libraries" paradigm, *and* with Datomic, EDIT *and* with the problem domain /EDIT...and if I understand correctly, he launched almost immediately into production with a tiny team, giving him little room to refactor. That's a ludicrous number of new paradigms to learn, all simultaneously, all in just a few months, while building a product which has to be suppor…
u/phillmvin r/Clojure • Mentions
On “Simple Ain't Easy, but Hard Ain't Simple: Leaving Clojure for Ruby”
>but that you lacked experience but yet felt that you had enough knowledge to make sweeping judgements about the language.
We worked on the app for a year and a half! I personally spent at least five months full time on it; I think I'm entitled to _some_ opinions ;).
>So devs can't write the same app on a different platform with 1/10th of the experience....okay...I think we all knew that.
Did you watch the talk? I don't recall making any perf claims anywhere else - and, well, I think we're in agreement and I feel like I said something very similar :).
See about 60 seconds starting here: link to this video
u/SpoofedCodein r/Clojure • Mentions
On “Appcanary - Simple Ain't Easy, but Hard Ain't Simple: Leaving Clojure for Ruby”
What I really found interesting was the video: link to this video
It's hard to beat Rails for a quick, secure and high quality CRUD web application. He says learning Clojure is worth doing, and mentions he's a better Ruby developer for it.