Richard Newman <holyg...@gmail.com> writes: > Whatever happened to engineers building a decent solution out of a > sense of pride, or even making the most basic half-assed attempt to > conserve resources?
I take your points but I think we may just have different priorities of what to conserve, so we could probably argue about this all day. To me disk space is cheap and simplicity precious. I'd rather waste 300mb of space then have to muck around sorting out link problems when I run the code on a different server and suddenly all the symlinks are broken because I forgot an obscure flag on my copy/tar/rsync/whatever. Hard links are better, there's much less that could go wrong (but obviously they have the limitation that they don't work across different filesystems). The implementation is also not so trivial as you make out. How does one even create a symlink (or hardlink) on the JVM (prior to the unreleased JDK7)? There's no way I know of to do it via the standard library. You'd have to resort to JNI or shelling out to "ln". What happens if you're on a platform or even just a filesystem that doesn't support links? Do you start littering the code with per operating system conditionals? If so, what happens if you're technically running on Linux but with a different userspace (perhaps Android or something) and there happens to be no "ln" binary? Another special case? Very quickly we're spiralling down into a mess of over-engineering. -- 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
