Live data from Hacker News

Phoenix 1.3.0 Released

phoenixframework.org

11–20 of 143 posts

Re: Phoenix 1.3.0 Released

#11
post #10
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?

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.

Re: Phoenix 1.3.0 Released

#13

Quote interesting release, many useful features. `action_fallback` looks really nice. Contexts ... not so much imo

I have an example where context works well for me.

I have built an app[0], the app allow user to submit links, either using our web ui or via a bot.

When using web ui, they have to login, hence we associate the links with that user. The bot is different, everyone submit via the post share the same `Bot` account.

In other words, the process of inserting a link from web ui or via bot is a bit different. Without context, I would use different module or some branch code to distinct between them. I think context solves that nicely for me.

---

[0] https://one.betterdev.link which is an extra version of https://betterdev.link/

Re: Phoenix 1.3.0 Released

#14

Quote interesting release, many useful features. `action_fallback` looks really nice. Contexts ... not so much imo

I love contexts!

But if you don't, that's cool too. There are mix tasks for using the older style generators and mix tasks for the newer context style generators. Use whichever you prefer.

Re: Phoenix 1.3.0 Released

#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.

Re: Phoenix 1.3.0 Released

#16
post #10
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?

Go into it with the attitude of 'deferal of gratitude'. In other words it might look painful for a while but when various things click you get your holy s moments and you'll never go back. I've worked in a lot of java, php, python, c# etc frameworks and there are very specific reasons this is near always better long term. A lot of it comes back to elixir simply solving the correct problems. Learn elixir using the elixir lang site guides and then jump into phoenix using their official guides. Eventually you'll experience the upsides and versatility

Re: Phoenix 1.3.0 Released

#17
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?

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?

Re: Phoenix 1.3.0 Released

#18
Gonna do phoenix for a side project.

I'm just a bystander reading about erlang and elixir for awhile. Did web dev in php and a little bit of nodejs.

But I think what you guys doing are great. I'm glad Elixir and Phoenix came about it really helps drive the language into a field (web dev) and get people to notice.

And that one implementation of figuring out how people is log off or not that is in Phoenix was really sweet when you presented it.

Re: Phoenix 1.3.0 Released

#19
post #16
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?

Go into it with the attitude of 'deferal of gratitude'. In other words it might look painful for a while but when various things click you get your holy s moments and you'll never go back. I've worked in a lot of java, php, python, c# etc frameworks and there are very specific reasons this is near always better long term. A lot of it comes back to elixir simply solving the correct problems. Learn elixir using the eli…

By correct you mean that Elixir solves problems differently than java, php, python, etc. and you found this more appealing over time, which may or may not be the case for someone else.

Or are you making a stronger claim that language X is better than Y, at least when it comes to web dev?

Re: Phoenix 1.3.0 Released

#20
post #17

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 works within existing Elixir constructs like macros and modules, so it keeps a lot of the nice interfaces of Rails without the magic, how things work is pretty straightforward.

It is worth stating that the way Erlang/Elixir manage processes is completely different than most other languages and that has to be grokked at some point. Thankfully the framework abstracts a lot of that.

The Elixir and Phoenix docs are also pretty good. They're not Django-level (what is), but they're good.

Post reply on HN