These are the customer-reported issues addressed in 15.7.3:

• VS2017 compiler creates broken debug build using Qt framework and generates 'Invalid address specified to RtlValidateHeap' error.
• Incorrect code generation for matrix multiplication.
• VS 2017 Update 7: Git History Codelens only showing entries for the past 6 months.
• UWP projects reference multiple NetStandard 2.0 dlls after 15.7.1 upgrade.
• Building C++ code in VS 15.7 with /std:c++17 breaks binary compatibility for std::_Ptr_move_cat.
• Visual Studio 15.7 stuck when opening XAML files.
• CMake configuration fails and generates message "C++ IntelliSense information may be out of date, generate the CMake cache to refresh".
• Unable to start second process for debugging.
• After update to Visual Studio 15.7.1, some test programs fail in start-up due to reading access violation.
• Missing compiler required member 'Microsoft.CSharp.RuntimeBinder.Binder.Convert'.
• Build fails after 15.7.0 update on older project using .NET 3.5 .
• Coloring, typing, tooltips and IntelliSense slow in F# in VS2017 editor.
• F# editing experience takes up to a minute for tooltips and dropdowns to display.
• Certain class member variable value are incorrectly read as zero.
• Attempt to open XAML file for the first time causes VS to sit with the "Opening the file ..." message for about 10 minutes before XAML file opens.
• Visual Studio slows down and freezes, creating work loss.
• The target "GetBuiltProjectOutputRecursive" does not exist in the project.
• Internal error with lambda C++17 after 15.7.1 update.
• UWP App is slow to return a stopped state in IDE.
• MSVC auto-vectorization produces incorrect code or incorrect results.
• Visual Studio closed debug a new instance project1, when a new debug new instance project2 has started.
• Latest update breaks "start without debugging" on multiple projects.
• UWP XAML is very very slow on open.
• XAML viewer freezes on 15.7.2 and 15.8.0 preview 1.1.
• Xamarin UI Test App project template missing.
• Xamarin project creation problem.
• Visual Studio crashes when creating new Mobile APP Xamarin.
• Unable to create Xamarin.Forms-Projects.
• Não consigo criar novos projetos Xamarin Forms - Can't create new projects Xamarin Forms.
• Blank project crash after update. 

Established leaders (in blue in the chart and including Java, C#, and JavaScript) which are "common in paying organisations and show a high demand globally". Followers (in green) such as PHP, Python, and Ruby were found to "pay on average the same salaries, although their is 50% less demand for them". Finally there are a group referred to as Niche (orange) which "show very low demand and salaries almost 60% lower". 

Causes of Memory Leaks in JavaScript and How to Avoid Them  

4 Types of Memory Leaks in JavaScript and How to Get Rid Of Them 

10x faster and 90% memory reduction compared to Microsoft's immutable collections 

Why We Chose Typescript?
requirements:
- Must have types.
- Must have good tooling already.
- Powers major production apps.
- Our devs should be able to onboard fairly quickly.
- Should work on both the client and the server.
- Good library support.

The IESG has formally approved the HTTP/2 and HPACK specifications, and they’re on their way to the RFC Editor, where they’ll soon be assigned RFC numbers, go through some editorial processes, and be published. 

BenchmarkDotNet v0.10.13 has been released! This release includes:

• Mono Support for DisassemblyDiagnoser: Now you can easily get an assembly listing not only on .NET Framework/.NET Core, but also on Mono. It works on Linux, macOS, and Windows (Windows requires installed cygwin with obj and as). (See #541)
• Support ANY CoreFX and CoreCLR builds: BenchmarkDotNet allows the users to run their benchmarks against ANY CoreCLR and CoreFX builds. You can compare your local build vs MyGet feed or Debug vs Release or one version vs another. (See #651)
• C# 7.2 support (See #643)
• .NET 4.7.1 support (See 28aa94)
• Support Visual Basic project files (.vbroj) targeting .NET Core (See #626)
• DisassemblyDiagnoser now supports generic types (See #640)
• Now it's possible to benchmark both Mono and .NET Core from the same app (See #653)
• Many bug fixes (See details below)