djedr

10 ms·

31.
by djedr 4y ago
Location: Poland Remote: Ok Willing to relocate: Maybe Technologies: would love to learn something new, something exotic would be interesting; recent experience in TypeScript, JavaScript (React + Redux) on the frontend, Scala (Spring, Akka,
32.
by djedr 4y ago
Yes, this is probably the most sensible approach. Other options would be to ignore everything you don't recognize or ignore all nodes of the form: unrecognized tag [value] i.e. where you don't recognize the key and the valu
33.
by djedr 4y ago
> The element/attribute distinction is because HTML is a markup language, where the primary content is text and markup is used to add structure and metadata. That may have been the idea, but it falls apart in implementation. Lines
34.
by djedr 4y ago
I was talking about is making up a new markup language, which doesn't have to inherit the distinctions and behaviors of HTML. If, in this language, you wanted to have this feature in combination with what I proposed, you could simply m
35.
by djedr 4y ago
Surely you mean S-expressions. They're great, but not as a markup language. What I show here is in fact even simpler and more flexible than S-exps[0]. [0] For some details and polemic see this thread: https://news.ycombinato
36.
by djedr 4y ago
> More or less, what I want from markup is to convert a text string into a document tree: enum Element { Text(String), Node { tag: String, attributes: Map<String, String> children: Vec<Element>,
37.
by djedr 4y ago
If this standard is abstract/modular enough then it should be easy to use/adapt it for use with Jevko. A Jevko-based markup format combined with that would then be similar to XML+XDM, albeit much more minimal. This would be in lin
38.
by djedr 4y ago
Thank you for your feedback. Can you clarify? What is the "first page" that you are referring to? Can you paste a link to it along with the broken examples link? This Hacker News submission features the blog post under this URL:
39.
by djedr 4y ago
If you ever publish the project, send me a gmail at darius.j.chuck I'd love to feature it here: https://github.com/jevko/community
40.
by djedr 4y ago
Thanks! I put it here: https://github.com/jevko/community Cheerio
41.
by djedr 4y ago
> I don't think your revision of the "S-expression" grammar is in accordance with the normal use of the term; it says ()() is an S-expression, when conventionally it's considered to be two of them. If that's what
42.
by djedr 4y ago
I suppose there is a bit of confusion. User23> For example, a Common Lisp hosted Jevko parser implementation might choose to represent Jevko text objects as symbols. This is right. gnulinux> These are not strings. These are symbols. T
43.
by djedr 4y ago
This analysis would be valid if we were talking about lambda calculus or a Lisp with square brackets. Jevko isn't that. It's not a programming language[0]. It's just syntax, with even less semantics than JSON and even simpler
44.
by djedr 4y ago
Would you mind if I feature this somewhere on a Jevko-related page with attribution to your GitHub user account (or whatever you want)?
45.
by djedr 4y ago
Responding to some points I left off here https://news.ycombinator.com/item?id=33336789 I guess the main one is this: > If your audience is people like me, I think it would probably be worthwhile for you to spend some ti
46.
by djedr 4y ago
> Thank you for your thought-provoking explorations, for the unwarranted flattery, and for taking the time to respond! Clearly we share an interest in flexible simplicity. Indeed we do! :) > As for S-expressions, I agree that what I w
47.
by djedr 4y ago
Yes, it has the same spirit of S-expressions and shares the lovely square brackets with Rebol. The major difference is that Jevko is whitespace-agnostic: it has no notion of elements separated with whitespace. Generally it's a simpler,
48.
by djedr 4y ago
Awesome, very happy to hear this! For a simple higher-level format, have look at Easy Jevko: * https://github.com/jevko/easyjevko.lua – implementation in Lua * https://github.com/jevko/easyjevko.js
49.
by djedr 4y ago
By all means! If you run into any trouble let me know. Some tips and useful links are here: https://lobste.rs/s/xm6mm4/jevko_minimal_general_purpose_syn... Thanks for the interest! :)
50.
by djedr 4y ago
Yes, S-expressions come in many flavors, some more minimal than others, some binary. They are all truly wonderful. The most wonderful to me are the simplest ones, and Jevko grows out of the same spirit as them. However, it does not attempt
51.
by djedr 4y ago
Plain Jevko is a notch below JSON/XML/S-expr -- it's not really a format, but a syntax that can be leveraged to build a format. This is where the rules for whitespace would be specified. These can then be taken advantage of b
52.
by djedr 4y ago
This is a valid concern, but on a higher-level. Jevko leaves whitespace handling not to clients, but to formats built on Jevko which would be the thing the clients typically use (rather than plain Jevko). Such formats of course should be cl
53.
by djedr 4y ago
I love your comment. Thanks for taking the time to look so deeply into this! I'll respond to the main points and then expand on the details later. I'm not sure what the authoritative source on S-expressions is (or even if there is
54.
by djedr 4y ago
Nice find! Jevko is the evolved version of that (I'm the author).
55.
by djedr 4y ago
Author here, thanks for posting this. If anybody has any technical questions or comments, ask away!
56.
by djedr 4y ago
Thanks for taking the time to look at this. ;) What you are getting is the plain Jevko parse tree. The examples explicitly talk about a format built on top of that. See this answer: https://news.ycombinator.com/item?id=33334
57.
by djedr 4y ago
> 1. It relies on later stages to do things like convert to native values or remove whitespace. As such an intermediary can't really "understand" the document very well. E.g., if you are using this syntax to express key&#x
58.
by djedr 4y ago
One comparison is here: https://jevko.github.io/compactness.html To see how it's syntactically simpler than S-exps note that the grammar of Jevko can be condensed into one short line of ABNF: Jevko = *("[&quot
59.
by djedr 4y ago
Certainly! The advantage of a Jevko-based format over the above is that it has the simplicity and elegance parameters (IMO) cranked up to maximum! ;) Now, for the tool support...
60.
by djedr 4y ago
Nice find and you understand correctly! ;) This is one way. I've experimented with many others. Some semi-documented here: https://github.com/jevko/markup-experiments Some ways don't need additional level of

More ›