← Back to context

Comment by weslleyskah

1 day ago

It's a matter of taste, isn't it? It's like LaTeX vs. Typst. You create the environment that works best for you.

7 comments

weslleyskah

Reply
crazygringo  1 day ago

In my experience, not really. I'd love to use Typst, you have no idea -- but when most journals require you to use their LaTeX template, then my personal taste doesn't really enter into the equation.

jameshart  1 day ago

For personal workflows, yes. In your own backyard, you decide what side of the road you drive on.

But when building a product for other people to use - a messaging tool like slack or a commenting platform like GitHub code review…?

  • tikhonj  1 day ago

    GitHub has at least some support for org-mode rendering. Which is a good reminder that a lot of this stuff really doesn't have to be a stark either-or choice—a lot of standardization isn't inevitable or natural or necessary, but just a choice we happen to make, often for systemic reasons that aren't inherently justified (legibility/etc).

  • fipar  1 day ago

    What if you're building a product for other people like you to use?

    I think this is very common, like people building tools for trackers vs Ableton/Live/etc style DAWs, or those writing software only targeting the OS they use? Not every product is built with the goal of worldwide adoption.

    Back to the specific case being discussed, I can easily export usable markdown from org. The people I share it with have never noticed it wasn't markdown since the start, so why wouldn't I continue to use org even when interacting with people who don't? It makes my private side of the exchange better for me, and it doesn't affect the public side negatively for others.