After struggling with installing Angular into my Rails app, Storm Savvy, I went in search for better answers and found a good resource from Lean Pub on the topic.
I normally turn to Lean Pub when in need of a guide on a specific topic, and this was such a case – the book includes chapters to specific use cases for Angular within Rails.
Where I started initially with a good tutorial from Adam Anderson for bootstrapping Angular into Rails, the Lean Pub book helped fill in the gaps.
Much of my gap in knowledge was in how exactly Angular fits into the Rails asset pipeline and gets loaded with the Rails App.
That said, I still have much to learn on bringing Angular into Rails but have at least moved on from my initial sticking point of loading the app and getting into the inner workings of Angular.
Being my editor of choice, I enjoy developing in vim for its simplicity and light-weight (saving resources for other tasks).
One drawback to getting started is the steep learning-curve – all input vim is done via touch typing which no mouse… NO MOUSE.
Sure, vim has included a visual mode and other modern features but at the core and its major advantage is being able to complete all your tasks without your fingers even leaving the home row of ASDF.
Enough of my personal thoughts on vim, here some quick start pointers for those of you who wish to start on vim:
- Follow the tutorials: Practice makes perfect, so practice before you actually practice with your code.
- Consider some plugins: I recommend Janus which provides some nice syntax tools but vim has a wide variety of plugins, so feel free to experiment as needed.
- The shell is your friend: Using vim means spending more time on the command line, so practice command tasks (e.g. copy, paste, etc.) using the basic bash/unix utilities.
- Consult the wiki: Vim has a great wiki containing detailed information on many common tasks and commands.
In conclusion, the initial time investment into vim is reaped later when many tasks can be completed with the shell (between tabs, in my case).
No, there was not typo in the title to this post – I do mean Rails on Ruby as in Rails is built on Ruby.
And in that, I mean that to develop in Rails is to use it as a tool and keeping in mind that Ruby is the set of building blocks doing all the work behind the scenes.
So how to apply this advice when developing on a new framework?
It means several things:
- Starts with the Basics: Setup the environment, complete tutorials and understand the basic functionality of the framework.
- Get to know the Framework: Most tutorials and textbooks will give an explanation of how the framework operates behind the scenes, typically from the standpoint of the underlying language (e.g. Java in Android, JS in Angular, etc.)
- Know as you go: Learn as much of the language as necessary to move forward in development. Knowledge is good, but it may not be what you need to know for solving a particular problem.
In conclusion, I recommend the “know as you go” in learning a new language behind a framework and focus on the overall objective and/or problem that you wish to solve.