Resilient technologies aren’t retro—they’re ROOT: Robust, Open, Ongoing, Time-tested.

[lukascbossert@mastodon.social]

Resilient technologies aren’t retro—they’re ROOT: Robust, Open, Ongoing, Time-tested. In RDM, text-first + small, composable tools beat opaque stacks. Emacs/Org(-babel) for literate workflows & provenance; Makefiles declare rebuilds; CLI atoms—curl, sed, awk, grep, diff, tar, rsync, cron, SQLite—keep steps inspectable, portable, rebuildable. DOI: https://doi.org/10.5281/zenodo.17157588 — Feedback welcome!

#ROOT #ResilientTech #Emacs
#OrgMode #RDM #NFDI
#FAIR
#Reproducibility
#literateprogramming
#BoostOK

[lukascbossert@mastodon.social]

Main poster maps long-lived tools to the research-data life cycle (Plan → Produce → Analyze → Archive → Access → Re-use). Emacs/Org for provenance, Make for rebuilds, curl/sed/grep/diff for intake & checks, awk for tables, cron for timing, tar/rsync for packaging/sync, plus SQLite/LaTeX/find. Pipelines you can re-run years later. Feedback welcome! #ROOT #ResilientTech #RDM #NFDI #Emacs #orgmode #literateprogramming #OpenScience #tools #researchdatamanagement
https://doi.org/10.5281/zenodo.17157588

[lukascbossert@mastodon.social]

The meta poster frames the concept: clarity + openness → resilience. It traces the lineage from Knuth’s Literate Programming to Org-mode and NFDI practice, and introduces the ROOT badge as a compact signal for robust, open, ongoing, time-tested tools. It also spotlights resilient stalwarts often hiding in plain sight—find, LaTeX, perl, rsync, SQLite—showing why they remain reliable RDM building blocks.
#ResilientTech #LiterateProgramming #OrgMode #RDM #NFDI #FAIR https://doi.org/10.5281/zenodo.17157588

[lukascbossert@mastodon.social]

The source poster shows the guts: Emacs/Org-babel + LaTeX; noweb tangling; minted listings; multi-column layout. The complete source code! The poster is both publication and working research object. Example flow: query Zenodo via curl, download dataset, compute checksum, compare, then proceed with scripted transforms—transparent steps you can re-run. Everything is fully specified, so you can regenerate all of it from source. #Emacs #OrgBabel #TeXLaTeX #orgmode
https://doi.org/10.5281/zenodo.17157588

[raphaellek@social.sciences.re]

@lukascbossert poke @mc2

[mc2@social.sciences.re]

@raphaellek @lukascbossert thanks for the link but I probably don't get the message. I know emacs can the things I do with vim (mixing sources to get unique input) but I really hated both the emacs and latex experience.

[lukascbossert@mastodon.social]

@mc2 @raphaellek I don’t want to say that you should use exclusivly #Emacs. Personally I am also fine with #Vim, it’s just not my tool. and I wanted to stress the #orgmode/#orgbabel use with source-blocks and tangling/weave.

[mc2@social.sciences.re]

@lukascbossert @raphaellek I cloned the repo. and finally think that Raph. just pointed out the link because our practices are really close even if we chose different tools.

I'm still waiting for an official org-mode grammar so we could have an editor independant implementation. bzg resigned as maintainer so I have no fresh news about it.

[sreycoyrehourcq@social.sciences.re]

@mc2 @lukascbossert @raphaellek i think we're are very close of official with tecosaur org.jl https://code.tecosaur.net/ work folowing https://orgmode.org/worg/org-syntax.html

[mattiabunel@framapiaf.org]

@SReyCoyrehourcq @mc2 @lukascbossert @raphaellek There is also the work of @publicvoit on orgdown (https://karl-voit.at/2021/11/27/orgdown/)

[publicvoit@graz.social]

@mattiabunel @SReyCoyrehourcq @mc2 @lukascbossert @raphaellek Thanks for mentioning #orgdown. 🙇

However, the org community still lacks a formal definition of the (whole) syntax.

From orgdown perspective, #od1 specification would be a promising low hanging fruit but as long as the #orgmode community does not embrace the "syntax separate from implementation" idea I tried to coin, this isn't going to happen, I'm afraid.

Maybe from outside of the #Emacs/org community because orgdown as a syntax has many advantages IMO: https://karl-voit.at/2025/08/17/Markdown-disaster/

[oantolin@mathstodon.xyz]

@publicvoit I think the name might be holding the idea back? I don't feel down about Org nor do I want to take Org down. It seems negative to me. Markdown has "down" in its name because of a pun: it's in opposition to markup. Without that context I don't see why you'd want "down" in the name. I think "Orgmark" would have been clearer, or "OrgML" (for markup language), which also had the advantage that someone might mistake it for machine learning and give you money.

[publicvoit@graz.social]

@oantolin If that would actually be the reason, then the #orgmode community would have changed its name but embraced the idea. Didn't happen.

I personally do find the name helpful because the main target group is not Org users but normal users, who do know what "Markdown" is and they get some idea transfer to "Orgdown" because of "down".

Nobody I've came across ever said that "Markdown" is negative because of "down". 🤷

To me, "down" symbolizes a "simpler version syntax" according to Lightweight Markup Language (LML) in contrast to complex markup languages like HTML, tex, ...

That said: as long as the org community does not even start to embrace the idea, its name choice is more than irrelevant.

I started #orgdown not as a personal project in the sense that it stays this way. I was hoping for the community to take it away from me and follow the basic idea such that OD is becoming a tool-independent and much better alternative to #Markdown as explained on https://karl-voit.at/2025/08/17/Markdown-disaster/

[aamfp@fosstodon.org]

@publicvoit
OrgMode plugin(s) in IntelliJ are not so good; Notepad ones are even worse (if any).

I do know OrgMode is better than Markdown (and the fact that I've always wanted to learn Emacs helped me), but if the technology is not supported is difficult.

(Then there's also the problem of xkcd 927: why inventing a partial language like Markdown, when there were already gazillion other things, including OrgMode?)
@oantolin

[aamfp@fosstodon.org]

@publicvoit
I agree with you: I've moved from Markdown to OrgMode after many years using the lovely QOwnNotes (and translating 90%+ of it in Italian) because of the different flavours of Markdown.
But just like Mercurial is way simpler than Git, but the world is using Git or Betamax was better than VHS, ... well, usually it's a mix of things not helping a technology.
Codeberg is great, but project README in OrgMode breaks up, so I have to forward people to the GitHub mirror;
@oantolin

[ericsfraga@fediscience.org]

@publicvoit @oantolin Your goal for OD is laudable and I agree that the issue of OD not being taken up more generally has nothing to do with the name. I think, instead, that it's due to many of us, that depend on org mode, spending the vast majority of our time (100% in my case) within Emacs and therefore the benefits are marginal at best. YMMV, of course. ;-)

#orgmode #Emacs

[publicvoit@graz.social]

@ericsfraga @oantolin Yes, the direct and initial benefits of #Orgdown are mostly for non-Emacs people: https://karl-voit.at/2021/11/27/orgdown/

However, just imagine for a minute, that all #Markdown usage is replaced with Orgdown usage. Let your thoughts wander for a moment.

This would have tremendous impact on the #Emacs people as well when it comes to working with external tools and people.

#PIM #LML #indirectprofitability #markup #publicvoit #orgmode

[aamfp@fosstodon.org]

@publicvoit
Even better: this would have tremendous impact on the normal people by Emacs people! 😉
@ericsfraga @oantolin