“This is your last chance. After this, there is no turning back. You take the blue pill — the story ends, you wake up in your bed and believe whatever you want to believe. You take the red pill — you stay…
I am excited about this topic, since the technology we are going to talk about opens the way for a new generation of web-based apps, which can directly communicate across multiple browser windows without involving a backend.
[side note] The article got pretty long. In case you got only a…
This is a huge step for getting UI development back where it belongs:
Into the browser.
Take your skills to an entirely new level by learning to create a visually stunning and blazing fast next generation web app using web workers.
The app as well as your components will live within an application web worker.
This article is challenging, polarising and thought provoking on purpose. It covers a lot of fresh content and ideas which you are most likely not aware of.
Since your apps, including your components, live within the application worker, a question which frequently pops up is:
“Can we use external Web Components within our neo apps?”
The main goal of…
However, there can be use cases where in…
Since workers run inside a separate thread (using your own CPU if possible) this means that expensive app related JS logic can not slow down your Canvas rendering performance and vice versa: expensive logic…
I just needed this widget for the neo.mjs calendar implementation.
Following the “Application worker being the main actor” paradigm, the list lives within the App web worker scope.
The neo.mjs v2.0 release was focussed on the new view models implementation, which enables you to bind component configs to view model data properties anywhere inside the model hierarchy tree.
This article is covering the latest enhancements to make complex application based state management even easier and more powerful.