Tuesday, June 29, 2010

Technology Populism

Technology Populism — information workers provisioning technology outside of IT's auspices — is a topic of great interest to both technology vendors and IT departments. But is it more hype than reality? No. Information
workers are increasingly playing a role in selecting and managing the smartphones, computers, and software they use to get their jobs done. And because IT departments feel the necessity of meeting the growing needs of a distributed workforce while cutting costs, we see them increasingly allowing some technology autonomy for workers. For technology product marketers, this means speaking directly to end users about solving their specific business problems. Going forward, technology vendors will have to design, develop, and market products directly to a variety of information workers who, like consumers, have myriad choices

Technology populism is driven by people's need to interact. For many employees, the telephone and e-mail are being replaced by text messaging, instant messaging and mobile devices such as iPhones and Blackberrys, and social computing tools such as Facebook and Wikipedia. Drivers behind technology populism include: (1) Cheap broadband at home and work as personal and professional lives converge (2) A new generation of applications based on network interactions

To compete among the niche group, IT managers to be driven by ‘technology populism'

Friday, June 18, 2010

No(n parameter) constructor in Value Type

There are two key types in .NET framework (1) Value (2) Reference. As we know, value consumes stack and reference uses heap memory to store direct and indirect data. On working in Value type .NET objects, got the quite
interesting observation.

In terms of constructor, there are two significant differences between value and reference types.
1. Value type can't define non-parameter constructor where as reference will.
2. If no constructor is defined, .NET Compiler can produce default non-parameter constructor for reference type, where as value type can't.

1. Non parameter
On writing the below code with parameterless constructor, .NET compiler throws the error 'Structs cannot contain explicit parameterless constructors'
public struct RectangleInfo {
public RectangleInfo() {

2. No constructor
On using ILDASM to inspect the members of the value type, a parameterless constructor is not a member of the structure as marked in the attached image. But during the app execution, .NET framework has ability to instantiate a value type by using a language's constructor called implicit default constructor.

Sunday, June 13, 2010

Recommendation Note

This week is in vacation mode at Goa beach resort;completely out of work station. Got a surprise recommendation note from Dave, one of the popular web master.

Last year, published an article in code project (http://www.codeproject.com/KB/silverlight/DB_in_SL3.aspx). CRUD explains the complete operation in any language; itz about Silverlight 3. Dave recommended it(http://www.daveenjoys.com/2010/05/20/introduction-to-web-net-programming/) with code example category. In general, motivation drives additional energy and so i'm ready to publish next CRUD article in ASP.NET MVC Framework.

Truth, naked, unblushing truth, the first virtue of all serious history, must be the sole recommendation of this personal narrative.”-Edward Gibbon(1780). Thanx Dave!

Saturday, June 5, 2010

HTML5 beats

HTML5 beats Adobe Flex, Microsoft Silverlight and Oracle JavaFX. Here u go!

Thought works to back up:
  • Plug in Hell: Except HTML 5, plug in is required to install in the customer machine for Adobe Flex, Microsoft Silverlight, and Oracle JavaFX by design. In the current IT, there are lot of focus towards app security. But, plug-in design leaks the power of security and provides the high probability of hacking/security break operation.
  • Next Gen Web: As MS web developer, Silverlight is not the only option to build the next gen web applications. Better choice would be ASP.NET MVC, WCF and Entity framework for UI, Service and DB app layers. Still, HTML5 UI capability exceeds other technologies.
  • Browser support: Though HTML5 spec is evolving, all browsers will support HTML 5 completely by 2010 end. Major browsers like Firefox 3, Internet Explorer 8, Chrome 2 and Safari 4 are already supporting.
  • Performance: In terms of performance, built-in browser support execution faster than the custom plug in app.

Google wave is built on HTML5 and more list to go! CTOs may have more tech justifications to switch.