server side development

Programming Language of the Future {6}

by Rudy P
The article I chose to blog about this week is titled, “Is Javascript the Future of Programming?” by Dani Fankhauser of Mashable Tech. JavaScript, “first created by Brendan Eich at Netscape in 1995” (Fankhauser). It was initially not taken by developers as a serious server side languages, such as Java, Python, or Ruby. However, over the years JavaScript has become more prolific and more widely used, and can even be used as a server side language with a framework  called Node.js.         Node.js is an “asynchronous, which makes it highly scalable and a great fit for all the big data out there”(Fankhauser). JavaScript is the only client side language, and runs directly in the browser gives it an edge over other languages.  JavaScript is now one of the preferred  ways of developing applications for Windows 8, Klout, Storify and Yammer because of its ability to be a front and back end language. This and the array of tools at its disposal such as Node.js, jQuery (a library), JSON (JavaScript Object Notation) and MongoDB, give JavaScript a very bright future to be a top language for both the front and back end of applications. read more...

ASP.NET MVC {Comments Off on ASP.NET MVC}

by Jonathan F

http://t1.gstatic.com/images?q=tbn:ANd9GcQgQKnRVdXUJhaodlvPI-avERjxr_hKhUBlcQF-cJIynwBXJp4O

Developers now have a choice when developing a Web page, they can use ASP.NET or use ASP.NET MVC. MVC stands for Model-View-Controller it is a framework that separates an application into three main components. Many companies now are choosing ASP.NET MVC because it lacks any constraints that are imposed by ASP.NET and are using it to revise existing sites. The problem is that there is a greater startup cost for ASP.NET MVC and the benefits of using it might not be large.  ASP.NET MVC was created by Microsoft in 2007- 2008 to demonstrate that it was able to apply MVC to ASP.NET. Its goal was to separate data, business logic, and the presentation to the user. It wanted to reduce the intermingling of the business logic and presentation layer. ASP.NET MVC is more advanced than ASP.NET because it incorporates some of the business and technological advances that have been made after ASP.NET was released. The advantages that ASP.NET MVC has over ASP.NET is that it is lightweight, easy to modify, and highly testable. The first people to adopt ASP.NET MVC were developers that were not happy with the ASP.NET Web Forms because it created a large layer built on top of the Web Forms. ASP.NET MVC lets developers have control of HTML and HTTP. The control of HTML was important because developers could build applications using Ajax more comfortably and it made it easier to add more interactivity and responsiveness to existing apps. ASP.NET MVC adapts easier to the new Web technology developments and ASP.NET MVC uses interface-based contracts that allow isolation which makes testing components easier. It is easier to test code and to write the code cleaner. The author says that although ASP.NET MVC is better than ASP.NET Web Forms it is not really necessary to use ASP.NET MVC over ASP.NET because the core functions of both are the same. The only real reason to use ASP.NET MVC is when Web Forms are no longer useful to the developer. read more...