Hacker Newsnew | past | comments | ask | show | jobs | submit | more alixanderwang's commentslogin

Looks great! Giving it a try, posted a $220 bounty: https://github.com/terrastruct/d2/issues/921


Thank you so much Alex, welcome to Algora!! love the chess diagram in the Terrastruct D2 README ;) first Golang open source bounty, let's go!


PR merged! the bounty was rewarded to a new contributor <3


we embed some CSS in SVG outputs to make animated diagrams for our text-to-diagram language: https://github.com/terrastruct/d2/releases/tag/v0.3.0


Right. It's okay to leave written documentation on SaaS (e.g. Notion), because the text is the artifact. If they're shutting down, or I don't like them anymore, I just move the text. But if Ilograph goes down, all I have is useless YAML.

Our team went through this thought process when we decided to open source our text-to-diagram language, users need to be able to reproduce their docs even if we shut down (https://github.com/terrastruct/d2).


> But if Ilograph goes down, all I have is useless YAML.

Depends. If you're using Ilograph Desktop [0], an outage won't affect you. And both with Ilograph Desktop and paid versions of the web app, you can export your diagrams to standalone HTML files. These artifacts will live forever.

[0] https://www.ilograph.com/desktop/index.html


I moved from Notion because of too many bugs, outage is just one of many scenarios where you'd want to bail, and not a primary one because it's not like a diagram service is in the customer path.

The HTML files are also not enough for me. It's like a bricked artifact. I can't modify my diagrams anymore. Like if I adopted a company's programming language and they assured me my assembly code artifacts will live forever.



Yup!


We offer a drag-and-drop UX, where edits made are written back to the text: https://terrastruct.com (it's not Mermaid, but a similar text-to-diagram language)


You can compare at https://text-to-diagram.com (disclaimer: i made it, but it's all open-source, the maintainers of mermaid have contributed to it).


we made the change to Linear, but ultimately, made the change back to GitHub Issues. Their marketing and devrel is good -- it convinced me without actually considering its merits, that surely everyone must be buying into it for a reason. Ultimately, I did not find the overhead of another tool to be worth it.

(we also open-sourced the script we wrote to automate the migration: https://github.com/terrastruct/byelinear)


you could just resubmit, and leave a comment here pointing there. i'll look for it in the new section to upvote!


Hah, typically this line goes, "once Google/big tech does this, you're in trouble".

The reality is like that xkcd meme of some random dev in midwest US supporting critical infra with their open source efforts. GitHub natively runs Mermaid which runs Dagre, which has been unmaintained for many years now because the one guy working on it left and nobody's touched it since, despite many holes in the algorithm.

ELK has been continuously worked on by a research team for over a decade, and we can produce better looking layouts just by specializing for different cases. The space is so large. I hope that a great FOSS open-source layout engine comes along, I'll gladly integrate it into D2, but I don't fear it'll make TALA moot.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: