- Resource Lists
- Awesome Elixir Resource List https://github.com/h4cc/awesome-elixir
- Elixir Talks https://github.com/elixir-lang/elixir/wiki/Talks
- Phoenix Framework http://www.phoenixframework.org/
- Elixir Official Site http://elixir-lang.org/
| Interlaced image loads an early degraded version of the whole image as soon as possible and then progressively renders the image to clear state. | |
| Non-interlaced image will load up in tiles showing clear image in each tile as it progresses to load in the image. | |
| For .jpg the interlaced = progressive and not interlaced = baseline. |
The Phoenix Framework was built with realtime communication as a first class priority. Using its built in socket handling and channels we can implement a basic, realtime chat application with little effort.
For this video we’re going to assume that you already have Elixir and Phoenix Setup. You will not need a database as the messages will not be persisted. This tutorial is taken pretty much directly from the Phoenix Documentation.
To start let’s generate a standard phoenix application:
$> mix phoenix.new instachatSending scheduled or automated emails from your application is a very common problem with a number of solutions. In this write-up I am going to demonstrate one particularly easy approach to adding email functionality to your Phoenix App. Phoenix is a web framework written in Elixir that is enjoying a meteoric rise in popularity recently. Many people are jumping onto the Phoenix bandwagon for its explicit, non-magical and functional approach to development.
For this demonstration, I am going to use an external library that integrates Mailgun into my Phoenix application. Phoenix includes the Elixir configuration file mix.exs which we will use to add our new dependency. We will add {:mailgun, "~> 0.1.1"} to the list of "deps" our project is currently us
While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.
Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.
Note: this was written in April/May 2014 and the API may has definitely changed since. I have nothing to do with Tinder, nor its API, and I do not offer any support for anything you may build on top of this. Proceed with caution
I've sniffed most of the Tinder API to see how it works. You can use this to create bots (etc) very trivially. Some example python bot code is here -> https://gist.github.com/rtt/5a2e0cfa638c938cca59 (horribly quick and dirty, you've been warned!)

