This is part 2 of our series. Click here if you need to read part 1.
Now that we have our project set up, we can start building our application.
This is part 2 of our series. Click here if you need to read part 1.
Now that we have our project set up, we can start building our application.
As Angular 2 reaches closer and closer to completion, and as TypeScript releases newer and cooler features, one may want to be prepared for the coming TypeScript revolution. However, sometimes setting things up isn’t as clear as it should be. Fortunately for you, dear reader, I’ve done this a few times now, and am willing to help you out.
Over the course of a few posts, I’m not sure how many yet, we’ll go over setting up an Angular 1 project with the following technologies:
Read, evaluate, print, loop. A simple tool at the end of it all. Most languages come with one. Node, Ruby, and Python all have one. Even Lisp and Haskell come with them. There are even attempts at Java and C# ones. However, the default REPL is a little lackluster. All it usually does is read, evaluate, print, and loop, after all. There’s no autocomplete and no syntax highlighting, two features I greatly enjoy.
or is there…
Oh, boy. Python! This is part 3 of 3 on our “Development on Windows” series, and by “part 3 of 3,” I of course mean I haven’t thought about more Windows development issues… yet. If I can come up with more, I will be adding more posts. Tweet at me if you think of any issues you have. Maybe I’ll tackle git one day.
There’s a couple reasons why setting up Python on Windows is the hardest. First, a couple of tools that come highly recommended for Python aren’t compatible on a plain Windows install. Second, I’ve never been able to successfully install a C-based extension in Windows. I’m trying a new approach that might be successful as I write this, so hopefully it works out okay.
Continuing on with our “Developing on Windows” series, we will now be talking about Ruby. Why does everyone think that you can’t develop on Windows? Our last post talks about getting a decent set up for vim.
Compared to that, this is actually not too bad. It follows three steps: