@conaw did an interview and posted it on loom about #roam, amongst other things. Interesting and promising thoughts. Worth listening to if you are a roam enthusiast.
Highlights (having gone through the Chris filter):
- Roam is an R&D company
- Asked about Roadmap - no roadmap (see first bullet to know why)
- Roam prizes allowing community develop solutions
- Channeling Doug Engelbart (if you have to have a role model - good choice)
- Roam learns from community
- But mostly “build” for themselves
- RDF is a consensus, so not looking to lock-in to an approach, roam is map of your mind and minds are different (roammap?)
- Check out hyper graphs & hyperarchs (they have the schemas, need to figure out UX)
Seems like I am not the only one trying to understand the broader “Tools for thought” space
Personal thoughts: really enjoy when Conor is so articulate & cogent. IMHO he has one of the best understandings of this space & likely has the most complete non-roadmap visions when compared to others. Really excited to see what hyper graphs/hyper archs looks like in the end.
When I signed up for Roam I made a mistake thinking it was a product. This interview confirms for me Roam is an R&D prototype, another iteration of iterations. Explains a lot of things.
So now we wait for next prototype or “v1”. I think what will come in a year or more likely two, will be exciting. More patience. I have 9.5 years left on my believer plan, so gives Roam some leeway for experimentation :-)
• • •
Missing some Tweet in this thread? You can try to
force a refresh
OBSIDIAN COMMUNITY REVIEW 1/ I have been promising for some time to write a review of the @obsdmd community. While a "community" is not a product, when it comes to "Tools for thought", community should be viewed as an important feature, not an afterthought or byproduct.
2/ Let me preface this review with a note: For the last year I have been focused on the #roam community & very happy with that. This is not intended as a comparison of these communities, but rather a "new user" experience into the Obsidian community & my first impressions.
3/ What is "Tools" in "TOOLS for Thought"? Tools are the collection of tools we use in leveraging our thoughts in written form. Tools are software, but more importantly include workflows, methods, techniques, practices & algorithms. "Tools" is plural, made up of all these things.
2/ First, Roam42 will be hosted on the same reliable secure & fast service maintained & operated by Dave. Second, 42 will become a part of the powerful free open-source suite of tools at roamjs.com. Dave will be taking the reins 42 as its primary maintainer.
3/ This is a big help to me. I started Roam42 last year when I had more time. But now real life (full time job) beckons, & 42 needs more love than I can give. Dave is primarily focused on extending Roam & has the time to give 42 and its loyal user base the attention it deserves.
We are seeing more & more expressions that the amazing people in the “tools for thought” communities have much more in common than they have differences. Harley has taken this literally. Here he runs @RoamResearch inside @obsdmd. Who says these tools don’t play well together?
+ Who says you can’t have Markdown in Roam?
+ Who says Roam can’t export to Obsidian?
+ I see he is running Roam42 in Obsidian, I didn’t even know that was possible.
+ Obsidian beat Roam to an implementation of the Roam Desktop client.
+ My graph is bigger than your vault.
Ok, having some fun at expense of Obsidian & Roam.
We may have our differences in the way our tools work, but we can collaborate & have a common bond in learning, sharing & growing. Check out this amazing thread between two amazing communities.
By the way this is not a question for any specific tool, rather a broad PKM discussion. The concept of #tags has been around for years now in many products. They exist in @evernote, @RoamResearch, @obsdmd, @logseq, @todoist, etc.
2/ Taggin is even used outside of software. I remember doing GTD years ago, all on paper, and using @ for context and # for categorization. All written out on paper, summarized daily and weekly into lists. (Those were wonderful, simpler times)
3/ Tagging things I found to be very useful in managing present. Do this today #task. Do this at @home. #pending, #somdayMaybe, #people. By having a dozen or so tags, I can nicely focus in on actions and responsibilities in my life.
1/ There is a lot of talk about roam/js and security concerns. Frankly, these issues exist from the first day Roam introduced roam/js. It boils down to trust. Do you trust the plugin author or not? There are some very good plugin authors who deserve your trust. #roam
2/ One of them is @dvargas92495, founder of roamjs.com. What many don't know is that Dave and I have collaborated since last summer. While we have gone different paths, we frequently talk about Roam and how to solve problems. I have always valued his advice.
3/ Dave is a very experienced software dev with an amazing vision for developing & supporting open source. His roamjs.com site focuses on Roam & is a living proof his concept works. https://t.co/qiZcl2mG3K is the biggest and most complete collection of roam plugins.
Since last summer I have been intrigued by this quasi-no roadmap concept from Roam. But now almost a year later, I actually don't think it's a good strategy. @Conaw maybe now is a good time to lay out a plan with the public and timelines.
I see value in the "no roadmap" approach during prototyping & beta, but as the product matures & tackles larger problems, people want to understand what they are investing in. People using a product is an investment. Is the bank going go grow their money, or gain little interest?
Without a roadmap that outlines general goals, how can a team set priorities? how can they design for the future? Databases for example cannot be easily changed, especially when it comes to security, performance and optimized search.