What every JavaScript developer should know about Unicode

Dmitri Pavlutin on javascript, unicode, ecmascript-2015, string |

This story starts with a confession: I was afraid of Unicode for a long time. When a programming task required Unicode knowledge, I was searching for a hackable solution for the problem, without detailed sense what I was doing. My avoiding continued until I faced a problem that required detailed Unicode knowledge. There was no way to apply situational solutions. After applying some efforts, reading… Continue reading

Comments

The art of writing small and plain functions

Dmitri Pavlutin on javascript, clean-code, small, plain, function |

The complexity of software applications is growing. The code quality is important in order to make the application stable and easily extensible. Unfortunately almost every developer, including myself, in his career faced with bad quality code. And it's a swamp. Such code has the following harmful characteristics: Functions are too long and do too many things Often functions have side effects that are difficult to… Continue reading

Comments

How to iterate easily over object properties in JavaScript

Dmitri Pavlutin on javascript, es2017, ecmascript-2017, object, property |

I like my code to be elegant and efficient. The logic should be straightforward to make it hard for bugs to hide, the dependencies minimal to ease maintenance [...]. Clean code does one thing well. Bjarne Stroustrup, inventor of C++ In the same period of ECMAScript 2016 release in June 2016, JavaScript developers are happy to know that another bunch of awesome proposals reached the stage… Continue reading

Comments

Make your JavaScript code shine: knockout old ES5 hacks (Part 2)

Dmitri Pavlutin on javascript, es2015, ecmascript-2015, class-inheritance, string |

Many developers were frustrated about JavaScript, especially before ECMAScript 2015 standard. And they had the right too: the language is known for its weakness and initial design drawbacks. How did it happen? At the beginning of the web era, no one did know how exactly the web will look in 10 - 15 years. And especially that a small Java's brother JavaScript will become the… Continue reading

Comments

Make your JavaScript code shine: knockout old ES5 hacks

Dmitri Pavlutin on javascript, es2015, es2016, ecmascript-2015, ecmascript-2016, hacks-dont-pass |

It's known that before ECMAScript 2015 JavaScript language was tricky. For simple scripts ES5 code works fine. But as soon as the application complexity grows, you start to feel that the lack of language constructs is making your code unpleasant. Because you have to implement the application requirements, you can't jump over the parts of code that are troublesome to implement in ES5 style. The… Continue reading

Comments

Detailed overview of well-known symbols

Dmitri Pavlutin on javascript, symbol, iterator, well known symbols, ecmascript-2015, es2015 |

Symbol is a new primitive type available from ECMAScript 2015, which allow to create unique identifiers let uniqueKey = Symbol('SymbolName'). You may use symbols as keys of properties in objects. A list of symbols that JavaScript treats specially is published as well-known symbols. Well-known symbols are used by built-in JavaScript algorithms. For example Symbol.iterator is utilized to iterate over items in arrays, strings, or… Continue reading

Comments

JavaScript variables lifecycle: why let is not hoisted

Dmitri Pavlutin on javascript, let, const, class, var, hoisting, temporal dead zone |

Hoisting is the process of virtually moving the variable or function definition to the beginning of the scope, usually for variable statement var and function declaration function fun() {...}. When let (and also const and class, which have similar declaration behavior as let) declarations were introduced by ES2015, many developers including myself were using the hoisting definition to describe how variables are accessed. But after more… Continue reading

Comments

Why object literals in JavaScript are cool

Dmitri Pavlutin on javascript, ecmascript-2015, es6, object literal, object initializer, prototype, super |

Before ECMAScript 2015 object literals (also named object initializers) in JavaScript were quite elementary. It was possible to define 2 types of properties: Pairs of property names and related values { name1: value1 } Getters { get name(){..} } and setters { set name(val){..} } for computed property values Sadly, the object literal possibilities match into a single example: Try in JS Bin var myObject = { myString: 'value 1', get myNumber(… Continue reading

Comments

Must know details about ES2016 features

Dmitri Pavlutin on javascript, array, includes, exponentiation operator, ecmascript-2016 |

Good news, in June 2016 ECMAScript 2016 was approved. It contains the features that passed the stage 4, which means finished, of the TC39 process: The array method includes() The exponentiation operator base ** exponent This edition is smaller than ECMAScript 2015, but it doesn't mean less important. Still it has details that you should know before using the new features. The new method array.includes(… Continue reading

Comments

Yes. JavaScript rises.

Dmitri Pavlutin on javascript, rise, history, ecma-262, ecmascript-2015 |

It is hard to find a developer who didn't write JavaScript code. These days ECMAScript 2015 makes JavaScript the supreme leader of the Web. Let's see how JavaScript rises from a complementary language back in 1995 until these days, when it becomes very popular and conquerors the client and server side web development. The dark JavaScript was created in about 10 days by Brendan Eich… Continue reading

Comments