Nope. Once you see same (sub)set of classes repeated, you would instead define .alert and .alert-danger using Tailwind's @apply directive, and you now have a single place to change how your `alert alert-danger` looks :)
Because you'll have 29 different margins, 67 different left paddings, etc all over the place. Tailwind allows you to create a consistent design system. CSS was supposed to be "write one class, use it everywhere instead of inlining". Usually it ends up with nobody reusing that class and everyone creating their on in the same codebase. There's an article I don't have a link handy, which explained how ridiculously many classes were used by GitHub/Lab, Airbnb, etc. Now even GitHub have their own utility based CSS system and others are following along, including Bootstrap with their CSS utility classes.
> Because you'll have 29 different margins, 67 different left paddings, etc all over the place.
That's not really the case since SCSS became a thing. If SCSS doesn't help you, Tailwind won't, you can ignore their classes just as you could ignore preset constants.
Honestly, to me it seems like people are just starting "fresh" with a benefit of some experience, and ascribing the benefits of experience to the tool.
I've used SASS for years, and yet switching to tailwind felt reaaally nice. have you tried it for yourself, or are you just assuming that you understand the practical differences?
Can you elaborate? I can't agree with you. Tailwind is meant to provide a consistent design system, of which CSS size should never get out of hand (which is the case then using regular CSS). Whenever I use Tailwind, I end up adding maybe 20-30 lines of CSS and I never have to open a CSS (or other sass/less/whatever) ever again. Have you tried Tailwind or you're just assuming what you're saying?
Glad you like it :)! Thanks for sharing the link. One of the reasons I created Stackdraft was the thought "why cloud architecture diagrams can't look good as well?". It's like we're constrained to crude tools, but the technology has gone so far already :)
I went through a bunch of diagraming options. draw.io is 2D diagraming only. There's also Lucidchart and few others. One other option seems to provide more than flat diagramming, but it's fixed to isometric projection (so, it is flat in the end).
I was also inspired by these diagrams from Amazon [1]. In Stackdraft, you press V key and toggle between 2D and 3D. You have full control over the point of view :). You can also create an animated presentation, like this one [2] - that one was just to show off a few AWS 3D models, so it's quite simplistic, but you get the idea :).
Thank you! I really hope to improve the graphics further with postprocessing, more custom 3D models, etc.
Yes, 'multi-provider' was one of the reasons I built it :). You can naturally mix the icon sets as you wish, if you have cross cloud infrastructure, which is becoming more popular these days for HA purposes.
Thank you for your kind words. Yes - Stackdraft was partially inspired by Cloudcrafts sole focus on AWS. I don't blame Tomas though, only on surface supporting multiple providers seems like an easy task - I'm sure it's not. At this early stage of Stackdraft I focused on diagramming and presenting and naturally plan to add more advanced features.
To answer your second statement - I think it's a matter of doing one thing only and one thing well. While I do plan to support sub-resource level items like containers, I doubt the tool will reach as far as UML/software modeling, at least not in the foreseeable future. Do note I received lots of feedback from a LucidCharts users, who draws architecture diagrams, and in general there's a few good parts of LucidCharts I'd like to take example from.
Regardless, I will always welcome any ideas for Stackdraft, so thank you very much for your feedback :)! I appreciate you took time to leave this comment.
Nope. Once you see same (sub)set of classes repeated, you would instead define .alert and .alert-danger using Tailwind's @apply directive, and you now have a single place to change how your `alert alert-danger` looks :)