120 karma · joined August 28, 2013
Sorry, I didn't explain it clearly enough. In our project, it's not only about components/classes. We have architectural documentation which describes a high-level architecture of the whole project: services, deployments, interfaces, devices, middlewares, files, virtualized environments, databases, and their relations across different domains and software clusters so it's not possible to generate diagrams for such things.
>> there is no way to control the position and layout of elements on diagrams
> This is a feature: there is no way to waste time fiddling with diagram layout
Yep, I understand but... As I just said, when a project is big, and it has a big architectural document that describes different software clusters, their relations, deployments, and so on, then it's totally unacceptable when all teams on each sprint/release are getting such an important document with brand-new diagrams because of "that feature" since some new architectural piece was added to the diagrams.
> you can tell that to the cheapskates who made you switch from Enterprise Architect to PlantUML.
After all, we didn't make a full switch to puml. We are still using both. There were some problems with the Enterprise Architect so lead architects decided to check how puml will play in that role but they quickly rejected the idea after the evaluation of pros/cons.
We realized it's just impossible to handle in a reasonable way hundreds of diagrams from different teams who have to show/maintain cross-component dependencies independently. Puml isn't designed for that at all. Another limitation of puml we faced: there is no way to control the position and layout of elements on diagrams. With complex diagrams, you'll quickly get a total mess and if you are lucky to manage how to get finalized nice diagram then any tiny element added later will ruin the whole diagram since puml decided to reposition everything.
Just wanted to share our experience. Yep, we are still using it for small generic diagrams to quickly depict some concepts as well as for sequence diagrams but never for documenting complicated component/class relations.
It's slow as a hell. I don't understand why changing exposure on my 16 core i9 macbook takes up to 2-3 seconds for 24 mpix image. Same with zoom: 24 mpix image takes 3-4 seconds to zoom in/out! Really? How this software is written that simple actions are taking so much time? Enabling OpenCL helps, but not so much: changing exposure takes up to second (yes, 3-4 times faster) and zoom still 3-4. Meanwhile devs are spending time on css driven UI...
But UI is also unusable: it's very compact and many elements on a retina display are very close to each other, so I'm constantly miss-clicking them. Slider knobs are ridiculously small and hard to grab and drag. Numbers on controls can't be entered manually, so if you need some exact value you should spend seconds on dragging sliders until you get what you want.
Any other photo software are way ahead of this editor in terms of UI and performance, so I don't understand why this one gets so much attention.
1. I want to engrave international symbols by myself. Will they have a backlight like original symbols?
2. Many people around the web are very pleased with their Cherry MX based keyboards. This is understandable when they are switching from cheap keyboards with same keystroke length. But what about people that have switched from laptop or Apple keyboards with shorter keystrokes? I found for myself that twice shorter keystroke is also twice comfortable (much less movements for fingers). Does it make a sense to try again a keyboard with long keystrokes, but with good mechanics like the CODE? Has anybody tried to use CherryMX keyboard after using laptop or any other keyboard with short keystrokes? Could you share your experience?