I will group them into the four following categories:
There was a recent event at Open West 2018 that was magnificent: each person at the conference could come to the Pico Labs booth and register for their own Pico, at which point they would then receive a printed QR code. When scanning the code of other participants (or being scanned by others), a mutual connection would be formed between the Picos of the respective owners. At the close of each day, whoever had the most connections won a prize.
The contest generated interest, the presentation was well-attended, yet none (to my knowledge) have expressed interest to assist in furthering the project. Participants were told that they owned their Pico, but what can they do with it? Without a knowledge of KRL, there is no purpose to log into the Pico in the first place.
KRL Learning Curve
I know that this is a debatable subject, but when it comes to adoption, it’s a big one. Most people out there don’t even want to watch a YouTube video that’s over five minutes, let alone actually READ a post of this length! (Kudos to you for reading this far. Buy yourself a box of your favorite Kudos flavor at your local supermarket the next time that you’re out and imagine that I gave them to you.)
People want a quick answer and a solution that meets their needs (that’s why Stackoverflow is so popular; I can find the answer to my problem fast). For the general populace out there, “Learn KRL” is -not- a response that will resonate with them, especially when the documentation on Attlasian is pages and pages and pages long.
the Pico Engine runs on Node.js; it’s the underlying framework of the system. It is not a far cry to enable rules in the native language of the engine that executes them.
It is the suggestion of the post author that the Developers and Directors of the Pico Labs project give significant consideration to this proposal.