3 ms·
Here's another argument from last year: https://www.ilograph.com/blog/posts/its-time-to-drop-drag-and-drop-diagram-tools/ https://www.ilograph.com/blog/posts/it
by Veuxdo 4y ago
Here's another argument from last year: https://www.ilograph.com/blog/posts/its-time-to-drop-drag-and-drop-diagram-tools/ https://www.ilograph.com/blog/posts/its-time-to-drop-drag-an...
As for Haskell... while I think architecture diagrams should be written in code, they shouldn't be written in a programming language. Programming languages are for writing, well, programs. Programs execute, accept input, have state, and all manner of other things that just don't apply to diagrams. Diagramming in a programming language is just weird.
- pufuwozu 4y agoI didn't mention it, but I do write architecture diagrams which have input. data Version = Current | Future generate :: Version -> Diagram Implementation uses a few if/else expressions. Really simple. The final points of the post was that we should be able to generate architecture diagrams from other code. Parsing a service descriptor, generating them from tests, etc. You DO need a programming language.
- Veuxdo 4y agoFair point, and an interesting distinction, I think. Diagramming from code vs. diagramming with code...