3 ms·

Nope. It doesn't. I've spent two years working with it. And "gets every single dang decision right" is a matter of opinion. Chris and José are incredibly wonder

by bphogan 10y ago

Nope. It doesn't. I've spent two years working with it. And "gets every single dang decision right" is a matter of opinion. Chris and José are incredibly wonderful people, but they are just as opinionated as the people behind Rails. So "gets decisions right" sounds good as long as you agree with those decisions. I happen to love working with Elixir and Phoenix. I find working with Ecto frustrating not because of the code, but because of the opinions the framework creators have made about where things go. They have good solid reasons for their opinions. And they are not wrong. I just don't agree with them. And that's totally ok.

brightball 10y ago
Depends on the decisions, but in my experience the way they've setup to do things encourages the proper balance of productivity, separation of concerns, maintainability and data integrity. The balance on the database side of things has been most impressive because I didn't expect it at all coming from several years of Rails. In my experience to this point, the idea of letting your database enforce the integrity of your data was generally viewed as heresy. You could do it and the Rails team itself provided all of the tools to do it properly, but it seemed as if the community in general was totally opposed to it. The community shift towards embracing PostgreSQL so heavily has seemed to slowly be steering that trend away but there's still a lot of opposition. I've seen some tragic consequences because of those decisions in the last few years. The balance encouraged in Programming Phoenix sets an excellent standard for a growing community. The view + template layer has been a breath of fresh air. Of course, to each his own. Phoenix has me more excited about work than I've been in years though and I'm that guy that doesn't shut up about things that he loves. :-)

by bphogan 10y ago

brightball 10y ago

Depends on the decisions, but in my experience the way they've setup to do things encourages the proper balance of productivity, separation of concerns, maintainability and data integrity. The balance on the database side of things has been most impressive because I didn't expect it at all coming from several years of Rails. In my experience to this point, the idea of letting your database enforce the integrity of your data was generally viewed as heresy. You could do it and the Rails team itself provided all of the tools to do it properly, but it seemed as if the community in general was totally opposed to it. The community shift towards embracing PostgreSQL so heavily has seemed to slowly be steering that trend away but there's still a lot of opposition. I've seen some tragic consequences because of those decisions in the last few years. The balance encouraged in Programming Phoenix sets an excellent standard for a growing community. The view + template layer has been a breath of fresh air. Of course, to each his own. Phoenix has me more excited about work than I've been in years though and I'm that guy that doesn't shut up about things that he loves. :-)