Microsoft acknowledged death of Windows Phone

Is it worth "crying about" death of Microsoft Windows Mobile? Let's figure out
11 October 2017   1195

Recently, Microsoft official announced that they stop "building new features" for Windows Mobile 10. This was reported by the Joe Belfiore, Corporate Vice President in the Operating Systems Group at Microsoft.

Also, he said that "as and individual user, I switched platforms." 

The fact that Windows Phone is a "dead" platform is not a new for everyone. Verde ascertained death of the platform in January 2016. They pointed to the constant sales drop Lumia phones and to the fact that such phones were sold for an order of magnitude less than devices on iOS and Android: 110 million versus 4.5 billion (Androids plus iPhones).

In 2015 and 2016, Microsoft conducted massive layoffs of employees from mobile units - the work lost several thousand people.

But Windows 10 Mobile update was released in September 2017. It has some bugfixes and new features, like 2FA. 

The main reason of the platform's death is low quality and quantity of available apps. 

At the end of September, even Bill Gates reported on the rejection of the Windows phone: during an interview about Steve Jobs and new iPhones, he told that he switched to Android "with a bunch of programs from Microsoft." 

So, is it a big pitty that Windows phone died? We've made small research of search engine trends, and here's what we've found.

Search Trends
Search Trends

On a chart above, blue line is a popularity of Andoid, red line - iOs and yellow - Windows Mobile. As you can see, Windows Mobile was on the one level with other operating systems only 10 years ago, at the age of smartphones. So, there is no need to cry about the death of Windows Mobile OS.

.NET Standard 2.1 to be Released

IT giant added a lot of new features and updates to its programming platform standard
07 November 2018   279

Microsoft developers have updated .NET Standard to version 2.1, adding to it a number of improvements and a large number of APIs. .NET Standard is a set of common interface specifications for the .NET Framework, .NET Core, Mono, Xamarin, and others. A library that meets the specifications of .NET Standard can be used on other .NET platforms.

Main updates:

  • Span data type support for all platforms. Span allows to work with strings, arrays and other types of data, and also introduces an abstraction of access to a certain section of memory for both read and write. This will simplify development. In general, Span is at the heart of most performance improvements in .NET Core 2.1.
  • Foundational-API - updated standard for performance. It, unlike Span, expands the list of program interfaces, and not data types.
  • Updated ValueTask type for high load scripts. ValueTask returns the result if the operation is performed synchronously without creating a new task, which affects the overall software performance. Using ValueTask allows to minimize the overhead of a PC or server. The type itself appeared in .NET Core 2.1, and in the new version it additionally uses such types as Socket and NetworkStream.
  • Reflection emit adds type generation technology 'on the fly'. Separately, it has already been used, but now it is included in the standard. The .NET ecosystem usually makes extensive use of dynamic functions, so Reflection emit allows to optimize system performance.
  • The previously used SIMD API is now included in .NET Standard in the NuGet package.
  • There was a primitive DbProviderFactories. It makes it easier for libraries and applications to use ADO.NET technology. The registered instance of DbProviderFactory is selected by name from the database configuration parameters.
  • Functions System.HashCode and System.String added to base class libraries.

In .NET Standard 2.1, it is planned to add about 3 thousand APIs, some of which will be simply updated, while others will be completely new. This solves the problem of sharing code for .NET developers on all platforms. Learn more at official blog.