Building a chat app in 8 minutes with Phoenix
elixircasts.io
Building a chat app in 8 minutes with Phoenix
1–10 of 37 posts
Re: Building a chat app in 8 minutes with Phoenix
#2Here is another write-up that builds the same thing (and reads a bit nicer):
https://medium.com/@Stephanbv/elixir-phoenix-build-a-simple-...
Re: Building a chat app in 8 minutes with Phoenix
#3You can't do a build-X-in-low-Y-minutes trope when X involves implementing 30+ line classes.
EDIT: This comment was not appropriate, I apologize.
Re: Building a chat app in 8 minutes with Phoenix
#4You can't do a build-X-in-low-Y-minutes trope when X involves implementing 30+ line classes. EDIT: This comment was not appropriate, I apologize.
Why not?
Re: Building a chat app in 8 minutes with Phoenix
#5You can't do a build-X-in-low-Y-minutes trope when X involves implementing 30+ line classes. EDIT: This comment was not appropriate, I apologize.
Why not?
The build-X-in-low-Y-minutes trope implies that something is trivial to implement (usually by importing middleware that does the heavy lifting). A 30 line class is not trivial.
Re: Building a chat app in 8 minutes with Phoenix
#6Earlier quoted context omitted.
Why not?
The build-X-in-low-Y-minutes trope implies that something is trivial to implement (usually by importing middleware that does the heavy lifting). A 30 line class is not trivial.
> implies that something is trivial to implement
I don't think it does. It shows something implemented quickly, suggesting that it's a tutorial you can sit down and follow in one go.
Re: Building a chat app in 8 minutes with Phoenix
#7Earlier quoted context omitted.
Why not?
The build-X-in-low-Y-minutes trope implies that something is trivial to implement (usually by importing middleware that does the heavy lifting). A 30 line class is not trivial.
> The build-X-in-low-Y-minutes trope implies that something is trivial to implement
I think it just implies that the reader can do it without prior knowledge, and that Y minutes is surprisingly small.
You wouldn't write "build a blog in 80,000 minutes" even if it could be done with one line of code. And you wouldn't write "build [complicated thing] 3 minutes" and then show an expert rapidly typing a pre-determined program into an editor.
If a newbie can do it in Y minutes following the tutorial, it seems valid to me.
Re: Building a chat app in 8 minutes with Phoenix
#8Earlier quoted context omitted.
The build-X-in-low-Y-minutes trope implies that something is trivial to implement (usually by importing middleware that does the heavy lifting). A 30 line class is not trivial.
> The build-X-in-low-Y-minutes trope implies that something is trivial to implement I think it just implies that the reader can do it without prior knowledge, and that Y minutes is surprisingly small. You wouldn't write "build a blog in 80,000 minutes" even if it could be done with one line of code. And you wouldn't write "build [complicated thing] 3 minutes" and then show an expert rapidly typing a pre-determined pr…
I'll agree the "surprisingly small" interpretation is more charitable.
Re: Building a chat app in 8 minutes with Phoenix
#9I'm in the very early stages of building what will be a pretty large web app with Phoenix and so far I really like it.
I have a lot of prior Rails / Flask experience and minimal Elixir experience but you can still figure things out for the most part.
It's kind of funny but, even at this Elixir newbie stage I feel more confident reading and tracing most Elixir code vs Ruby.
Re: Building a chat app in 8 minutes with Phoenix
#10Great screencast, Alex!
The best tools are the ones you don’t even notice, and Elixir is an absolute pleasure. You get to focus on the problem with little ceremony. Chat is a really interesting application of Channels, too.
It’s especially interesting to me as my team and I are working on a hosted API called Chatkit that makes it equally easy to add real-time chat to your applications, no matter what technology you’re using: https://pusher.com/chatkit
In addition to basic chat data, we also manage, “Who’s online”, typing indicators, rich media... And more
I highlight those features in particular because I am especially curious what that would look like with Elixir and Pheonix? Managing chat data, especially at scale is quite a hairy problem.
By the way, it simple/clean to subscribe to Elixir Channels on other platforms like Android and iOS, for example? One place we think we can add a lot of value is X-platform client SDKs (JavaScript, Kotlin, Swift, etc.)