Kirit Ayya kiritAyya

How to install, uninstall and upgrade Neovim

Via Neovim Release

Step to install

Chose Neovim version under Assets section (ex: NVIM v0.7.0)
Download nvim-macos.tar.gz
Extract: tar xzvf nvim-macos.tar.gz
Run ./nvim-osx64/bin/nvim

Getting started with Linux kernel development

Prerequisites

The Linux kernel is written in C, so you should have at least a basic understanding of C before diving into kernel work. You don't need expert level C knowledge, since you can always pick some things up underway, but it certainly helps to know the language and to have written some userspace C programs already.

It will also help to be a Linux user. If you have never used Linux before, it's probably a good idea to download a distro and get comfortable with it before you start doing kernel work.

Lastly, knowing git is not actually required, but can really help you (since you can dig through changelogs and search for information you'll need). At a minimum you should probably be able to clone the git repository to a local directory.

Comprehensive Introduction to @ngrx/store

By: @BTroncone

Also check out my lesson @ngrx/store in 10 minutes on egghead.io!

Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!

Table of Contents

	<h1>Angular 2 Recursive List</h1>
	<ul>
	<ng-template #recursiveList let-list>
	<li *ngFor="let item of list">
	{{item.title}}
	<ul *ngIf="item.children.length > 0">
	<ng-container *ngTemplateOutlet="recursiveList; context:{ $implicit: item.children }"></ng-container>
	</ul>
	</li>
	</ng-template>

	// Package main is an example of how handler pattern works in golang.
	//
	// At first you will need some sort of start point. To do this we create
	// ExampleHandler interface, this interface has a trigger method that will
	// execute the chain, in his case is RunExample, it accepts a writer, and a
	// custom input object, as you see there is an out and an in parameter.
	//
	// We could work like this you can create multiple ExampleHandlers in a helper
	// function and call them on in another. But this is not very handy and it smells
	//

	if _, err := os.Stat("/path/to/whatever"); os.IsNotExist(err) {
	// path/to/whatever does not exist
	}

	if _, err := os.Stat("/path/to/whatever"); !os.IsNotExist(err) {
	// path/to/whatever exists
	}