[helloanoop]

yup! every postman alternative just follows postman playbook

starts as offline

vc funding

enables cloud sync for collaboration with teams

deprecates offline as scratchpad

deletes scratchpad

Its been like this for a decade now.

With Bruno the key insight was to store collections and requests as folders and files, and design a markup language that makes it easy to collaborate with your team. I wrote about this here: https://www.usebruno.com/blog/the-saas-dilemma

[_thinx]

How do you avoid that at Bruno v1.0.0 ? I means Postman playbook > vc funding

[helloanoop]

Here is how we avoid that in v1.0.0

I have penned down some thoughts: https://github.com/usebruno/bruno/discussions/269

Would love you to hear your thoughts and perspectives.

[_thinx]

Just read your idea.

Sometimes, I wish that I am a billionaire, so that I could let people using my software for free, completely. And the key point is, they know that it is free, absolutely. Because I am a billionaire, they know.

So, just keep it up. Anything you wrote is not important than the thing you do. Don't let people sink you in their perspective about the world they saw.

Open-source software needs a ton of efforts, tears, bloods. Above of the passion, you know that it should be pay-off, fair-price at least, for you and your people hard-works.

At the end, plan is just a plan. Just go to have a chance to fix it.

Good luck and best wishes!

[SergeAx]

MIT license. If the product is success and has significant devs following - they will just fork it from the commit before relicensing.

[helloanoop]

Yes MIT license is a great plan b. But forking is hard and painful. Elastic/MongoDB/HashiCorp and many more OSS keep moving towards Business Source License to protect themselves from bigtech monetizing the original creators hard work.

What we need is a better approach. One that doesn't involve VC funding. One that keeps the all the incentives of the community, contributors and the creators aligned.

Will share a draft of this approach soon (likely tomorrow) and open it up for community discussion. I want Bruno to be there for the long term.

[bafe]

My only doubt is whether you need to design a special "language" to store the queries/configurations. Wouldn't it be easier to leverage existing languages, maybe something like dhall?

[helloanoop]

Yes, The language itself went through many iterations. You can look at these 3 iterations here: https://ibb.co/8j8yM1f

First was break a giant collection json and save it as individual files, second attempt was to convert into a dsl (was a bit like xml), the third attempt that is used today to make it even simpler.

The key driving force behind the language design was to make sure that it was simple and readable enough to be able to do a PR review flow in git.

Also, simple enough so that you can open the collection folder in a editor (like vscode) and still be able to make changes

Json didn't support multiline strings. Yaml was indentation hell. I wanted something neat, no need for quotes around strings. And lot of nuances, like how do you store a query param as disabled.

you can read more about the lang design at: https://docs.usebruno.com/bru-language-design.html