Web Worker is a modular script that runs separately from the main JS thread (a thread that normally includes all the scripts of your web application) and communicates with it using events only.
Nowadays there’re lots of technologies in a Front-end and most of them have easily understandable tutorials. So starting with them is not a problem. But there’s always a problem when you try to use some of them together. In this article, we’re going to talk about a usage of Angular or Vue.js together with D3.js, and find out why we might have problems with the integration.
After some portion of theory it will be a good practice to do some practice! So today we’re going to build weather widget with auto update function and simple chart that will be fully built using RxJS. Take your knowledge of base concepts, that we’ve studied on previous lesson and let’s go!
The methods that are covered in this video are flattop, concat/merge, switch, switchMap. Main topic of video is more complex structures – higher order observables. Also we’re going to talk about handling of async stuff inside observables with life example of working with real API. Subscribe to our channels! Youtube Facebook Twitter LinkedIn Instagram Google […]
The methods that are covered in this video are map, filter, reduce, take/skip and distinct. Most of them are array-like primitives they will give you the basis of your further work with RxJs and introduce main instruments from this large swiss knife!
Our today’s heroes are Publisher / Subscriber pattern and the Mediator pattern. Basically, I created this video to explain the difference both to patterns and Observer pattern …
Our today’s topic is a library for working with streams and events. It’s RxJS and it represents the idea of reactive programming. In the simple words, the meaning of this idea semantically is a representation of all operations as the stream, more specifically, as the sequence of events. Programmatically it means for our usage of two patterns: iterator (for establishing of the sequence itself and going through this one) and observer (for changes propagation).
Use when you want to select between different algorithms in the process of task resolving. So basically all that you need to realize this pattern are strategies (each of them in the separated component/class, but with the same interface) and strategy selector (decides what strategy is more effective at the moment and uses it).
The main idea is a creation of simplified interface to application functionality. Basically, when you create components of your application the interfaces of these ones can be really complicated for outside usage. So to resolve this problem and provide easy-to-go solution, you can use Façade.