ijson VS ngs

> JSON’s design assumes the user can read the entire file into memory

No? The design of most JSON libraries assumes that, but there are perfectly good incremental JSON parsers out there[1–3]. It’s just that people don’t seem to have figured out a good API for not-completely-incremental parsing (please prove me wrong here!), but this applies equally to any structured data format as soon as you want to pull out pieces of data that are nested more than one level down.

The lack of length prefixes in JSON does indeed make a solid parser somewhat more difficult, but you get the ability to author and validate it manually instead. All in all a draw and not because of the incremental parsing thing.

(Tabular or otherwise homogeneous data is indeed reprsented wastefully, but unless the individual records are huge json+gzip is a perfectly serviceable “worse-is-better” solution.)

[1] https://github.com/ICRAR/ijson

[2] https://github.com/AMDmi3/jsonslicer

[3] https://github.com/danielyule/naya

Next Generation Shell. As a shell, it's a programming language and a UI. Half baked: programming language - pretty much done, we use it at work; UI - just starting to work on.

Ananlysis of what's wrong with current shells' UIs and how to fix it - https://blog.ngs-lang.org/2023/09/30/ui-in-ngs/

Project - https://github.com/ngs-lang/ngs

Any help would be appreciated of course :)

The plan for UI is at https://github.com/ngs-lang/ngs/wiki/UI-Design

The site is at https://ngs-lang.org/

Project: https://github.com/ngs-lang/ngs

There are number of new ones coming out ...and I'm curious of https://github.com/ngs-lang/ngs. As a language nerd, have you seen that?

Thanks, took a note - https://github.com/ngs-lang/ngs/issues/621