#jdaml — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #jdaml, aggregated by home.social.
-
Been working some more on the #document #format. Added #interactivity. Now it's possible to use #JDAML in #JS also for runtime, not just build time.
I took all the problems described in this paper https://arxiv.org/abs/2310.04368 as challenges and implemented enough #features that they could be solved.
Also added some more #syntax #sugar -- paragraph inference and [=expr] syntax for substitution, to cut down on the nested brackets. I think it's looking good already.
What do you think?
-
Been working some more on the #document #format. Added #interactivity. Now it's possible to use #JDAML in #JS also for runtime, not just build time.
I took all the problems described in this paper https://arxiv.org/abs/2310.04368 as challenges and implemented enough #features that they could be solved.
Also added some more #syntax #sugar -- paragraph inference and [=expr] syntax for substitution, to cut down on the nested brackets. I think it's looking good already.
What do you think?
-
Been working some more on the #document #format. Added #interactivity. Now it's possible to use #JDAML in #JS also for runtime, not just build time.
I took all the problems described in this paper https://arxiv.org/abs/2310.04368 as challenges and implemented enough #features that they could be solved.
Also added some more #syntax #sugar -- paragraph inference and [=expr] syntax for substitution, to cut down on the nested brackets. I think it's looking good already.
What do you think?
-
Been working some more on the #document #format. Added #interactivity. Now it's possible to use #JDAML in #JS also for runtime, not just build time.
I took all the problems described in this paper https://arxiv.org/abs/2310.04368 as challenges and implemented enough #features that they could be solved.
Also added some more #syntax #sugar -- paragraph inference and [=expr] syntax for substitution, to cut down on the nested brackets. I think it's looking good already.
What do you think?
-
Been working some more on the #document #format. Added #interactivity. Now it's possible to use #JDAML in #JS also for runtime, not just build time.
I took all the problems described in this paper https://arxiv.org/abs/2310.04368 as challenges and implemented enough #features that they could be solved.
Also added some more #syntax #sugar -- paragraph inference and [=expr] syntax for substitution, to cut down on the nested brackets. I think it's looking good already.
What do you think?
-
I think #Jevko / #JDAML is pretty perfect for rapidly exploring stuff like this and I think #Znatchke + #JS can grow to be a viable document format.
I'd love to #research this stuff further. Now all I need is #funding... Fortunately, that's easy to get, especially in this #niche. You wouldn't believe how many zeroes are on the sum of #money I've gotten over the years of working on this stuff. Hint: it's a single-digit number.
So anyway, anybody want to buy me a #coffee or something yet? :D
-
I think #Jevko / #JDAML is pretty perfect for rapidly exploring stuff like this and I think #Znatchke + #JS can grow to be a viable document format.
I'd love to #research this stuff further. Now all I need is #funding... Fortunately, that's easy to get, especially in this #niche. You wouldn't believe how many zeroes are on the sum of #money I've gotten over the years of working on this stuff. Hint: it's a single-digit number.
So anyway, anybody want to buy me a #coffee or something yet? :D
-
I think #Jevko / #JDAML is pretty perfect for rapidly exploring stuff like this and I think #Znatchke + #JS can grow to be a viable document format.
I'd love to #research this stuff further. Now all I need is #funding... Fortunately, that's easy to get, especially in this #niche. You wouldn't believe how many zeroes are on the sum of #money I've gotten over the years of working on this stuff. Hint: it's a single-digit number.
So anyway, anybody want to buy me a #coffee or something yet? :D
-
I think #Jevko / #JDAML is pretty perfect for rapidly exploring stuff like this and I think #Znatchke + #JS can grow to be a viable document format.
I'd love to #research this stuff further. Now all I need is #funding... Fortunately, that's easy to get, especially in this #niche. You wouldn't believe how many zeroes are on the sum of #money I've gotten over the years of working on this stuff. Hint: it's a single-digit number.
So anyway, anybody want to buy me a #coffee or something yet? :D
-
I think #Jevko / #JDAML is pretty perfect for rapidly exploring stuff like this and I think #Znatchke + #JS can grow to be a viable document format.
I'd love to #research this stuff further. Now all I need is #funding... Fortunately, that's easy to get, especially in this #niche. You wouldn't believe how many zeroes are on the sum of #money I've gotten over the years of working on this stuff. Hint: it's a single-digit number.
So anyway, anybody want to buy me a #coffee or something yet? :D
-
Also been #experimenting with mixing some #JavaScript into it.
TBH I'd use #JDAML over #JSX in #JS any day.
Using \ as the delimiter makes it pretty easy to integrate into the syntax of JS. Also it adds some superpowers to JS for free, such as fenced strings.
-
Also been #experimenting with mixing some #JavaScript into it.
TBH I'd use #JDAML over #JSX in #JS any day.
Using \ as the delimiter makes it pretty easy to integrate into the syntax of JS. Also it adds some superpowers to JS for free, such as fenced strings.
-
Also been #experimenting with mixing some #JavaScript into it.
TBH I'd use #JDAML over #JSX in #JS any day.
Using \ as the delimiter makes it pretty easy to integrate into the syntax of JS. Also it adds some superpowers to JS for free, such as fenced strings.
-
Also been #experimenting with mixing some #JavaScript into it.
TBH I'd use #JDAML over #JSX in #JS any day.
Using \ as the delimiter makes it pretty easy to integrate into the syntax of JS. Also it adds some superpowers to JS for free, such as fenced strings.
-
Also been #experimenting with mixing some #JavaScript into it.
TBH I'd use #JDAML over #JSX in #JS any day.
Using \ as the delimiter makes it pretty easy to integrate into the syntax of JS. Also it adds some superpowers to JS for free, such as fenced strings.
-
BTW https://jevko.github.io/ is now a mirror of https://jevko.org
In fact right now it contains the #future #refreshed version of jevko.org which hopefully does a better job at describing #Jevko.
It also features #JDAML and I put a draft specification for Jevko #extensions there:
https://jevko.github.io/extensions.html
(most importantly for #Markdown-like fenced text)
This new Jevko website should be live soon after the #2023 calendar goes into the ♻️ 🗑️ .
-
BTW https://jevko.github.io/ is now a mirror of https://jevko.org
In fact right now it contains the #future #refreshed version of jevko.org which hopefully does a better job at describing #Jevko.
It also features #JDAML and I put a draft specification for Jevko #extensions there:
https://jevko.github.io/extensions.html
(most importantly for #Markdown-like fenced text)
This new Jevko website should be live soon after the #2023 calendar goes into the ♻️ 🗑️ .
-
BTW https://jevko.github.io/ is now a mirror of https://jevko.org
In fact right now it contains the #future #refreshed version of jevko.org which hopefully does a better job at describing #Jevko.
It also features #JDAML and I put a draft specification for Jevko #extensions there:
https://jevko.github.io/extensions.html
(most importantly for #Markdown-like fenced text)
This new Jevko website should be live soon after the #2023 calendar goes into the ♻️ 🗑️ .
-
BTW https://jevko.github.io/ is now a mirror of https://jevko.org
In fact right now it contains the #future #refreshed version of jevko.org which hopefully does a better job at describing #Jevko.
It also features #JDAML and I put a draft specification for Jevko #extensions there:
https://jevko.github.io/extensions.html
(most importantly for #Markdown-like fenced text)
This new Jevko website should be live soon after the #2023 calendar goes into the ♻️ 🗑️ .
-
BTW https://jevko.github.io/ is now a mirror of https://jevko.org
In fact right now it contains the #future #refreshed version of jevko.org which hopefully does a better job at describing #Jevko.
It also features #JDAML and I put a draft specification for Jevko #extensions there:
https://jevko.github.io/extensions.html
(most importantly for #Markdown-like fenced text)
This new Jevko website should be live soon after the #2023 calendar goes into the ♻️ 🗑️ .
-
I've been working intensely on #JDAML for a few weeks now.
I put together an online #demo / #PoC which shows how it maps to and from #JSON, #XML, and #HTML
https://jevko.github.io/jdamlIt's still very much #WIP and things may break, but the basics are in place.
If anybody would like to play around with the early version, be my guest! #Feedback welcome!
-
I've been working intensely on #JDAML for a few weeks now.
I put together an online #demo / #PoC which shows how it maps to and from #JSON, #XML, and #HTML
https://jevko.github.io/jdamlIt's still very much #WIP and things may break, but the basics are in place.
If anybody would like to play around with the early version, be my guest! #Feedback welcome!
-
I've been working intensely on #JDAML for a few weeks now.
I put together an online #demo / #PoC which shows how it maps to and from #JSON, #XML, and #HTML
https://jevko.github.io/jdamlIt's still very much #WIP and things may break, but the basics are in place.
If anybody would like to play around with the early version, be my guest! #Feedback welcome!
-
I've been working intensely on #JDAML for a few weeks now.
I put together an online #demo / #PoC which shows how it maps to and from #JSON, #XML, and #HTML
https://jevko.github.io/jdamlIt's still very much #WIP and things may break, but the basics are in place.
If anybody would like to play around with the early version, be my guest! #Feedback welcome!
-
I've been working intensely on #JDAML for a few weeks now.
I put together an online #demo / #PoC which shows how it maps to and from #JSON, #XML, and #HTML
https://jevko.github.io/jdamlIt's still very much #WIP and things may break, but the basics are in place.
If anybody would like to play around with the early version, be my guest! #Feedback welcome!
-
NB here is the #YAML #document from #hell [0] encoded in #JDAML.
I'm designing #JDAML to eliminate the risk of accidental interpretation. Unless a leaf value is clearly explicitly marked in a predictable manner, it will be interpreted as a #string.
So no #norwayproblem, no #sexagesimal or other weird number literals. No #anchors, #aliases, or #tags. No accidental non-string keys, no accidental numbers.
[0] as described by Ruud van Asseldonk in this article: https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell
-
NB here is the #YAML #document from #hell [0] encoded in #JDAML.
I'm designing #JDAML to eliminate the risk of accidental interpretation. Unless a leaf value is clearly explicitly marked in a predictable manner, it will be interpreted as a #string.
So no #norwayproblem, no #sexagesimal or other weird number literals. No #anchors, #aliases, or #tags. No accidental non-string keys, no accidental numbers.
[0] as described by Ruud van Asseldonk in this article: https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell
-
NB here is the #YAML #document from #hell [0] encoded in #JDAML.
I'm designing #JDAML to eliminate the risk of accidental interpretation. Unless a leaf value is clearly explicitly marked in a predictable manner, it will be interpreted as a #string.
So no #norwayproblem, no #sexagesimal or other weird number literals. No #anchors, #aliases, or #tags. No accidental non-string keys, no accidental numbers.
[0] as described by Ruud van Asseldonk in this article: https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell
-
NB here is the #YAML #document from #hell [0] encoded in #JDAML.
I'm designing #JDAML to eliminate the risk of accidental interpretation. Unless a leaf value is clearly explicitly marked in a predictable manner, it will be interpreted as a #string.
So no #norwayproblem, no #sexagesimal or other weird number literals. No #anchors, #aliases, or #tags. No accidental non-string keys, no accidental numbers.
[0] as described by Ruud van Asseldonk in this article: https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell
-
NB here is the #YAML #document from #hell [0] encoded in #JDAML.
I'm designing #JDAML to eliminate the risk of accidental interpretation. Unless a leaf value is clearly explicitly marked in a predictable manner, it will be interpreted as a #string.
So no #norwayproblem, no #sexagesimal or other weird number literals. No #anchors, #aliases, or #tags. No accidental non-string keys, no accidental numbers.
[0] as described by Ruud van Asseldonk in this article: https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell