Seems like it could have been cool, but likely will not seriously try it because of these limits.
Seems like it could have been cool, but likely will not seriously try it because of these limits.
Shame. Mermaid works almost okay and often looks like garbage. I wish there was an open source effort somewhere to do better, or even a paid locally runnable tool that has no service connections.
That said, over time a diagram's value will diminish regardless if you have auto-layout or not, since the codebase will always outpace documentation.
edit: I've updated the docs to make this clear
But when the project is trying to compare itself to others, it's only fair to compare based on what's true of the project currently vs what's aspirational. I would guess that for many potential users, the temporary limitations trump most of the stuff in the comparison portion of the FAQ, or the "current shortcomings" section.
And the "Getting Started" section could also say "create an account and familiarize yourself with the existing terrastruct product" or whatever.
If they made the core open and allowed users to use this language independently of their online service, there's still a ton of value they could have added with premium services on top of this. For writing the docs, sharing with teams, comments / versioning, etc. Visual figma type features essentially. A team bought into the specification would very likely pay for this.
But it's hard to imagine it taking off being completely locked into their service. Ah well, a fine idea and looked pretty well executed.
EDIT: maybe that's on their roadmap "When the language is more stable, we intend to open source D2. This will happen sometime in 2022.". Ok, back on board
> INFO: It's currently in alpha. During this time, it's only housed on Terrastruct, which provides the most well-supported interface (IDE) for it. Once we have a stable v1, we'll release and continue development of it in open source and make local options available.
I think the author of this page started with the assumption that of _course_ given their business and product, a 'language' for diagrams is only giving users access to something that maps on to whatever internal representation their tool already uses, and allows technically inclined users to work with text and fewer clicks. To them, the assumption seems to have been that readers will already be users of their product, and the assumption that the 'language' is built into their tool _and nowhere else_ is so far in the background that it's only somewhat obliquely addressed as the last question in a FAQ.
> When it's more stable, we will be open-sourcing the language.
If thats the case, that only the language will be open-sourced, not the visualization, then I'm not entirely sure what that really gets you, beyond perhaps alternative editors?
But its the layout algorithms that are actually notable.
I mean, I agree, that "new" is marketing speak for "alpha/beta", but -to me- there is a difference between a "language/tool" and a "Single-Vendor-WebService". Or is my understanding of the semantics of the English language outdated?
Even patents aside, why wouldn't this D2 thing qualify as:
COMPUTING
a piece of software that carries out a particular function, typically creating
or modifying another program.
(source: google "define tool")While it isn't creating or modifying a program, I'd consider "parsing text in a specific syntax to create a diagram" more like a compiler than a site that just provides information or crud sites with some forms. I'm not entirely certain how where it runs affects it's tool status, but it certainly is a consideration to be made while evaluating it for any particular use case.
(also from define tool:
a thing used in an occupation or pursuit.
and depending on where you stand on the "thingness" of software may also apply here, but that feels diversionary)I can think of quite a few single vendor languages - various IBM mainframe languages like JCL, K, matlab, multiple .Net and MS languages until recently, applescript, etc.
Just because HN isn't Reddit doesn't mean ads aren't thrown in with all the curated "content"
Like other said, maybe it will inspire someone to take this and make an open-source version
> if it wasn't paid.
Maybe you intended to say 'if it wasn't closed', or similar.
And there's C4 Model for Visualising Architecture [0] that has upcoming tool support, for instance Structurizr DSL [1]. It has an online editor [2] that can export to Mermaid, PlantUML and other formats. And has various open source repo's, like this Java codebase for the DSL itself [3].
[1] https://structurizr.com/help/dsl
When I want to make diagrams graphically, I use diagrams.net. when I want to make diagrams from code, I use PIC. What else do people use? PIC works pretty well, but it has its limits and it's ancient.
Is a modern implementatiom that's pretty nice.
An alternative implementation with good docs.
Gotta find a way to do an "open core" or similar.
If not, I won't use it for anything serious.