Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Phoenix 1.3.0 Released

phoenixframework.org

Post reply on HN
Print view View original

21–30 of 143 posts

Re: Phoenix 1.3.0 Released

#21

Post by dqv »

dopeboy wrote: post #10
fareesh wrote: post #8

I'm spending all my free time with Phoenix. I come from a Rails, Laravel, Django and a bit of .NET Core background. So far I am extremely impressed. I'm surprised it has not been adopted by that many folks in production.

I'm a django guy. I have no experience with functional programming. What would a transition to phoenix + elixir look like for me?

You'll have a phase of disorientation where you'll be wishing you had x feature in Django and the reverse where you'll wish you had y feature in Phoenix/Elixir.

The thing I really miss from Django is the admin scaffolding. Phoenix just isn't there. In practice, you could continue to use Django as a front-end.

I moved away from Django when the recurring question of "this is neat, but how do I make it keep going no matter what?"

Re: Phoenix 1.3.0 Released

#22

Post by jpinnix »

dopeboy wrote: post #17
aaron-lebo wrote: post #11

Earlier quoted context omitted.

It's more Rails than Django but once you've seen one MVC framework you've seen them all. I'd suggest: https://pragprog.com/book/phoenix/programming-phoenix In structure it reminds me a lot of the very first Rails book co-authored by DHH. It's a good way to get into the language/framework.

Thanks for the link. One thing I hated about Rails when I tried it was the level of magic involved. Does Phoenix suffer from that at all?

Phoenix 1.3.0 really helps you understand that you are just making an Elixir app with some additional features. I don't think there is as much "magic" as Rails.

Re: Phoenix 1.3.0 Released

#23

Post by aantix »

dopeboy wrote: post #17
aaron-lebo wrote: post #11

Earlier quoted context omitted.

It's more Rails than Django but once you've seen one MVC framework you've seen them all. I'd suggest: https://pragprog.com/book/phoenix/programming-phoenix In structure it reminds me a lot of the very first Rails book co-authored by DHH. It's a good way to get into the language/framework.

Thanks for the link. One thing I hated about Rails when I tried it was the level of magic involved. Does Phoenix suffer from that at all?

Something isn't magical if you understand the underlying concept/convention.

Re: Phoenix 1.3.0 Released

#25

Post by abledon »

dqv wrote: post #21
dopeboy wrote: post #10

Earlier quoted context omitted.

I'm a django guy. I have no experience with functional programming. What would a transition to phoenix + elixir look like for me?

You'll have a phase of disorientation where you'll be wishing you had x feature in Django and the reverse where you'll wish you had y feature in Phoenix/Elixir. The thing I really miss from Django is the admin scaffolding. Phoenix just isn't there. In practice, you could continue to use Django as a front-end. I moved away from Django when the recurring question of "this is neat, but how do I make it keep going no mat…

Could you give some examples of 'neat' things that needed to keep going no matter what on django (thus switching to Phoenix)

Re: Phoenix 1.3.0 Released

#26

Post by goatlover »

dopeboy wrote: post #17
aaron-lebo wrote: post #11

Earlier quoted context omitted.

It's more Rails than Django but once you've seen one MVC framework you've seen them all. I'd suggest: https://pragprog.com/book/phoenix/programming-phoenix In structure it reminds me a lot of the very first Rails book co-authored by DHH. It's a good way to get into the language/framework.

Thanks for the link. One thing I hated about Rails when I tried it was the level of magic involved. Does Phoenix suffer from that at all?

Everything above the machine level is magic (the computer is doing stuff behind the scenes for you, abstracting away from all the unnecessary detail).

Re: Phoenix 1.3.0 Released

#28

Post by s0l1dsnak3123 »

We’ve been using Phoenix at my company in production for over a year now. So far the experience has been overwhelmingly positive, our team have totally come round to its adoption, our server costs have come down and our response times have gone down also.

Coming from Rails, the ecosystem isn’t quite there yet, but it is far more mature than rails’ was this early on.

The hardest thing for us has been deployment, but we’ve solved that internally, including giving back by building exrm_deb (it works with distillery too!) to compile the entire project into a Debian package.

If you haven’t already looked at Phoenix (and Ecto!) give it a try :)

Re: Phoenix 1.3.0 Released

#29

Post by GiorgioG »

bnchrch wrote: post #15

I've been working professionally in Elixir/Phoenix for the past 4 months. Summary: It's amazingly productive, pleasant to work with and simple. Coming from a background spanning Python/Django, C#/.net and Node/Express I really believe it blows them out of the water. Thank you for all the hardwork of the Phoenix team and the amazing community you've made.

As a .NET developer by day, I'm curious what you like about Elixir over C#/.NET? I have a copy of Elixir in Action on my nightstand, I just haven't had a chance to crack it open yet.

Re: Phoenix 1.3.0 Released

#30

Post by jolux »

dopeboy wrote: post #17
aaron-lebo wrote: post #11

Earlier quoted context omitted.

It's more Rails than Django but once you've seen one MVC framework you've seen them all. I'd suggest: https://pragprog.com/book/phoenix/programming-phoenix In structure it reminds me a lot of the very first Rails book co-authored by DHH. It's a good way to get into the language/framework.

Thanks for the link. One thing I hated about Rails when I tried it was the level of magic involved. Does Phoenix suffer from that at all?

There's almost no magic in Phoenix, it's modular from the start and is really just a collection of libraries held together by some mix tasks to help you structure stuff.
Post reply on HN