- .NET 6 is confirmed as faster than .NET 5; if you needed more motivation to upgrade, then that is a pretty good reason to do so. Besides the fact that you will eventually need to do so anyway;
- Bitrise does not officially support Xamarin anymore. It’s not a bad message, however. The company prepares to support .NET MAUI;
- In the light of deprecation of Internet Explorer last year, organizations must rethink what is their Web Development baseline. The answer will not be the same for everybody, anymore.
.NET 6 Faster Than The Predecessors
Microsoft shared the results of a performance benchmark, where they compared the performance of .NET 6 with the performance of .NET 5 and .NET Framework 4.8. The results are promising – in all the presented tests, the newest release had a bit of an edge over the ancestor.
The Bottom Line
Upgrades that bring noticeable performance changes are most welcome. Unfortunately, as it is the case with numerous major updates, there are some changes that might break your apps. In the case of .NET 6 and the accompanying libraries, the list does go on for a bit. This does not mean, that it automatically makes the transition impossible. It’s a tradeoff like any other: on one side we have our devs’ work hours, and on the other we have improved UX.
Unfortunately, though, there is an illusion of choice here. Any codebase has to be regularly maintained, which in turn means you will have to upgrade the .NET eventually. Putting it off for too long might be less than ideal, though there is a silver lining: .NET 6 is the Long-Term Support, which means it will be supported much longer, than usual.
Bitrise Removing Official Support For Xamarin Apps
Bitrise is a mobile CI/CD platform, that is advertised as a solution that “just works.” The tagline does not apply to Xamarin apps anymore. The company shared a post announcing the end of their official support for Microsoft’s app framework. There is a way to still build Xamarin apps on the platform, though it is not exactly recommended.
The Bottom Line
The announcement is a positive, overall. The company admitted they are working with the IT giant from Redmond on supporting the upcoming upgrade to .NET MAUI. Some sacrifices have to be made in the name of progress, and that might be the case more often now.
Web Development In 2022
Line shared an interesting post about the baseline for web development in 2022. They are looking for a new baseline they have to aim for now, after Microsoft retired Internet Explorer last year.
Even though the whole Web Development community was ecstatic after the announcement, everybody now needs to answer the same question – what do we want to design for? Before IE’s deprecation, the answer was simple. Now it’s a bit more complicated, and one has to factor in the popularity of web browsers on the markets you are targeting.
The Bottom Line
The internet we are building still fails to address more than a few issues:
- Bundle sizes are often much too big;
- Low-end Android phones from 2020 finally caught up to the performance of an iPhone 5 from 2012. Any complex computations that we ask these users to make will significantly degrade their user experience;
- Even though we may now safely assume the baseline for the network standard is 4G, many web apps still fail to hit any widely acceptable load time standard.
After having analyzed the available statistics, Line decided to establish their baseline as:
1. Safari is the baseline in terms of web standards: The sites we develop must work in Safari versions at least 2 years old.
2. Low-tier Android devices are the baseline in terms of performance: Low-tier Android devices have advanced little in the past few years so we must make sure our sites are super performant.
3. 4G is the baseline in terms of networks: Mobile networks have become a lot faster and stabler worldwide in recent years.
The new target does make sense in the context of their main target market (Japan), and takes all relevant aspects into consideration. Your organization now needs to go through the same process, if it already had not.