[JoshCole]

Seconding this; I switched to Obsidian from Notion and I've been liking it. I also use a plugin called Wielder for it that lets me write codeblocks in my notes and turns my note taking system into a literate programming environment. So I have for example a self-written plugin that applies transformations to existing pages to incorporate the sort of question templates suggested in books like How To Solve It or on websites like untools. I also have certain data structures built into the note environment - stuff like asynchronous task management. Since everything is markdown everything just defaults to working when these higher level tools aren't active because I'm in a no code environment.

What I'm not so certain on is if this is actually helping me think better enough to be worth the cost in time of getting fancy. This is an example of a blog post written basically by stringing together notes from walking a path through the graph of my notes:

- https://joshuacol.es/2021/05/17/virtuous-cycles.html

These are two I wrote before adopting the methodology which I feel a bit happier with because I feel like I learned more in the process of researching them and writing them:

- https://joshuacol.es/2020/03/06/modeling-technical-income.ht...

- https://joshuacol.es/2019/04/23/hypothesis.html

[diggan]

Off-topic maybe, but I'm the author of Obsidian Wielder (https://wielder.victor.earth), so it's great to hear that people in the wild are finding it useful! If you have any sort of feedback how it can help you more, please do let me know!

I'm sure a lot of other Obsidian users here on HN would find Wielder useful as well, but the Show HN I made a while ago didn't get much traction (https://news.ycombinator.com/item?id=31846474), maybe I'll retry once I've added some more features :)

[JoshCole]

Amazing work and thank you so much for making something so cool. With regard to feedback.

- Some features I'm interested in are being able to install libraries or a recommended path for getting access to libraries via RPC to a less limited runtime. For example, lets say I want to use the hugginfaces API to do text extraction within my note. Clojure has some great tools for running arbitrary Python code from within it, but how can I leverage that code from within Weilder.

- Is there planned support for importing from a namespace in another note? My current workflows are everything goes into one note and then I just hide the sections with the code so they don't distract but sometimes there are pages worth of code. I expect over time I'll find a lot of things that have common implementations.

[diggan]

> - Some features I'm interested in are being able to install libraries

Might be tricky to achieve, as I don't think we can load arbitrary files at runtime in Obsidian. What could possibly work, is loading libraries via HTTP and evaluate them in Wielder after that, but would be tricky is my guess. Worth looking into to though.

> or a recommended path for getting access to libraries via RPC to a less limited runtime. For example, lets say I want to use the hugginfaces API to do text extraction within my note. Clojure has some great tools for running arbitrary Python code from within it, but how can I leverage that code from within Weilder.

If you can run a HTTP server locally (via Python's http.server for example), with the right headers set regarding CORS, you should be able to just use JavaScript `fetch` to GET/POST/PUT stuff to locally running servers. In Wielder, you'd do something like `(js/fetch "http://localhost:8080/read-data")` and use it just like you'd use any JavaScript Promise.

> - Is there planned support for importing from a namespace in another note? My current workflows are everything goes into one note and then I just hide the sections with the code so they don't distract but sometimes there are pages worth of code. I expect over time I'll find a lot of things that have common implementations.

Yeah, I'm currently thinking and playing around with how to achieve this, hopefully via supporting Clojure's `ns` declarations directly, so you can do `(ns my-vault.a-page)` in one document and then simply `(ns another (:require [my-vault.a-page :refer [a-func]]))` in another.

For now (with a bit bad UI I'd admit), you can use the normal Obsidian including to reuse code from multiple pages, just uploaded an example here: https://wielder.victor.earth/Examples/Embed+code+from+other+...

Not the best UX directly, and looks bad, so hopefully the whole `ns` endeavor will work out instead, but will take some time before I can implement that correctly.

> Amazing work and thank you so much for making something so cool

Thank you! And thanks a lot for the feedback, it's very helpful.

[lwerdna]

I'm interested in this bit:

> ...lets me write codeblocks in my notes and turns my note taking system into a literate programming environment. So I have for example a self-written plugin that applies transformations to existing pages to incorporate the sort of question templates suggested in books like How To Solve It or on websites like untools.

Do you have any posts or additional information on this in particular?

[JoshCole]

Depending on which particular subject you are interested in:

- The plugin:

https://wielder.victor.earth/Welcome shows the sort of things you can build with Wielder. The github repository for the library is here https://github.com/victorb/obsidian-wielder

- How To Solve it

The key ideas behind How To Solve It are that for a lot of our challenges there are strategies we can use to tackle them effectively. How To Solve It expounds on how to go about understanding a problem, understanding the connection of the data you have with what you don't know, how to make problems more tractable, carrying out a plan, and evaluating the results.

- Untools

A site dedicated to listing various strategies for thinking, communicating and prioritization; they sell templates similar in nature to what I'm building, but I depart sharply from them in my desired document representation choice for templates - Zettlekastian graph continuations for me versus linear documents for them.

- My own tool

This is currently private and not yet ready for public consumption. I have a whole lot of philosophical backing for what I'm trying to build but it is still very far from generating utility at the level I want it too. Later today I'll see about moving some private notes into a blog post going into more depth about what I'm building and why.