weather
A command line weather app built using elixir (by tacticiankerala)
real world example app
Exemplary real world application built with Elixir + Phoenix (by gothinkster)
| weather | real world example app | |
|---|---|---|
| - | 2 | |
| 69 | 870 | |
| - | - | |
| 0.0 | 0.0 | |
| over 5 years ago | over 1 year ago | |
| Elixir | Elixir | |
| - | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
weather
Posts with mentions or reviews of weather.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning weather yet.
Tracking mentions began in Dec 2020.
real world example app
Posts with mentions or reviews of real world example app.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Phoenix namespacing conventions
After that, you're left with everything else in your application, much of which is interrelated on the data level. Using this repo as an example, you find that it has Accounts and then Blog as the primary namespaces (which make sense), which then leaves you with blog.ex which is a file containing a ton of database reading/writing/helper functions for all these different entities in the namespace (this is how the generators will also scaffold things, continuing to pile on the functions). It feel strange to me to have one giant file that forever grows proportional to the size of the namespace with so many concerns. Is it a good idea to split these things out (particularly when the ecto models aren't responsible for database queries in Pheonix) or am I just thinking about this the wrong way??
-
Phoenix
Getting Id token - here is some example: https://github.com/gothinkster/elixir-phoenix-realworld-example-app
What are some alternatives?
When comparing weather and real world example app you can also consider the following projects:
ex_iss - An elixir wrapper for Open Notify's International Space Station API. http://open-notify.org/
phoenix-liveview-counter-tutorial - 🤯 beginners tutorial building a real time counter in Phoenix 1.7.7 + LiveView 0.19 ⚡️ Learn the fundamentals from first principals so you can make something amazing! 🚀
koans - Small exercises to discover elixir by testing
phoenix-flux-react - An experiment with Phoenix Channels, GenEvents, React and Flux.
harakiri - Help applications kill themselves
changelog.com - Changelog is news and podcast for developers. This is our open source platform.
oop - OOP in Elixir!
elixir_koans - Elixir learning exercises
weather vs ex_iss
real world example app vs phoenix-liveview-counter-tutorial
weather vs phoenix-liveview-counter-tutorial
real world example app vs koans
weather vs phoenix-flux-react
real world example app vs harakiri
weather vs changelog.com
real world example app vs oop
weather vs oop
real world example app vs elixir_koans
weather vs elixir_koans
real world example app vs changelog.com