I thought about it and all that came to my mind that there simply
won't be
an upgrade path. Once you generated your code / templates / whatever
you
are done and up to yourself.
Having a supported upgrade path might be
1. to much for one or two persons to handle
2. Incompatible to the "generate" everything approach as one would
have to
make sure that old code, enriched with user code (which can be
anything),
still works with new code in whatever feature context that might be.
I think that's a very reasonable approach to take for the app template
approach to a "web framework". I just wonder if it will ever meet the
original posters presumed need for a web framework for the Clojure
community. I think an upgrade path is probably table stakes (for many
people, not all) for a web framework that will see wide adoption these
days.
I am curious, why did you upgrade your application over such a long
time?
Was this a product that got added new features over many years? Or was
it
more a "it's easy to do, so let's just stay up to date in case we
might
need it"?
It's the latter case, a few products that started 6+ years ago that
continue to grow in usage and features. I can also add that the benefits
that came along with each release (Rails 2, 3 and 4) have been critical
in being able to add new features and modernize the app. Building
features today with the tech we had in Ruby/Rails in 2009 would be very
inefficient.
Cheers,
Sean
--
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.
