slides VS mam_mol

Hello, my name is Dmitriy Karlovskiy and all my articles (and presentations) I write in MarkDown. And you know what? It's already pretty sick of me! I write texts in Russian, but most of the special characters are only in the English keyboard layout. And editing tables is the eternal Leaning Tower of Pisa from vertical lines. In short, is has problems both with the convenience of editing and with the readability. So let's try to design it from scratch, without dragging tons of puzzling structures along with us.

Framework $mol

This is an extended text version of the speech of the same name on PiterJS#47. You can read it as an article or open it in the presentation interface or watch video.

Original Russian article

And for those who, for some reason, are not yet ready to completely switch to the $mol framework, we have prepared several independent micro-libraries:

Do you want to try ReactiveDOM in action right now? I published a prototype of the polyfill $mol_wire_dom.

To do this, we will first take $mol_jsx, which is the same as E4X creates real DOM nodes, not virtual ones:

Well, let's cure the patient, and at the same time show the ease of integration of the reactive library $mol_wire into a completely foreign architecture.

We have omitted some methods here. The complete set can be found in the sources $mol_wire_set.

As you can see, proceduralism is more popular here, which is also not the most practical approach. And the most practical thing here is Vue. Only $mol is cooler than it, but there is no point in considering it separately as a framework, because it simply uses the $mol_wire library as a circulatory system, and we have already analyzed it earlier.

$mol_wire_sync makes any API synchronous.