I like plantUML, I really do. but I think more people will be attracted by it, if they improve design and colors, so it looks modern out of box without any hacking
I was originally a proponent of it, but I find these days i prefer Mermaid. It doesnt hurt that there are more Markdown editors/viewers integrated with Mermaid than PlantUML.
Until mermaid comes up with the vast list of diagrams one can create in Plant UML, I don't see it as operating in the same weight class. E.g., wireframes, basic Gantts, AWS diagrams, component diagrams with graphviz (thought I confess I hate this dependency), archimate diagrams if you're really hardcore.
for UML it seems mermaid is indeed good enough, I used mermaid but never used it for OOD UML, after a quick read it looks very simple and straightforward for UML comparing to plantuml, especially you can embed mermaid right into markdown as text
You could customize a style for your diagrams and then include it via a one-liner in every diagram you create. This also allows for branding of diagrams.
Personally, I'm a huge fan of the simplicity and whenever I present such a diagram to teams or execs, I break the ice by warning them it'll be "ugly" or "let's go back to 1995 for a sec" :) More importantly, the focus remains strictly on the content because of the basic design.
PlantUML has morphed into a two part tool.
Its original purpose was to visualise various forms of UML diagrams.
More recently it has utilised its underlying graphviz to create a more general 'graphviz on steroids' diagramming tool (referred to as the PlantUML standard library).
The original UML diagrams can be styled to look modern, but normally are shown in a default slightly old-fashioned and uninspiring visual style. Such a shame if that's your impression.
As mdaniel posted, just a refresh of the colour scheme can modernise the look of UML diagrams
PlantUML is simply awesome. There is no other langauge that supports so many diagramming features. I use it for more then half decade now on all projects. You can create interface mocks, timelines, mindmaps, gant charts, uml diagrams, graphs, OOP diagrams, whatever really, if it was invented, it is in plantUML for sure, or will be. Also, devs are VERY responsive, if you have a good idea, they will for sure implement it.
The only thing that is going on my nerves sometimes is that you can't preciselly say position of elements and being happy with how concrete, albeit more complex diagram draws, is somewhat trial and error (you change direction, change arrow length here and there, change element order etc) but eventually you will make it likeable.
Other thing is that syntax differs a lot between diagrams and I always need to check out manual, no matter how much I use it, it just doesn't stick for me. Thankfully, this is all very easy to do.
For those on Windows, I created chocolatey package [1] that installs all dependencies along with PDF manual and you can have it on your CI or local server as simply as `cinst plantuml`. There is also vscode and mkdocs plugins that are great so you can just insert plantuml diagram strait into markdown between other documentation (alternative is to prerender images which I also did in the past, and is very fast as plantuml regenerates only changed stuff). If you need mkdocs bundled with all this and other nice stuff, check out mm-docs [2].
I must honestly say that this is one of the best FOSS projects I encountered and that it definitelly needs more recognition and support.
Not being flippant, that's the difference. graphviz/dot is general-purpose and can be configured to produce UML-like diagrams, but that's labor intensive.
PlantUML takes text and produces UML diagrams from it. It's configurable... as long as you want UML. If you want something else, reach for graphviz.
In my own work, I use dot/graphviz for diagramming abstract syntax trees, while I've used PlantUML a couple times to diagram the layout of structs and to map the high-level relationships between modules in large software projects.
org-mode does a very nice job of integrating both of those formats into documents, fyi.
Putting the emphasis on UML is a bit misleading actually (even though it is literally in the name of the tool). I use it for basically any kind of ad hoc diagramming. Essentially, an equivalent of Markdown for PowerPoint charts if that makes sense. A few quick lines in text that look mostly like what they come out as in the diagram and you have a very nice representation of a workflow etc.
Sort of tangential.
While there are lots of tools to convert code into diagram, I wonder if there are tools to convert diagram into code with defined rules.
Am asking because there are lots of programming illiterate colleagues. By encoding the business rules into drawing rules, one could potentially delegate the business logic writing part to non-coding staff
There's a whole discipline around converting diagrams to code, called Model Driven Engineering. The idea is that you capture business entities and rules in various well defined diagrams, which then can be converted to code through code generation tools, i.e. can be turned into programs.
This was mainly promoted and developed by the creators of UML and has strong ties to it. That was UML's vision after all, a visual diagram language that unambiguously captures the essense of a program.
The Eclipse Modeling Framework is a framework that implements this approach.
I think MDE was up and coming around the end of the 2000s. As far as I know it didn't really go anywhere.
You could perhaps do something with the dot language and gvpr[1]. It's not super easy to use though, but I've used it to generate a Javascript representation of a graph before.
https://real-world-plantuml.com/
which appears to be harvested from GitHub searches: https://github.com/yfuruyama/real-world-plantuml/blob/master...