I’m pleased to share the registration of a new package, JSON3.jl, in the General registry, available immediately. Let’s cut right to the chase and answer the elephant questions in the proverbial discourse room: why do we need another JSON package in Julia? what does it offer distinct from what JSON.jl, JSON2.jl, or LazyJSON.jl offer? why spend time and effort developing something that’s “already solved”? JSON3.jl was born from the spark of three separate ideas, and a vision that they could com...
I don’t. But the last commit on JLD.jl was 3 months ago. Compare to 2 months ago for the last commit on HFD5.jl. For something like this I wouldn’t expect very frequent changes, so JLD seems alive. JLD2 is officially deprecated though.
Ahhhh I thought both JLD and JLD2 were deprecated. I’ll take another look. But HDF5 has been fine so far so no complaints.
I’ll have to take a look at serialization. But most of my data is use it for a paper and then archive. Which HDF5 does well, just curious what others were using.
I don’t. But the last commit on JLD.jl was 3 months ago. Compare to 2 months ago for the last commit on HFD5.jl. For something like this I wouldn’t expect very frequent changes, so JLD seems alive. JLD2 is officially deprecated though.
Why not Julia’s built-in serialization?
Ahhhh I thought both JLD and JLD2 were deprecated. I’ll take another look. But HDF5 has been fine so far so no complaints.
I’ll have to take a look at serialization. But most of my data is use it for a paper and then archive. Which HDF5 does well, just curious what others were using.
Since you like JLD2, there’s interest in reviving it.
Thanks for the update!