> From: "Brian Goetz"
> To: "Ethan McCue" , "core-libs-dev"
>
> Sent: Tuesday, February 28, 2023 8:48:00 PM
> Subject: Re: JEP-198 - Lets start talking about JSON
> As you can probably imagine, I've been thinking about these topics for quit
As you can probably imagine, I've been thinking about these topics for
quite a while, ever since we started working on records and pattern
matching. It sounds like a lot of your thoughts have followed a similar
arc to ours.
I'll share with you some of our thoughts, but I can't be engaging in
Link to the proxy which I forgot to include
https://gist.github.com/bowbahdoe/eb29d172351162408eab5e4ee9d84fec
On Tue, Feb 28, 2023 at 12:16 PM Ethan McCue wrote:
> As an update to my character arc, I documented and wrote up an explanation
> for the prototype library I was working on.[1]
>
> An
As an update to my character arc, I documented and wrote up an explanation
for the prototype library I was working on.[1]
And I've gotten a good deal of feedback on reddit[2] and in private.
I think its relevant to the conversation here in the sense of
- There are more of rzwitserloot's objectio
Sidenote about "Project Galahad" - I know Graal uses json for a few things
including a reflection-config.json. Food for thought.
> the java.util.log experiment shows that trying to ‘core-librarize’ needs
that the community at large already fulfills with third party deps isn’t a
good move,
I, pers
> are pure JSON parsers really the go-to for most people?
Depends on what you mean by JSON parsers and it depends on what you mean by
people.
To the best of my knowledge, both python and Javascript do not include
streaming, databinding, or path navigation capabilities in their json
parsers.
On
> The 95%+ use case for working with JSON for your average java coder is
best done with data binding.
To be brave yet controversial: I'm not sure this is neccesarily true.
I will elaborate and respond to the other points after a hot cocoa, but the
last point is part of why I think that tree-crawl
I'll have to read the whole thing, but are pure JSON parsers really the
go-to for most people? I'm a big advocate of providing also something
similar to XPath/XQuery and that's IMHO JSONiq (90% XQuery). I might be
biased, of course, as I'm working on Brackit[1] in my spare time (which is
also a que
A recent Advent-of-Code puzzle also made me double check the support of
JSON in the java core libs and it is indeed a curious situation that the
java core libs don’t cater to it particularly well.
However, I’m not seeing an easy way forward to try to close this hole in
the core library offerings.
I'm writing this to drive some forward motion and to nerd-snipe those who
know better than I do into putting their thoughts into words.
There are three ways to process JSON[1]
- Streaming (Push or Pull)
- Traversing a Tree (Realized or Lazy)
- Declarative Databind (N ways)
Of these, JEP-198 expli
10 matches
Mail list logo
