Thanks for this breakdown; a lot of what you're saying about Transit is
stuff I had inferred from prior announcements, but it's still enlightening
to see an explicit comparison to Edn and Fressian.
On Sunday, March 15, 2015 at 7:51:55 PM UTC-7, Alex Miller wrote:
Hi Ryan,
To answer the big
Nippy looks like an interesting project; I wasn't familiar with it.
However, it seems to be very Clojure-centric. Which is fine, at least for
certain use cases; it just doesn't really occupy the part of the
serialization format design space that I'm most interested in for
dynamic-object.
On
+1 nippy
I have successfully used it in few of my projects.
2015-03-17 5:30 GMT+01:00 Lucas Bradstreet lucasbradstr...@gmail.com:
I have had a lot of success with nippy
https://github.com/ptaoussanis/nippy, which is quite well documented. We
had problems with fressian round tripping Clojure
I have had a lot of success with nippy https://github.com/ptaoussanis/nippy,
which is quite well documented. We had problems with fressian round tripping
Clojure collections, as you've described.
It has a number of other features (compression, encryption) that I may end up
using. It has given
Hi Ryan,
To answer the big question, all of these data formats are in active use at
Cognitect and while I make no promises, I expect them all to be alive and
active for the knowable future. Each of them targets a different niche but
all of them share the qualities of transmitting extensible
This is an aside, but I wanted to add about translations...
An EDN generator is somewhat redundant from Clojure, but I usually use
fipp for standard formatting: https://github.com/brandonbloom/fipp
Also clj-yaml for YAML output, and Chesire or data.json for JSON. (Note
data.json has trouble
Thanks for the pointer to fipp, that actually looks like just what I need!
Fantastic.
On 11 July 2013 13:58, vrak...@gmail.com wrote:
This is an aside, but I wanted to add about translations...
An EDN generator is somewhat redundant from Clojure, but I usually use
fipp for standard
Perhaps you've not seen this:
https://github.com/edn-format/edn/wiki/Implementations
(But there's no CL implementation listed there.)
//Ben
On Tuesday, July 9, 2013, Rich Morin wrote:
I'm intrigued by edn (extensible data notation), as described here:
https://github.com/edn-format/edn
On Jul 9, 2013, at 13:37, Ben Smith-Mannschott wrote:
Perhaps you've not seen this:
https://github.com/edn-format/edn/wiki/Implementations
(But there's no CL implementation listed there.)
Yep; I had missed that. Thanks!
-r
--
http://www.cfcl.com/rdmRich Morin
Up at the top of the page you link to, there is a button labeled Issues
(at least if you are logged in with a free-to-create Github account), and
you can create an issue for this there.
Andy
On Fri, Mar 29, 2013 at 10:01 AM, Cedric Greevey cgree...@gmail.com wrote:
Thanks. I did look at the (incomplete) C version, and will take another
closer look before deciding what route to take, but I suspect
an Obj-C/Cocoa version would have different enough requirements to warrant
a new start, or at least a significant re-write.
Cheers,
Matthew.
On Wednesday,
According to the Implementations page of the edn wiki [1], libclj [2]
seems to be a possible starting point for that plan.
[1] https://github.com/edn-format/edn/wiki/Implementations
[2] https://github.com/brandonbloom/libclj
2013/2/5 Matthew Phillips mattp...@gmail.com
Hello,
a quick search
Java has arrays, lists, maps and sets, so does Ruby and Erlang.
If they were redundancies in these structures, can't see why these three
still
maintain this distinction. It's probably a safe bet to say that we need to
convey these
nuances in edn somehow.
Let's keep this in
My point was about the necessity or not to support both lists and vectors.
The original poster did not find any usefulness in supporting both, arguing that
they were redundant. He found the idea too Clojure centric.
I do not think it's Clojure centric and that the nuances are not worth to carry
On Mon, Sep 10, 2012 at 2:15 PM, Marko Topolnik
marko.topol...@gmail.com wrote:
Java has arrays, lists, maps and sets, so does Ruby and Erlang.
If they were redundancies in these structures, can't see why these three
still
maintain this distinction. It's probably a safe bet to say that we
Using an explicit tag or not is a minor detail but...
I'd argue that from the Clojure perspective it is not that minor. I think
the absence of the distinction would ruin the experience for Clojure users.
If you restrict an exchange format because some language(s) have no
literal
On Sep 8, 2012, at 9:28 AM, Steven E. Harris wrote:
Michael Fogus mefo...@gmail.com writes:
Data formats do not exist in a vacuum. They are parsed by languages.
Some may have a fine-grained distinction between lists, arrays/vectors
and sets and some may not.
The concern I have is for
Would you mind taking specific requests for clarification to the issues page,
so I don't lose track of them?
https://github.com/richhickey/edn/issues
Thanks,
Rich
On Sep 9, 2012, at 8:09 AM, Ben Smith-Mannschott wrote:
On Fri, Sep 7, 2012 at 3:01 AM, Rich Hickey richhic...@gmail.com wrote:
On Sep 10, 2012, at 8:44 AM, Ben Smith-Mannschott wrote:
On Mon, Sep 10, 2012 at 2:15 PM, Marko Topolnik
marko.topol...@gmail.com wrote:
Java has arrays, lists, maps and sets, so does Ruby and Erlang.
If they were redundancies in these structures, can't see why these three
still
maintain
On Mon, Sep 10, 2012 at 5:38 PM, Rich Hickey richhic...@gmail.com wrote:
Would you mind taking specific requests for clarification to the issues page,
so I don't lose track of them?
https://github.com/richhickey/edn/issues
Thanks,
Rich
sure thing
// Ben
--
You received this message
On Fri, Sep 7, 2012 at 3:01 AM, Rich Hickey richhic...@gmail.com wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely used as a data exchange format, e.g. as an alternative to
JSON.
Please have a look:
https://github.com/richhickey/edn
On Fri, Sep 7, 2012 at 3:01 AM, Rich Hickey richhic...@gmail.com wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely used as a data exchange format, e.g. as an alternative to
JSON.
Please have a look:
https://github.com/richhickey/edn
Michael Fogus mefo...@gmail.com writes:
Data formats do not exist in a vacuum. They are parsed by languages.
Some may have a fine-grained distinction between lists, arrays/vectors
and sets and some may not.
The concern I have is for someone wanting to define a format atop EDN --
or, to put
I'd say on the basis of convenience, since we get to serialize and
deserialize for free (o with customizations), and for most cases the author
on both ends is likely to be the same person or team. For other languages,
producers don't work any harder either way, and consumers are free to
On Fri, Sep 7, 2012 at 3:01 AM, Rich Hickey richhic...@gmail.com wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely used as a data exchange format, e.g. as an alternative to
JSON.
Please have a look:
https://github.com/richhickey/edn
If
Ben Smith-Mannschott bsmith.o...@gmail.com writes:
I follow forbidding -4bar since that means potentially unbounded
look-ahead to distinguish numbers from non-numbers.
Presumably forbidding .4bar is for the same reason, though .01
doesn't appear to be a valid numeric literal. (Numeric
Armando Blancas abm221...@gmail.com writes:
I'd say on the basis of convenience, since we get to serialize and
deserialize for free (o with customizations), and for most cases the
author on both ends is likely to be the same person or team.
I find that to be a specious defense. If we expect
In Clojure, all Clojure files are utf-8. I assume that is also required in
edn?
(I think it should be)
On Sep 7, 2012 2:01 AM, Rich Hickey richhic...@gmail.com wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely used as a data exchange format,
On Fri, Sep 7, 2012 at 3:01 AM, Rich Hickey richhic...@gmail.com wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely used as a data exchange format, e.g. as an alternative to
JSON.
Please have a look:
https://github.com/richhickey/edn
On Sep 6, 2012, at 11:56 PM, David Nolen wrote:
On Thursday, September 6, 2012, Rich Hickey wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely used as a data exchange format, e.g. as an alternative to
JSON.
Please have a look:
On Sep 7, 2012, at 12:33 AM, Daniel Pittman wrote:
On Thu, Sep 6, 2012 at 6:01 PM, Rich Hickey richhic...@gmail.com wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely used as a data exchange format, e.g. as an alternative to
JSON.
On Sep 7, 2012, at 4:36 AM, Ben Smith-Mannschott wrote:
On Fri, Sep 7, 2012 at 3:01 AM, Rich Hickey richhic...@gmail.com wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely used as a data exchange format, e.g. as an alternative to
JSON.
On Thursday, September 6, 2012 8:31:59 PM UTC-7, Weber, Martin S wrote:
The question that's left for me is: why vectors and lists? I mean, from a
data format perspective, and a non-clojure implementor, I'm not sure the
distinction makes sense. After all for the _data format_, in its
Hi folks,
I put some feedback up in a Hacker News comment
http://news.ycombinator.com/item?id=4487588, but it
probably makes sense to reproduce it here too, where comments
will be seen.
[By the way, Rich, I don’t use Clojure (... yet ...), but
your Stu’s talks are always an inspiration, and I
On Fri, Sep 7, 2012 at 3:45 AM, Rich Hickey richhic...@gmail.com wrote:
On Sep 7, 2012, at 12:33 AM, Daniel Pittman wrote:
On Thu, Sep 6, 2012 at 6:01 PM, Rich Hickey richhic...@gmail.com wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely
I addressed this here:
http://news.ycombinator.com/item?id=4489330
On Sep 7, 2012, at 2:36 AM, Elliot wrote:
On Thursday, September 6, 2012 8:31:59 PM UTC-7, Weber, Martin S wrote:
The question that's left for me is: why vectors and lists? I mean, from a
data format perspective, and a
On Thu, Sep 6, 2012 at 8:26 PM, Weber, Martin S martin.we...@nist.gov wrote:
The question that's left for me is: why vectors and lists? I mean, from a
data format perspective, and a non-clojure implementor, I'm not sure the
distinction makes sense. After all for the _data format_, in its
On Fri, Sep 7, 2012 at 3:40 AM, Rich Hickey richhic...@gmail.com wrote:
On Sep 6, 2012, at 11:56 PM, David Nolen wrote:
So will colons become whitespace in maps so the JSON using hordes have an
easy upgrade path? ;)
{foo :true} ;;boolean or keyword?
Requiring whitespace after the colon
@googlegroups.com] On Behalf Of Sean
Corfield [seancorfi...@gmail.com]
Sent: Friday, September 07, 2012 18:44
To: clojure@googlegroups.com
Subject: Re: edn
On Thu, Sep 6, 2012 at 8:26 PM, Weber, Martin S martin.we...@nist.gov wrote:
The question that's left for me is: why vectors and lists? I mean, from
On Fri, Sep 7, 2012 at 3:57 PM, Weber, Martin S martin.we...@nist.gov wrote:
Sure. Languages. This is a data format, not a language.
But languages will be doing the serialization / deserialization so
this is relevant.
Why should I not inflate a edn-list into a vector in my language? What if I
[seancorfi...@gmail.com]
Sentd: Friday, September 07, 2012 18:44
To: clojure@googlegroups.com
Subject: Re: edn
On Thu, Sep 6, 2012 at 8:26 PM, Weber, Martin S martin.we...@nist.gov
wrote:
The question that's left for me is: why vectors and lists? I mean, from a
data format
Sure. Languages. This is a data format, not a language.
Data formats do not exist in a vacuum. They are parsed by languages.
Some may have a fine-grained distinction between lists, arrays/vectors
and sets and some may not.
Why should I not inflate a edn-list into a vector in my language?
Is this too Clojure specific ?
I wouldn't say so. By definition the definitions of list,
vector/array and set encompass the behavior in question. I think
people are getting too wrapped up by the textual representations where
the forms (1 2 3) [1 2 3] and #{1 2 3} look fairly similar. By nature
Java has arrays, lists, maps and sets, so does Ruby and Erlang.
If they were redundancies in these structures, can't see why these three still
maintain this distinction. It's probably a safe bet to say that we need to
convey these
nuances in edn somehow.
My question was meant as a preamble to
which problem other than NIH is edn solving? - given it's a subset of
clojure's data notation, it's not really native clojure either, so you gotta
convert to/fro.
So: Why do we need another JSON?
I'm sure you have answers to these questions, possibly answered them before,
but definitely not
On Sep 6, 2012, at 9:10 PM, Weber, Martin S wrote:
which problem other than NIH is edn solving? - given it's a subset of
clojure's data notation, it's not really native clojure either, so you gotta
convert to/fro.
Of course it's native Clojure. Being a subset doesn't affect that. Clojure
Rich:
On Sep 6, 2012, at 9:10 PM, Weber, Martin S wrote:
which problem other than NIH is edn solving? - given it's a subset of
clojure's data notation, it's not really native clojure either, so you
gotta convert to/fro.
Of course it's native Clojure. Being a subset doesn't affect that.
Here we moved away from yaml (json was in its infancy when we opted for yaml).
We now serialize values over the wire using Clojure expressions and nippy to
get some
compression and speed improvement.
Nippy falls back to the reader if it does not know how to compress a given
value.
We plan to
On Sep 6, 2012, at 9:52 PM, Weber, Martin S wrote:
Rich:
On Sep 6, 2012, at 9:10 PM, Weber, Martin S wrote:
which problem other than NIH is edn solving? - given it's a subset of
clojure's data notation, it's not really native clojure either, so you
gotta convert to/fro.
Of course it's
Please don't use edn if you don't see the point. I'm not trying to convince
you or anyone else.
I expect there to be a point, and thus also expect it to be communicatable. If
there wasn't
a point, you wouldn't have chosen to use it in datomic, or create the page. I
feel you haven't
The rationale appears to be up now, and for my money, it is quite clear: JSON
not powerful enough, Clojure does too much and is a burden for implementers.
That said, I won't complain if somebody happens to implement full Clojure
serialization while implementing edn. ;-)
Stu
I expect there to
Stu:
The rationale appears to be up now, and for my money, it is quite clear: JSON
not powerful enough, Clojure does too much and is a burden for implementers.
That said, I won't complain if somebody happens to implement full Clojure
serialization while implementing edn. ;-)
The question
Looks great. What mime type should be used? application/edn?
Justin
On Thursday, September 6, 2012 9:01:15 PM UTC-4, Rich Hickey wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely used as a data exchange format, e.g. as an alternative
to
On Thursday, September 6, 2012, Rich Hickey wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely used as a data exchange format, e.g. as an alternative
to JSON.
Please have a look:
https://github.com/richhickey/edn
Rich
So will colons
On Thu, Sep 6, 2012 at 6:01 PM, Rich Hickey richhic...@gmail.com wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely used as a data exchange format, e.g. as an alternative to
JSON.
Please have a look:
https://github.com/richhickey/edn
The
On Thu, Sep 6, 2012 at 7:01 PM, Rich Hickey richhic...@gmail.com wrote:
I've started to document a subset of Clojure's data format in an effort to
get it more widely used as a data exchange format, e.g. as an alternative to
JSON.
Please have a look:
https://github.com/richhickey/edn
56 matches
Mail list logo
