@swanson personally I prefer #Markdown but that's trivial to convert to #HTML.
Personally, I just wished for #YADL to succeed as a superset of Markdown.
#YADL
@koehntopp @Moss_the_TeXie ich selbst würde ja eher daran arbeiten wollen, #YADL weiterzuentwickeln aber leider bezahlt das nicht mein überleben...
@arnan @the_grue @mrmasterkeyboard @publicvoit re: #tables and the like, I do propose a successor standard / superset of #Markdown I named #YADL:
http://github.com/greyhat-academy/YADL
Because #TSV is the superior format for #spreadsheets…
@DrPen I purposefully choose to use @libreoffice / #LibreOffice equivalents or Straight-up name the file type I want (because If I say #TextDocument I can get anything;from a #txt file to #YADL to #Markdown, #LaTeX, #HTML, #OpenDocument & #PDF depending on who I ask and how they feel like)...
@kubikpixel .conf file / #Ansible / #YADL!
https://github.com/greyhat-academy/yadl
@ClickyMcTicker @pearl @geerlingguy
From scratch should (and would) be possible if said #configuration isn't just proprietary bs but actually following a documented syntax akin to any proper #configuration.
- I assume this is NOT the case cuz otherwise you'd not offer said job.
Not to mention #vendors prefer #siloing amd #Enshittifying products, so having #InterchangeableFormats goes against their primary #commercial interests.
- We can see this peak with #Cisco & #Microsoft pushing both proprietary #SingleVendor & #SingleProvider standards, #patenting the implementation (i.e. #VRRP) and sueing everyone who wants to implement them (i.e. #CARP had to do a shitton of redundant work!) whilst also refusing to follow #Standards (i.e. #Posix new line ) & #Conventions (I've seen literal CISCO <=> #IETF dictionaries!)...
Sadly it's more #unrealistic to see such standardization to happen than #YAML being replaced by #YADL...
@sodiboo @luna @ari @puppygirlhornypost2 You're correct.
Personally, I do want to get a unified and better alternative going.
I call it #YADL:
https://github.com/greyhat-academy/YADL
@lazarus @santiago TBH, I thought of merely a sort-of-metapackage (kinda like #LibreOffice is, as it's components are indicidually installable)...
- For the most part, it should just provide a few basic scripts to i.e. use #YADL and build a pipeline to whatever output formats are desired...
I.e. you can, just edit your documents/presentations/... in like #neovim or #ne or whatever ither #editor you like and you'd then just tell it to spit out i.e. PDFs, HTML (in a .tar.bz2 if there's more than a single HTML file) or whatever format...
- Not like a #Bloatware akin to #MicrosoftOffice which uses #OOXML as a means to prevent #OpenSource from succeeding.
@LunaDragofelis @dysfun @left_adjoint welcome to the club... points at a huge-ass libraries of old unfinished projects
May I fancy you with a box of #YADL?
@k0stk @devopscats I know but like every dev that I know uses #Markdown for #documentation - at the very least #GitHub-Style Markdown, cuz #AaronSwartz's death prevented someone from coherently managing it and preventing fracture into in part incompatible standards.
- Even if that means my own draft, #YADL, would be obsoleted...https://github.com/greyhat-academy/yadl
@h amd I thought #YADL seemed weird...
https://github.com/greyhat-academy/yadl
@wakame @mos_8502 @RetroViator Consider #YADL instead?
https://github.com/greyhat-academy/yadl
@em
1. WTF? Why would I want animations in markdown beyond calling.up a GIF/APNG with AltText?
2. Thx, I'll stick with #YADL...
https://github.com/greyhat-academy/yadl
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst