On 03/05/2015 01:37, Luc Prefontaine wrote:
Business case...
I have two business cases at hand.
None can be done with frameworks w/o making the end products look like any
other one in their respective space and having to bend to framework limitations.
Being disruptive requires a different approach.
Having to write all these individual libs ourselves would make these two
product sets much more difficult to create. Experimentation would also suffer a
lot.
Now we have the elements to create new recipes instead of everyone eating the
same dry cake that's been left on the shelf for a year.
Aside from HR tagging, I see little value in a branded framework.
Being reluctant to be part of a tagged herd, I can't agree with you :)
But given my (bad) character this may explain that :)
Luc P.
All I'm saying is it doesn't have to be either/or. Clojure is big enough
for modular and (relatively :)) monolithic approaches.
gvim
--
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.
