Component inheritance in Angular is a feature that doesn’t seem to get a lot of love. Maybe it’s the tie to object-oriented programming which is losing a little love to the functional programming trend. However, I’ve found component inheritance to be just the right fit for a number of use-cases. 

BitOps is an open source Docker image created by Bitovi that bundles popular deployment tools with the understanding of what to do with an operations repository. This coupling makes it easier than ever to set up the automated deployment of cloud infrastructure. However, BitOps requires an operations repository to work its magic.

This is part 2 of a BitOps tutorial series:

• Part 1: Introducing BitOps

Defining infrastructure as code repositories to handle complex systems with automated pipelines is difficult to manage at scale. BitOps is a solution to describe your infrastructure and the artifacts deployed onto that infrastructure for multiple environments in a single place called an Operations Repo. It was created and open-sourced by Bitovi.

This is part 1 of a BitOps tutorial series:

• Part 2: BitOps, Yo!
  

If you're dealing with forms in Angular on a regular basis one of the most powerful things you can learn is how to use the Control Value Accessor interface. The CVA interface is a bridge between FormControls and their elements in the DOM. A component extending the CVA interface can create a custom form control that behaves the same as a regular input or radio button.

Angular's Reactive Forms give us immense capabilities with its robust API, but the learning curve can be a bit steep from plain old template-driven forms that many are used to. This quick guide will explain Angular's main form elements and how to combine them, nest them, and dynamically create them in almost any scenario.

At Bitovi, we’ve been working on utilizing HTTP streaming to speed up single-page application (SPA) load times for the last couple of years. We’ve developed a technique that accelerates page load times that we call incremental rendering, which went into DoneJS 3. Today we’re happy to announce another project, Velocirender, which brings incremental rendering to any framework.

This article will: