Isn’t that a feature?

Oh ohkay. Thanks for clearing up.

The author himself mentioned that it is a staging instance for voyager.

It’s in this comment.

https://github.com/aeharding/voyager/issues/9#issuecomment-1804277817

Great. Thanks 🙌

I want my devices to run on an OS/framework which allows everything to be scriptable. Data should be visualised using simple/consistent interface.

There will be events, Actions, variables, data-streams, etc and the operating system should provide easy interface to quickly create new programs which can

1. Visualize data streams (filterable) using simple interfaces(configurable)
2. Create scripts which can create custom events or custom actions which are just built upon existing events/actions.

In such a system, the focus of apps should not be to add fancy interfaces for simple things, but to register new events, actions, data streams, visualizers into the OS and maybe provide new templates to use these additions.

Don’t have an objective definition of “Best” but here are few over the top of my head.

1. Profiled backend’s startup and reduced startup time by ~20-30 times. Issue was we were traversing node_modules folder to scan for API documentation.
2. Profiled python using cProfiler & snakeviz and optimized dozens of regex calls by simple pre-filtering. Improved performance by ~20 times.
3. Profiled python using pprofile & qcalgrind (IIRC) to pinpoint a single heavy regex compilation and optimized it by pre-filtering. Improved performance 8-10 times.
4. Use nodejs streams to do load data from s3, parse as CSV, transform into different structure and save into s3 in a continuous stream. Didn’t measure the performance gains but should be several times atleast. 5… many more, some coming from embedded world and even more drastic & unexpected

I’m right now using it, and never found any major issue that would stop me from continuing with it.

Can you tell what was the exact issue and what you’re using now?