Josh Tilles wrote on Monday, February 1, 2016 at 2:02 PM:
So, am I incorrect in seeing a similarity between the “data > code” mentality
and the rise of XML?
I see it as the difference between:
{:name "Sean" :age 52}
And:
public class Person {
private String name;
private Long age;
public Person( String name, Long age ) {
setName( name );
setAge( age );
}
public String getName() { return this.name; }
public Long getAge() { return this.age; }
public void setName( String name ) { this.name = name; }
public void setAge( Long age ) { this.age = age; }
}
Even if you made Person a value class by removing the setters, that’s a lot of
code obscuring a simple data structure. And with the data structure, you can
use any Clojure sequence function or hash map function, whereas with a Person
type, you’re stuck with the API presented.
Sean Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
