The short answer is, yes and no. It depends upon who you are. The purpose of this entry is to help you determine, yes or no.

Full disclosure. This entry is created on a Mac mini. And doing so on Windows 8 (Release Preview). If you are a developer, in my humble opinion you need to test on all platforms you expect your app to run or you are not much of a developer.

To be successful you need to leave politics in geographical territory known as Washington DC. My definition of that is: 14 mi.² of real estate surrounded by reality.

Only in politics can we afford to take sides. Those of us in IT, especially developers need to do our best to be all things to all people. Certainly this is a technical impossibility. However in our game we can get some points for at least being serviceable if not outstanding.

The innovators in technology have long paved the way for greater social advancement. No one can dispute the fact that the impact of Bill Gates and Microsoft will be far reaching for many years to come. The question is whether or not Microsoft will be able to adapt and thrive in emerging markets. The fact that Microsoft enjoys four decades of establishment also makes it difficult to make major changes without alienating the 1.5 billion Windows users.

This was apparent with the release of Windows 8. Windows users had come to expect a certain amount of consistency from their applications. The Metro tile, touch screen interface left a lot to be desired for enough people that Microsoft eventually more thoroughly implemented an older desktop view minus a traditional Start menu.

The app focused Windows 8 was supposed to be a step towards a greater integration of Cloud technology. In recent years, Microsoft lagged behind its competitors in getting established in new technologies. That includes the billions of dollars the emerging mobile market offered and Cloud computing.

Amazon was the first powerhouse to really establish themselves in the Cloud technology market. Google, Microsoft, and smaller parties are all playing catch up to take a piece of the Cloud pie. More and more businesses are embracing Cloud technology as a way to minimize their equipment and software expenses. While it does take a bit for older businesses to get onboard with such a change, start ups are looking at Cloud computing as an essential part of their business.

But what does that mean for Microsoft? Decisions were made to help update the four decade old Microsoft to the "always on" world we currently live in. Instead of operating in project "silos", different departments were brought together under more generalized headings where they could work closer with one another. Electronic delivery of software, including through Cloud tech, puts Microsoft in the position of needing to meet a pace that is very different from Gates’ early days.

The seriousness of their desire to compete with the likes of Amazon is their pricing matching on Cloud infrastructure services. Microsoft is not a company that has traditionally offered price cuts to compete with others. The fact that they have greatly reduced rates on getting infrastructure set up paves the way for more business users of their Cloud-based apps like Microsoft Office. Inexpensive solutions and free applications open the doors for Microsoft to initiate more sales of other products to their clients.

Former CEO Steve Ballmer recognized there was a need for Microsoft to change directions to remain competitive. In February 2014, he stepped down as CEO stating that the CEO needed to be there through all stages of Microsoft's transition in these more competitive markets. And the former role of his chosen successor, Mr. Satya Nadella? Head of Microsoft's Cloud services division.

Microsoft may not always catch the initial burst of a new development in their space; but they regularly adapt and drive forward. The leadership of Microsoft is clearly thinking forward in what they want to accomplish as sales of PCs have stayed on a continuous decline. It should come as no surprise that Microsoft will embrace this new direction and push towards a greater market share against the likes of Amazon and Google.

Related:

Who Are the Main Players in Big Data?

Is Cloud Computing Safe for Your Business?

Is The Grass Greener in Mobile App Development?

In Python, we can create three types of methods in a class:  instance or regular method, classmethod and staticmethod.  Instance methods are associated, as the name infers, with an instance or object of the class and take self as the first parameter.  Classmethods take a reference to the class, cls, as the first parameter of the class.  Staticmethods, for the most part, are convenience methods that could be declared as functions since they really do not have much to do with the class itself.  They were probably added at some time after the advent of Python in order to make the language more object oriented i.e. minimize the number of free floating functions. 

Refer the our article static, class and regular methods in Python for a detailed explanation on this subject.

Over time, companies are migrating from COBOL to the latest standard of C# solutions due to reasons such as cumbersome deployment processes, scarcity of trained developers, platform dependencies, increasing maintenance fees. Whether a company wants to migrate to reporting applications, operational infrastructure, or management support systems, shifting from COBOL to C# solutions can be time-consuming and highly risky, expensive, and complicated. However, the following four techniques can help companies reduce the complexity and risk around their modernization efforts. 

All COBOL to C# Solutions are Equal 

It can be daunting for a company to sift through a set of sophisticated services and tools on the market to boost their modernization efforts. Manual modernization solutions often turn into an endless nightmare while the automated ones are saturated with solutions that generate codes that are impossible to maintain and extend once the migration is over. However, your IT department can still work with tools and services and create code that is easier to manage if it wants to capitalize on technologies such as DevOps. 

Narrow the Focus 

Most legacy systems are incompatible with newer systems. For years now, companies have passed legacy systems to one another without considering functional relationships and proper documentation features. However, a detailed analysis of databases and legacy systems can be useful in decision-making and risk mitigation in any modernization effort. It is fairly common for companies to uncover a lot of unused and dead code when they analyze their legacy inventory carefully. Those discoveries, however can help reduce the cost involved in project implementation and the scope of COBOL to C# modernization. Research has revealed that legacy inventory analysis can result in a 40% reduction of modernization risk. Besides making the modernization effort less complex, trimming unused and dead codes and cost reduction, companies can gain a lot more from analyzing these systems. 

Understand Thyself 

For most companies, the legacy system entails an entanglement of intertwined code developed by former employees who long ago left the organization. The developers could apply any standards and left behind little documentation, and this made it extremely risky for a company to migrate from a COBOL to C# solution. In 2013, CIOs teamed up with other IT stakeholders in the insurance industry in the U.S to conduct a study that found that only 18% of COBOL to C# modernization projects complete within the scheduled period. Further research revealed that poor legacy application understanding was the primary reason projects could not end as expected. 

Furthermore, using the accuracy of the legacy system for planning and poor understanding of the breadth of the influence of the company rules and policies within the legacy system are some of the risks associated with migrating from COBOL to C# solutions. The way an organization understands the source environment could also impact the ability to plan and implement a modernization project successfully. However, accurate, in-depth knowledge about the source environment can help reduce the chances of cost overrun since workers understand the internal operations in the migration project. That way, companies can understand how time and scope impact the efforts required to implement a plan successfully. 

Use of Sequential Files 

Companies often use sequential files as an intermediary when migrating from COBOL to C# solution to save data. Alternatively, sequential files can be used for report generation or communication with other programs. However, software mining doesn’t migrate these files to SQL tables; instead, it maintains them on file systems. Companies can use data generated on the COBOL system to continue to communicate with the rest of the system at no risk. Sequential files also facilitate a secure migration path to advanced standards such as MS Excel. 

Modern systems offer companies a range of portfolio analysis that allows for narrowing down their scope of legacy application migration. Organizations may also capitalize on it to shed light on migration rules hidden in the ancient legacy environment. COBOL to C# modernization solution uses an extensible and fully maintainable code base to develop functional equivalent target application. Migration from COBOL solution to C# applications involves language translation, analysis of all artifacts required for modernization, system acceptance testing, and database and data transfer. While it’s optional, companies could need improvements such as coding improvements, SOA integration, clean up, screen redesign, and cloud deployment.