Comments on: Ecto v1.1 released and Ecto v2.0 plans

By: Aaron Tinio

Aaron Tinio — Tue, 23 Feb 2016 01:41:00 +0000

I’m so glad callbacks are being removed! Thank you guys for making the right, tough choices!

By: josevalim

josevalim — Mon, 01 Feb 2016 08:06:00 +0000

In reply to Chasm. Thank you! I would say a month from now is not an unreasonable expectation, at least for a beta release.

By: Chasm

Chasm — Mon, 01 Feb 2016 01:39:00 +0000

When I first encountered the Phoenix Framework about a year or so ago I was very dismayed that it appeared to be trying to rebuild Rails in Elixir. Why, why, why would anyone try to shoehorn an OOP framework into FP? Recently, I decided I’d better learn Phoenix anyway (how bad could it be?), and began reading the excellent new book.

I’m delighted to report that I was totally wrong about Phoenix. In almost every way, it does things right, which is to say the FP way. Awesome. Models, however, were one area that still seemed a bit suspect. I think that getting rid of them is a capital idea, and am very much looking forward to Ecto 2. Any idea when it might be ready?

By: Chris

Chris — Sat, 16 Jan 2016 22:45:00 +0000

In reply to stevegrossi. Unless I am mistaken, Daniel still leverage Ecto Callbacks in his GenEvent solution.

By: stevegrossi

stevegrossi — Tue, 15 Dec 2015 17:10:00 +0000

Awesome work! I’m actually excited for the removal of callbacks. Few features of Rails have given me more pain that those.

I’d like to bring attention to a very timely post by Daniel Berkompas on replacing Ecto callbacks with GenEvents: http://blog.danielberkompas.com/2015/12/08/use-gen-event-with-ecto-callbacks.html. His approach adds some complexity, but also gives you more control and could be a good replacement for anyone looking to migrate their Ecto callbacks before 2.0.