WebAssembly (WASM) is the new web standard, it is a new type of code designed to be faster to parse than JavaScript and faster to execute. It is also designed to run alongside JavaScript, allowing both to work together.

WASM is supported in all modern browsers.

Why we should care about WebAssembly?

It provides a way to run code written in multiple languages on the web at near native speed.

using the WASM JavaScript APIs, we can load its modules into a JavaScript app and share functionality between them. This allows taking advantage of WebAssembly's performance and power and JavaScript's expressiveness and flexibility in the same apps.

Watch this video from Mozilla.

Is it a web standard?

WebAssembly is an emerging standard, with ongoing work on the specification. The browser vendors have reached consensus on the design of the initial wasm API and binary format, and it is being developed as a web standard with an active group via W3C WebAssembly Working Group with members from Mozilla, Microsoft, Google, and Apple.

How is this different from JavaScript?

The key words are low-level. It defines primitives including a range of types and operations on those types, literal forms for them, control-flow, calls, a heap, etc…

These are very simple primitives, No complicated object system, No built-in automatic garbage collector following you around and stopping you periodically while it cleans up your scraps.

An important fact to know is, WebAssembly is backward compatible. In fact, there is no versioning.

Progressive Web Apps (PWA) are the next big thing in web development as they bring mobile-app-like experiences to users without requiring them to install an app from the app store/ play store. It is now the new way to deliver amazing user experiences on the web.

What is it? and Why do we need it?

It is the same web but better. PWA's allow us to develop great websites that can behave like native apps.

Below are some advantages of it,

• Load's instant, even in uncertain network conditions.
• Responds quickly
• Behaves like a native app with features like adding to Home Screen, push notifications, accessing to Camera, splash screen etc.,
• Work's offline with Service Worker.
  many more...

We need it as PWA's will help for higher conversions and increases user engagement.

What are qualities of PWA?^[1]

• Progressive - Work for every user, regardless of browser choice because they’re built with progressive enhancement as a core tenet.
• Responsive - Fit any form factor, desktop, mobile, tablet, or whatever is next.
• Connectivity independent - Enhanced with service workers to work offline or on low-quality networks.
• App-like - Use the app-shell model to offer app-style navigations and interactions.
• Fresh - Always up-to-date thanks to the service worker update process.
• Safe - Served via TLS to prevent snooping and make sure content hasn’t been tampered with.
• Discoverable - Are identifiable as “applications” thanks to W3C manifests and service worker registration scope allowing search engines to find them.
• Re-engageable - Make re-engagement easy through features like push notifications.
• Installable - Allow users to “keep” apps they find most useful on their home screen without the hassle of an app store.
• Linkable - Easily share via URL and not need complex installation.

Basic Progressive Web App Checklist

• Site is served over HTTPS
• Site is responsive across phone, tablet and desktop screen sizes
• All app URLs load while offline
• Metadata provided for Add to Home screen
• First load fast even on 3G
• Site works cross-browser
• Each page has a URL
• Page transitions don't feel like they block on the network

How to test Tools PWA?

Lighthouse Chrome Extension will provide analysis of PWA's

Here is the amazing list of PWA's available over web.

Cover Image^[2]

Wiki ↩︎

Google ↩︎

Many times we wanted to return multiple values, one solution is to create a model class and returning an instance of it.

Starting with C# 7, we can easily return multiple values using Tuples.

Tuples allow us to,

• Create, access, and manipulate a data set
• Return a data set from a method without using out parameter
• Pass multiple values to a method through a single parameter

If applications target .NET Framework is 4.6.2 or lower then install NuGet package System.ValueTuple.

Use below command to install via Package Manager CLI.

 PM> Install-Package System.ValueTuple

Below is a simple example using Tuples:

 using System;

 class Program
 {
    static void Main()
    {
        Tuple<int, string, bool> tuple=new Tuple<int, string, bool>(2610, "Microsoft", true);
        // Using tuple properties.
        if (tuple.Item1 == 1)
        {
            Console.WriteLine(tuple.Item1);
        }
        if (tuple.Item2 == "dog")
        {
            Console.WriteLine(tuple.Item2);
        }
        if (tuple.Item3)
        {
            Console.WriteLine(tuple.Item3);
        }
    }
 }

There are various ways of declaring Tuples as below:

 // using keyword
 Tuple<int, string, bool> t1=new Tuple<int, string, bool>(2610, "Microsoft", true);

 // without Tuple keyword
 (int, string, bool) t1=(2610, "Microsoft", true);

 // using named variables
 (int uniqueId, string fromName, bool isValid) t1=(2610, "Microsoft", true);

When working with Sitecore with Powershell Extensions, Powershell ISE prompts/alerts are distracting.

Below change in configuration will help to overcome the same.

Search for Cognifide.PowerShell.config in App_Config\Include folder in sitecore web root.

<tokens>
    <token name="Default" expiration="00:00:00" elevationAction="Allow"/>
    <token name="Console" expiration="00:05:00" elevationAction="Allow"/>
    <token name="ISE" expiration="00:05:00" elevationAction="Allow"/>
    <token name="ItemSave" expiration="00:05:00" elevationAction="Allow"/>
</tokens>

Update the configuration as required, above example is suggested only for Local environment only.

elevationAction can be any value as below:

• Block - always block action
• Password - Ask for Password to elevate session
• Allow - Always allow to elevate session without asking

expiration is TimeSpan serialized for how long session should stay elevated.