5 ms·
This was very confusing, until I found the 'about' button. I guess I'm leading a charmed life, because I can not recognise UML on sight? (I thought at first t
by eru 3y ago
This was very confusing, until I found the 'about' button.
I guess I'm leading a charmed life, because I can not recognise UML on sight? (I thought at first this was describing a grammar of fake pirate language or something.)
- IshKebab 3y agoThe way to recognise UML is by the wide variety of arrow styles that nobody can remember. I'm 90% sure that's the main reason it didn't catch on. You have to learn UML because of the stupid arrows. Compare it to something like this which acknowledges the fact that nobody is going to casually memorise 10 different styles of arrow just to read occasional UML diagrams: https://buck2.build/docs/concepts/concept_map/ https://buck2.build/docs/concepts/concept_map/ Much better.
- eru 3y agoDifferent arrows are useful to express different relationships. But perhaps you should just put a legend next to each diagram, or use words to annotate your arrows?
- Etherlord87 3y agoNo one forces you to use all possible arrows, you can learn just one, and use that. When reading a diagram, ideally you would read it by looking at the generated diagram, not text, as that's the entire point, but even when reading the raw text, it's apparent where the arrows are, based on "less than" and "greater than" characters, no?
- IshKebab 3y ago> No one forces you to use all possible arrows, you can learn just one, and use that. Not if you want to read other people's UML diagrams, which is rather the point.
- dathinab 3y agoit's not really UML, at least not standard conform I think through that's kinda true for a ton of tooling using the word "UML" and in many case you also somewhat want something which is less precise (and verbose) then UML theoretically is
- vidarh 3y ago> and in many case you also somewhat want something which is less precise (and verbose) then UML theoretically is This tends to be "the" big problem with UML (and similar): Very few people care about, or have a reason to, stick 100% to UML. They want to "speak diagrams", and just like written or spoken language, our syntax and semantics is context dependent and dependent on the dialect and speech patterns and understanding of those we speak to. So the "UML" people learn is often a dialect of sorts closer or further from the formal grammar, and a lot of tools fail to take that into account and try to force you into conformity. We accept that for programming languages, yet we still use pseudo-code in all kinds of contexts, but diagrams are one step up - one of the things we "escape to" when writing formal code is too complex or we want to explain things to people who don't know or care about the details. There's a significant strain there between those conflicting goals of diagrams as communication, and the evolution of CASE tools that wants diagrams to be formal, that is much closer to how we deal with natural languages (people arguing over formal use vs. slang) than with programming languages, and it's fascinating.
- layer8 3y agoIt’s a pity, because one benefit of UML would be that everyone speaks the same language. Before UML, there were many different modeling notations [0], and the goal with UML was to create a single interoperable unified language. This was successful insofar as it displaced the previous object modeling languages. However, it would be nice to have that benefit of a modeling lingua franca not only in modeling tools, but for casual usage as well. [0] https://en.wikipedia.org/wiki/Object-modeling_language https://en.wikipedia.org/wiki/Object-modeling_language
- tannhaeuser 3y ago