Apparently for the same things as with XML/JSON/TOML.
> I followed the link and read the page, but I’m still not sure what the point is!
According to the website:
> It has no data types, no semantics, no underlying model of cons cells or anything similar. It’s as close to pure generic syntax as it gets.
> So at the lowest level Jevko is a minimal formal specification for flexible trees of text.
For its simplicity it seems quite powerful to me. I don't see it replacing JSON/markdown or even TOML. But is seems trivial to implement on very low-level, older, less bloated, or less powerful systems.
Every time I've written or otherwise dealt with JSON/XML/etc. I wished I was dealing with something simpler, so I created it. If I had Jevko as a full-fledged alternative to JSON or XML, supported by tools, etc., I'd pick Jevko in a heartbeat. I like minimalism. Some people like it too, so perhaps Jevko can serve them well. There are many good reasons.
> But is seems trivial to implement on very low-level, older, less bloated, or less powerful systems.
Indeed, this is THE feature and a realistic application. I hope!
For a naive unrealistic vision that I sketched out some time ago see:
Say you build your own language, but don't want to write a parser for it (people who write tons of prog langs know that syntax is the most boring part (for some, I'm sure some people love it)) so you can borrow this, it gives you a syntax tree, and you just continue from there.
saurik|3 years ago
eterps|3 years ago
Apparently for the same things as with XML/JSON/TOML.
> I followed the link and read the page, but I’m still not sure what the point is!
According to the website:
> It has no data types, no semantics, no underlying model of cons cells or anything similar. It’s as close to pure generic syntax as it gets.
> So at the lowest level Jevko is a minimal formal specification for flexible trees of text.
For its simplicity it seems quite powerful to me. I don't see it replacing JSON/markdown or even TOML. But is seems trivial to implement on very low-level, older, less bloated, or less powerful systems.
djedr|3 years ago
Every time I've written or otherwise dealt with JSON/XML/etc. I wished I was dealing with something simpler, so I created it. If I had Jevko as a full-fledged alternative to JSON or XML, supported by tools, etc., I'd pick Jevko in a heartbeat. I like minimalism. Some people like it too, so perhaps Jevko can serve them well. There are many good reasons.
> But is seems trivial to implement on very low-level, older, less bloated, or less powerful systems.
Indeed, this is THE feature and a realistic application. I hope!
For a naive unrealistic vision that I sketched out some time ago see:
https://github.com/jevko/writing/blob/main/2022-01-13-vision...
gnulinux|3 years ago
Say you build your own language, but don't want to write a parser for it (people who write tons of prog langs know that syntax is the most boring part (for some, I'm sure some people love it)) so you can borrow this, it gives you a syntax tree, and you just continue from there.