This short list was the result of the research I did with the intent of the framework / library being that it would be best one for me to learn with; so no disrespect to any of the others. I chose Aurelia because I know that it is being used by another team at my company, and React and Angular are not; so that made that last bit a little bit easier!
So, now that I’ve made my decision, it should be easy to just ‘get started,’ no?
Well, really, no. No, not for me. I’m new to this. It’s not like learning ASP.NET MVC after already knowing ASP.NET Web Forms, or even, for me, the jump from Java to C#. I’m seeing words like ‘npm,’ ‘gulp,’ ‘jspm,’ and I’m on a Mac! Ah! What is all of this?
My point here is that, if you are in a situation similar to mine, while all of these new terms and tools may cause initial panic, we can learn – don’t feel bad about being a newbie :) I really felt that Julie Lerman conveyed this sentiment well in an interview she did on .NET Rocks! (which is a fantastic podcast, by the way, and I highly recommended checking it out if you haven’t already). She’s a Microsoft MVP and a Pluralsight author, and, as she says in her interview, she too had to work from the ground up in getting started in this new world, and that honesty and lack of arrogance was inspirational to me.
Back to the ‘Get Started’ app, I started out by building the project in Visual Studio Code, but I couldn’t figure out what was causing these red squiggles, and I couldn’t get over them.
After some consideration, I thought, well, why hang on at all anymore? I may as well just jump in. So, I closed my project out from Code and opened it back up in Atom,
Now, I’ve got a working Aurelia Hello World. Magnificent!
My next step will be to try to push this to Azure. If I change course and try to push it to AWS instead, then I’ll know I’ve really fell off the deep end.