Web Dev Flip Flopping
It is fair to say I have written this entry about 4 times and that is kind of funny as it is just one of those what I had for dinner entries.
As my previous posts indicate I am taking a bit of a dive into server side web development as it is area I know little about. The Udacity web course taught me a fair bit and made me think seriously about using the google app engine. Something just didn't feel right about it. The lack of control part where it seems very hard to get you data out if you decide to migrate away has just about scared me off.
I however liked python and took a look at using Flask. It seem pretty nice but again I didn't really progress with it. Last night I realised that I don't yet know enough about server side webdev to get going on the project I want to create and decided to attack the Node JS book I have again. This keeps in with my only use Javascript of C++ for projects this year, plus it is self contained and should give me the knowledge I need to actually start on the project I want to create.
I feel a little bit that I am being presented with too many choices and start to over think about things like migration to other systems and scaling. The lack of decision making on choice of tech was in turn making this post difficult to write. Lets be honest if I get a project going where I have to think about those things I would be quite happy.
On a different subject I took a look at the compatibility charts for JavaScript 6 and things seem to be slowly getting more and more support - if you ignore the current version of IE (the tech preview looks pretty good). It is only about four months until it is meant to be finalised and I guess at that point the flood gates should open. It should be a good year for JavaScript.
As my previous posts indicate I am taking a bit of a dive into server side web development as it is area I know little about. The Udacity web course taught me a fair bit and made me think seriously about using the google app engine. Something just didn't feel right about it. The lack of control part where it seems very hard to get you data out if you decide to migrate away has just about scared me off.
I however liked python and took a look at using Flask. It seem pretty nice but again I didn't really progress with it. Last night I realised that I don't yet know enough about server side webdev to get going on the project I want to create and decided to attack the Node JS book I have again. This keeps in with my only use Javascript of C++ for projects this year, plus it is self contained and should give me the knowledge I need to actually start on the project I want to create.
I feel a little bit that I am being presented with too many choices and start to over think about things like migration to other systems and scaling. The lack of decision making on choice of tech was in turn making this post difficult to write. Lets be honest if I get a project going where I have to think about those things I would be quite happy.
On a different subject I took a look at the compatibility charts for JavaScript 6 and things seem to be slowly getting more and more support - if you ignore the current version of IE (the tech preview looks pretty good). It is only about four months until it is meant to be finalised and I guess at that point the flood gates should open. It should be a good year for JavaScript.
Comments
Post a Comment