Compared to the other articles in this series, this article includes a set of short notes (recipes) that are useful to understand the Type system in JavaScript.
It is a common misconception that JS does not have types. In contrast to typed languages, js follows a slightly different approach in handling types. As a ground rule, I usually adhere to the following statement when thinking about types in JS.
The prototype of the Javascript Function object exposes two valuable methods named call() and apply(). In this article, we will see how to use these two methods effectively in our code. The content and some examples of this article are based on the MDN documentation of the Function.prototype.call() and Function.prototype.apply().
A JavaScript object is composed of a set of property: value pairs, where the
property is a string and the value can be any valid JavaScript data type. Here is an example.
const user = {
name: 'John',
};
Most of the time, developers deal with the value part of the object properties. We define object property values in a variety of ways ranging from strings, numbers, objects, and functions, etc. But we care less about the characteristics of the property part. Generally what we know about an object property is that,
In this post, we will find out why JavaScript inheritance looks different compared to other programming languages. We will cover the below topics.
While JavaScript has gained huge popularity over the past decade, developers still struggle on understanding how it models inheritance. This is due to the unconventional way that JavaScript approaches this OOP concept.
Let's see why, by starting from the basics.
If you are reading this post, there is a high chance that you might be using various software, apps, or tools at work and in your personal life. Haven't you ever wondered that most of those apps share a common set of features? Haven't you ever felt that most of them can be combined into one app or a platform so you can manage everything from a single place?
Low or no-code platforms (will be referred to as 'low code platforms' hereafter) are there to solve this problem. In the first article of this series, Introduction to "Low | No Code Software Development", I explained why such a discipline exists and its evolution.
Computing goes back to the age where our early ancestors used Abacus for calculations. Since then, the concepts like calculation, computation, data gathering, data processing have been evolved to a great extent. These concepts have played a vital role in the daily life of humans for a long time. As we evolved to be an intelligent race, there was one critically important skill which helped us to distinguish from other animals. That was the capability of finding ways to automate things.