Echo JS 0.11.0

submitted to the german gov hackathon #WirVsVirus 

https://devpost.com/software/covid-dashboard

https://www.youtube.com/watch?v=BhSZS6_UlO4

I am super excited to announce the biggest spin-off release since the neo.mjs framework went public.

You can find the Desktop Online Versions here:https://neomjs.github.io/pages/ (COVID-19 Dashboard App)

The new Dashboard App is a tech-demo to showcase a firework of CSS3 animations combined with webworker-driven delta updates.

Mobile support is not finished yet.

The app was crafted inside the neo.mjs repository, so you will find the commit log here:https://github.com/neomjs/neo/commits/dev

Quick update:

https://github.com/neomjs/neo
just hit 1000 commits since the public release (making it 4720 in total). v1.0.47 published on npm.

since this project is still widely unknown, it would mean a lot if you could just tell one friend about it (or share this post).

thanks a lot!

#neomjs #javascript30 #100daysofcode #webdev #webdevelopment #frontend #framework #html #html5 #webworker #multithreading #virtualdom #developer #oss #mit

thanks for the heads up, will try to post less frequently.

the next release will be the covid app combining the gallery, helix & table with some advanced component controller & routing logic.

i can write a blog post about creating this one. the current status is here: https://github.com/neomjs/neo/tree/dev/apps/covid

in case you would like to see an article about a specific topic, please let me know.

best regards, tobias

OSS (MIT license)

In short: The goal is to create a webworkers driven UI framework. Most parts of the framework as well as all apps you create run within the App thread. There is a data & a vdom worker in place as well. Having an idle main thread ensures that all UI related animations run as smooth as possible.

The main difference to other frameworks is, that you describe the component tree as well as the virtual dom tree via JSON. This enables us to combine and manipulate those with a very high performance plus it creates clean code.

One major design goal is to have all ES8+ classes / JS modules running inside the browser without any JS related builds. Right now this only works for the dev mode in Chrome 80+, for other browsers & dist versions there are webpack based build processes in place.

The dev mode results in a very smooth debugging experience, since you don't need source-maps and debug the real code 1:1.

On the roadmap are (e.g.)
1. Mobile Support
2. A buffered Grid
3. Drag & Drop
4. Data Package v2

(and a lot more => vision file)

Online Demos (Desktop!) are here:
https://neomjs.github.io/pages/

Short demo video on the helix component:
https://www.youtube.com/watch?v=iztv8YxWYUU

short demo video of the helix:
https://www.youtube.com/watch?v=iztv8YxWYUU

You will get by far the best experience using Chrome 80 in an desktop environment.

Direct link to the online examples (COVID-19 Helix):
https://neomjs.github.io/pages/

Feedback appreciated!

More input:

I spent 1.5 years of my full and unpaid working time to get the neo.mjs project to this point. In opportunity costs this already adds up to USD 600.000 (obviously this is not related to the "value" of the project).

I presented this work on a silver platter, free to use for anyone who likes to give it a try.

What I most definitely underestimated is the curiosity and acceptance of other developers regarding OSS projects, especially in the area of frontend frameworks.

Which led to this topic: Does anyone have recommendations on how to get early stage OSS projects sustainable?

There is a long term Business Model in place, if the project does get traction (e.g. trainings, support, PS).

The code base itself will stick to the romantic idea using the MIT license.

Took the time to write an intro guide, explaining the web worker setup and the json based virtual dom.

Feedback greatly appreciated!

Thanks & best regards, Tobias