Live data from Hacker News

Monodraw

monodraw.helftone.com

61–70 of 196 posts

Re: Monodraw

#61
post #49
post #44

Now, that is something really cool, pity we didn't had something like that on BBS days.

Antique furniture meant something- it was done by hand. Same with ASCii- you could respect that it took some time to make it. What respect and feeling will there be for work in the future? Everything generated or thought cheaply generated on whims. Everything throwaway.

Unfortunely the work in the future will be mostly done by our AI overloards.

Re: Monodraw

#63

Will love to buy this once I get my Mac. Looks great, and also love the perpetual license for $9.99 rather than the host of subscription services, i'll probably end up buying it just to support good practices.

That's cool … but we're calling buying an app licensing it now? That word is a red flag for me — wondering what dark pattern is awaiting, finding myself digging for the fine print…

true - it does say personal license, maybe there's some little print that says we own your entire project if it makes over $100

Re: Monodraw

#64
post #24
post #21

Earlier quoted context omitted.

> Monodraw does not use activation or any other form of DRM. We have complete trust in our customers. Interesting. But, why?

Any time spent on copy protection is time not spent on improving the product for the paying customers. I find it unlikely that such copy protection would actually convert a non-paying user into a customer. I also don't want to make the software network dependent in any way.

>I find it unlikely that such copy protection would actually convert a non-paying user into a customer.

I used to think that but then kept tripping across customers who ran multiple copies of my software after purchasing a single license. I now wish I'd tightened the DRM from the start.

Re: Monodraw

#65
post #23

Earlier quoted context omitted.

Windows version in the future?

There are no current plans but never say never (the app is 100% AppKit, so porting means a full rewrite). I wish I had the time to port it to all three desktop OSes.

ok.. web app? (not a programmer, so no idea if a web app is any different from a development standpoint)

Re: Monodraw

#66

Bought this couple months ago, and am now always looking for more ways to include this for inline-documentation. the fact i can export to clipboard and re-import it and reconstruct all the shapes etc. almost flawlessly is such a big win.

Absolutely love monodraw for diagrams in documentation! All of the diagrams for Oban and Oban Pro are done this way:

Job Lifecycle: https://hexdocs.pm/oban/job_lifecycle.html

Composition: https://oban.pro/docs/pro/1.6.4/composition.html

Re: Monodraw

#67
I use Mermaid and such for a lot of technical documentation, but this seems like it's going to be much more straightforward, especially for quick and one-off diagrams.

Very nice.

Re: Monodraw

#68
This at least 10th post of Monodraw on hn

https://news.ycombinator.com/item?id=8433417 - oct 09 2014

https://news.ycombinator.com/item?id=9545252 - may 14 2015

https://news.ycombinator.com/item?id=27832910 - july 14 2021

https://news.ycombinator.com/item?id=32134469 - july 18 2022

https://news.ycombinator.com/item?id=39651796 - march 9 2024

https://news.ycombinator.com/item?id=45037904 - 1 year ago

and the some

all of these gained interest, so my conclusion is Monodraw benefits a lot from being regularly exposed to HN crowd.

Re: Monodraw

#69
post #23

Earlier quoted context omitted.

There are no current plans but never say never (the app is 100% AppKit, so porting means a full rewrite). I wish I had the time to port it to all three desktop OSes.

as a noob Swift dev (Swiftie?) , why AppKit over SwiftUI? Maturity of former?

Not the OP but Monodraw predates SwiftUI by quite a while. On top of that SwiftUI is pretty bad on macOS.

Re: Monodraw

#70

Bought this couple months ago, and am now always looking for more ways to include this for inline-documentation. the fact i can export to clipboard and re-import it and reconstruct all the shapes etc. almost flawlessly is such a big win.

On one hand, this could provide a lot of value as some things are just plain hard to explain using only words. On the other hand, aren't you worried about when someone else comes along and needs to update one of those comments? If they're not aware of this tool, it's either going to be incredibly tedious or simply not going to happen.

As the other commenters put it, i dont think this is a huge issue. I usually use this for architecture level diagrams, and that shouldn't change often/at-all. In-case it does change, doing a new diagram is perfectly in-scope of whoevers working on that.
Post reply on HN