IT Programming Trend

xuexue87 — Fri, 25 May 2012 16:06:06 +0800

I myself is working for Microsoft.
As i know the trend programming language for now is ASP.Net and SharePoint.

For future it will be using ASP.Net MVC using HTML5 and razor.

Why i said so MVC will be using in the future ?

Well I cannot 100% confirm it will be use in future.
This is what i know and what i can tell you.

Future plan more and more people will be using the mobile as their working material and most of the development will be developed for web and mobile. Using MVC 3.0 you are able to develop the mobile version and website version easily. Then with this MVC your code will be more clean and data friendly. The code maintain is better than web form reason because the code can be reuse and it can automatic generate a page for you no need to rewrite all again but MVC majority will not use in Malaysia.

Reason: Malaysia never update a lot of company is still using IE6 to IE7 not using the browser that support HTML 5. Anyway IE 9 also not fully support HTML 5. IE10 is coming out together with Window 8 this October. Hope it fully support for HTML 5.

For Asp.net web form.
This is good for pc usage but is trouble to maintain because it require page by page maintainence. It also not specific for mobile devices and is not data friendly. The button submit will pass in a lot of data where will use up your data plan very fast. For example like I write a word for example "I love you". In behind the process actually is using about 30kb to finish it off.

SharePoint
Yes, SharePoint is the most hit and most usage this day. A lot of people are using SharePoint as their website because it available them to have Intranet and Extranet. This help a lot of the company to do a lot of thing but the problem is take a lot of time to do customisation on it. It work really well and you can do a lot of thing without using Database but you use SharePoint list. SharePoint list actually is the table of database and the column in the SharePoint is the Column database is the same concept but they use different query. SharePoint use CamlQuery to pull data and SQL use SQLQuery. The hardest part of SharePoint is not this but the XSLT part where you don't know how to do and what to change. If you change a bit and goes wrong then your whole portal content query web part will hit error and another hardest thing is the Masterpage if you dettach and attached a lot of time and something go wrong in between you need to do every thing again.Anyway best practice backup.

How about Java and other language is there anything change from there ?

Lowyat.NET: Latest topics by xuexue87

IT Programming Trend