Roam Monkey:
https://roamresearch...acker/page/jI-X_cwaf
-panzer
Here is the maddening dichotomy of Roam, Roamcult, and Conor laid bare: Things like this - which, by the way, looks really useful - are a testament to the flexibility of the system, but also
an indictment of the development priorities of the team lead.
It is on the one hand nice that Roam is flexible and extensible enough that such things can be done within it, despite them not having access to the code. That is really cool, in a way. It allows the community to help cover things that the core devs cannot, and without open sourcing, since not all developers/companies and profit models are amenable to doing so. It does present some security risks to allow this kind of stuff though, even with the warnings.
On the other hand, the security risks are arguably the smaller concern here. A majority of the features in RoamMonkey are highly useful to
most people. They are, in fact, largely features that should be a core part of Roam! Maybe they will be some day, but here's what frustrates me so much. These features were achievable by a self-professed amateur JavaScript developer using only external access. Surely this could be done as well or better and
faster by the internal developers. And yet, in the same several months that this guy has been developing these
highly useful features that almost everyone would use, Conor and his partner(s) have added a
Pomodoro timer,
Mermaid diagrams, and other arguably niche and certainly not "first priority" stuff. This is behavior that users SHOULD NOT accept from a developer of an app they are paying for (and, I would add, paying a premium over many comparable products).
Roam is doing cool stuff, but I refuse to support Conor's self-indulgent approach to development priorities. It's not going to work out well in the long run.
- Oshyan