Jacket<p>I officially stated my project. I know exactly how I want to build it and I only use things I'm not familiar with. Yes, I like pain. For the back end I use <a href="https://tech.lgbt/tags/elixir" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>elixir</span></a> with <a href="https://tech.lgbt/tags/phoenix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>phoenix</span></a> and <a href="https://tech.lgbt/tags/absinthe" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>absinthe</span></a>. The last one is to use <a href="https://tech.lgbt/tags/graphql" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>graphql</span></a>. I'm more familiar with <a href="https://tech.lgbt/tags/rest" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rest</span></a> but I decided to go proper. The reason for using elixir is that while it's not the fastest it's also the most robust to handle heavy loads. I also subscribe to the idea that back end is usually a problem that functional solves better. For the front end I will go with <a href="https://tech.lgbt/tags/dart" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dart</span></a> using <a href="https://tech.lgbt/tags/flotter" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>flotter</span></a>. The reason is that my front end will be a mobile, desktop and web app. I'm also doing all of this with a <a href="https://tech.lgbt/tags/tmux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tmux</span></a> / <a href="https://tech.lgbt/tags/neovim" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>neovim</span></a> kind of work flow. I start to get good at it. I was thinking of maybe go with <a href="https://tech.lgbt/tags/liveview" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>liveview</span></a> but I really like the flexibility that flotter gives.</p>