No hiring page yet, just dm @conaw on twitter for now
Good point. Will update.
Capability is there, but UX sucks for both sharing single pages and creating seperate workspaces. Been working on both this week.
Might not be for you. Most of benefit is in the new workflows you get via backlinks.
Blocks (paragraphs with subtrees) as first class objects with uids that can be pointed to. Pages as filterable collections of backlinks from blocks. A datalog engine for structured data via attributes. Collaborative…
Dev here - open to suggestions
TiddlyWiki is great, was one of many tools I used before starting to work on Roam. Lack of easy collaborative option and the speed of organizing sets of intersecting sets of notes were some of main reasons I needed…
Datalog :)
One of the devs here - totally true, our help docs and landing page don't really show half of what you can do. Help docs have a lot if you dig around though. Heres a link…
Just as FYI - Roam is built in Clojure/Clojurescript and we're hiring
Play in the Sandbox on the help db for an hour and see if you still think this.
Shouldnt be true for JSON export.
Use nvalt till that ships then, import will be easier, and you'll start to taste power of very fast two-way links.
We store in cloud as it is a collaborative app, designed for building off your own and other's past work. Lots of self hosted options that are much better than evernote or todoist. Org mode for one. Worth learning emacs…
Or control-shift-O when cursor is hovering over a link to open page or referenced paragraph/subtree (block) in sidebar.
Problem w evernote is that file is bad unit of organization. In a meeting with 4 people, discussing three big ideas, related to two projects, what file do you put the note in? In Roam that's not even a question you have…
Co-founder here. Best self hosted tools are Org-mode and nValt. Neither have full feature set, or work collaboratively, but nvalt in particular gives a good 80/20. We export to plaintext markdown that reads well in…
Co-founder of Roam here. Also huge fan of treesheets, do recommend. We export to markdown and JSON.
Also -- for folks asking about how we're different from Workflowy or Evernote or existing wiki tools Key claim we have is that knowledge doesn't really fit into the tree structure of a file system (nearly 100% of…
You can import any plain text or markdown file into Roam -- we take the indentation structure and parse it out. Can also copy/paste in any html Would build a special emacs importer if there was strong need -- but emacs…
Cofounder here -- just want to let people know that we STRONGLY believe that your data shouldn't be trapped in a SAAS application. Roam does allow you to export all your data to an org-mode file (the emacs outliner),…
The fact that folks in the comments are complaining here about Clojure's error messages here tells me that the implications of this post might not be obvious. Up to this point, it has been really really hard to give…
It means you may soon have amazing error messages when working with Clojure. You'll also be able to write your code in such a way that it gives you amazing error messages when some part of it breaks.
Solving that is what this post is about
"In my humble opinion clojure.spec is the most VPRI-worthy feature Rich Hickey has shipped since delivering fast persistent data structures." Love this quote
No hiring page yet, just dm @conaw on twitter for now
Good point. Will update.
Capability is there, but UX sucks for both sharing single pages and creating seperate workspaces. Been working on both this week.
Might not be for you. Most of benefit is in the new workflows you get via backlinks.
Blocks (paragraphs with subtrees) as first class objects with uids that can be pointed to. Pages as filterable collections of backlinks from blocks. A datalog engine for structured data via attributes. Collaborative…
Dev here - open to suggestions
TiddlyWiki is great, was one of many tools I used before starting to work on Roam. Lack of easy collaborative option and the speed of organizing sets of intersecting sets of notes were some of main reasons I needed…
Datalog :)
One of the devs here - totally true, our help docs and landing page don't really show half of what you can do. Help docs have a lot if you dig around though. Heres a link…
Just as FYI - Roam is built in Clojure/Clojurescript and we're hiring
Play in the Sandbox on the help db for an hour and see if you still think this.
Shouldnt be true for JSON export.
Use nvalt till that ships then, import will be easier, and you'll start to taste power of very fast two-way links.
We store in cloud as it is a collaborative app, designed for building off your own and other's past work. Lots of self hosted options that are much better than evernote or todoist. Org mode for one. Worth learning emacs…
Or control-shift-O when cursor is hovering over a link to open page or referenced paragraph/subtree (block) in sidebar.
Problem w evernote is that file is bad unit of organization. In a meeting with 4 people, discussing three big ideas, related to two projects, what file do you put the note in? In Roam that's not even a question you have…
Co-founder here. Best self hosted tools are Org-mode and nValt. Neither have full feature set, or work collaboratively, but nvalt in particular gives a good 80/20. We export to plaintext markdown that reads well in…
Co-founder of Roam here. Also huge fan of treesheets, do recommend. We export to markdown and JSON.
Also -- for folks asking about how we're different from Workflowy or Evernote or existing wiki tools Key claim we have is that knowledge doesn't really fit into the tree structure of a file system (nearly 100% of…
You can import any plain text or markdown file into Roam -- we take the indentation structure and parse it out. Can also copy/paste in any html Would build a special emacs importer if there was strong need -- but emacs…
Cofounder here -- just want to let people know that we STRONGLY believe that your data shouldn't be trapped in a SAAS application. Roam does allow you to export all your data to an org-mode file (the emacs outliner),…
The fact that folks in the comments are complaining here about Clojure's error messages here tells me that the implications of this post might not be obvious. Up to this point, it has been really really hard to give…
It means you may soon have amazing error messages when working with Clojure. You'll also be able to write your code in such a way that it gives you amazing error messages when some part of it breaks.
Solving that is what this post is about
"In my humble opinion clojure.spec is the most VPRI-worthy feature Rich Hickey has shipped since delivering fast persistent data structures." Love this quote