Yeah, honestly, sometimes I feel frustrated trying to explain it, because I know some people will never be satisfied. I just want to be transparent about the tradeoffs and let people SEE the actual usage (even if it will indeed not convince everyone).
yap...thats the thing...you never know...the interesting conversations can only happen only when we are open and ready to accept also the banal ones :)
thats super sad....I dont have a problem with someone not wanting chit chat but isnt better to just say "hey, today I am not in much mood to talk" or to show it and to make it happen without explicitly selecting it in an app.....
we are indeed looking at the docs again. To begin with we focused on the tool itself so some of the examples that you see can indeed be worth revisiting and re writing. :) But I hope you can focus and zoom in to the tool itself and see how this can help you with your API workflows.
True. Background of the story of how I learnt is in my tai chi class where I asked the teacher if they also do king fu there. And they told me that well tai chi is also part of kung fu.
depends on what you want to focus on - for example I like the reusable blocks and the programmable interface + the idea of community plugins that extend the tool!
feel free to play around and tell me what you thought - especially around the reusable blocks: most devs we talk with consider this to be the most "different" thing and what is more different than other clients.. For me its this one too + the plain text files all the way from specs, tests, docs, context etc...
Hey :) Voiden is not a rich text editor (non offense to rich text editors). It is executable API docs: requests, docs, and explanations that all live in Markdown… and actually run. (Yes, your docs that do stuff). As far as I know it is the first tool to collapse design, testing, and documentation into one file, one format, one workflow. If you know another tool that does this, I genuinely want to hear about it (definitely not trying to be cocky, just curious :)
Yaak has some ideas and concepts that I like a lot. One thing that is similar with Voiden is that they are extensible through plugins. This way the core can stay lean and new functionality can be added up without bloating the app.
hey - thats great :) Happy you downloaded it :) curious to hear your feedback - I will send you a discord link as a message so its not seen as spamming.
Let me see if I understand your question: you mean how Voiden would look when its more mature?
What I am most excited about is that Voiden already does a few things differently from most API tools. Reusable blocks, plain-text everything, and the ability to go from testing to docs to publishing from a single source are already working and shaping how teams can work in a more consistent way.
There is still a lot ahead (for example I want to see what kind of plugins people come up with for the tool, or how AI will eventually play a bigger role) but the principles of Voiden (reusability, composability, plain text, collaboration through git, single source of truth etc.) are the ideas I believe will define and set a new tone/standard of how API tools should be.
haha indeed - modern has this "blinking lights" connotation. something that is shiny.
True story - once, in primary school, I went to a halloween party, where all the boys were dressed as batman and all the girls as macarena (guess my age). The host of the party was maybe the only one not dressed as batman.
He was wearing some weird jell in the hair, like a punk kind of thing, with a lot of strass, stars all over his body, some heart or thunder shaped big mirror glasses, a shiny jacket and the best looking blue mocasines I have ever seen. He also had a big radio antenna (??) coming through his nylon electric yellow vest.
I asked him: what are you dressed as? and he replied: "Modern".
bruno does have a paywall last time I checked :) but the point is not to have tool debates :) my main point is around overall philosophies and ways that new things are like older things with a small twist.
Yeah, honestly, sometimes I feel frustrated trying to explain it, because I know some people will never be satisfied. I just want to be transparent about the tradeoffs and let people SEE the actual usage (even if it will indeed not convince everyone).