I have been planning, plotting, schema…ing(?) about Food.Eat since my original post. I have made some progress but I have not nailed down exactly how I want to handle user authentication/authorization. Mostly, I think this is due to my choice in the loosely scripted PHP backend. With that knowledge tucked in the back corner of my head I made a desicion this morning based on some information from listening to one of my first podcasts Adventures in Angular I am going to not only learn but also use Ruby on Rails for my backend.

Ruby on Rails is a full stack web application framework that is relatively young by comparison to many languages in use today. It is fast, nearly pseudocode (spoken language-ish).

Similarly to using ruby as a new language on Food.Eat I also made the decision to go with angular 1.3.X for performance reasons and am also following John Papa’s Styleguide which, in my opinion, made my angular code much easier to read (Example).

If you would like to see any of the workings as I move forward, please, star, fork, help out, or just think ‘huh, Matt types things and I have no idea what they mean or he is talking about”.

GitHub Code Repository

P.S. Sneak peek

login1 login2