probably more than some style cops would like.
NODE FILE MONITOR CODE
I've discovered Douglas Crawford's Code Conventions for the JavaScript Programming Language, and I've taken some hints from there. I'm working on trying to align my style and conventions to the majority of JavaScript code out there, but that's fighting against practices and styles I've been doing for many many moons.
One of the things you may notice is my coding style is changing between each article. JavaScript/Node? I'm going to scratch my head and answer "I don't know, but let's find out together." Need help with C++, C#, SQL, or Assembly: I'm your man and can answer a lot of questions off the top of my head. I am the newbie when it comes to JavaScript/Node, so keep that in mind. I'm still not an expert and don't pretend to be, so for those of you reading this article: realize this is done in the "Learn Along" kind of format and not as an expert trying to teach newbies. That way when I do use a framework, it's a time-saver and not a crutch. Doing this has really impacted my knowledge of the basics of JavaScript, so, as with the first article I continue to avoid frameworks until I get a strong handle on both Node and JavaScript. Sadly when using JavaScript as I do now, I rely extremely heavily on jQuery and other frameworks.
I've learned a great deal with just the few modules I've written so far, but there is still so much to learn. Hey! you never know, my writing skills might improve as well as my JavaScript/Node skills. I'm going to try and correct that going forward by focusing on one item at a time. While this article doesn't fulfill all the requirements of Sprint 2 of my self assigned "getting started" project, I think I tried to cover too much in the first article instead of focusing on one piece at a time. Reporting from the Trenches (thoughts 'til now) This article will focus on that functionality. So the requirements are: I need some way to monitor a directory (and possibly all of its child directories) for changes such as new files added, files deleted, files modified, folders removed, folders, added, etc. I usually do file handling on the server side with some other technology like C# or even PowerShell. Which to me is a complete departure from anything I've ever done in JavaScript. In this particular article, I start delving into the fs (File System) module of Node.js. I'm really starting to re-evaluate that position. Up until now, I've never really viewed JavaScript as something I might consider useful for anything beyond UI. I (like many developers I know), primarily use JavaScript for such things as AJAX calls and making web pages a little bit better and more responsive. I have to say that using JavaScript for more than just working with the DOM has been interesting.
My dive into the world of Node.js continues with this article.
NODE FILE MONITOR SERIES
George's Getting Started with Node.js Series
0 kommentar(er)
