News for hackers. Stuff that matters.
Re:Reasons to use Phoenix instead of Rails by aczerepinski on Sunday November 26, 2017 @01:20PM (#15782207)
One of my favorite perks of Phoenix vs Rails is no wasted time trying to figure out where the heck a method/function came from. Is it from the parent class? One of the included modules? Or perhaps not defined anywhere at all, with method missing magic? Going from that to explicit imports is refreshing.
Re:Reasons to use Phoenix instead of Rails by thibaut_barrere on Sunday November 26, 2017 @01:41PM (#15782290)
(note: I use both Elixir & Ruby, for different reasons)

You can most of the time rely on object.method(:blank?).source_location to quickly determine where a specific method is defined.

More useful debugging tips can be found here:

https://www.schneems.com/2016/01/25/ruby-debugging-magic-che...

Re:Reasons to use Phoenix instead of Rails by nitrogen on Sunday November 26, 2017 @01:59PM (#15782382)
If you use Pry with Rails, you can also call binding.pry before the method in question, then type show-method [methodname] in the Pry console.
Re:Reasons to use Phoenix instead of Rails by elvio on Sunday November 26, 2017 @01:49PM (#15782330)
That is a real productivity booster. I also enjoy the clarity and explicitness present in the framework.