Rich Hickey on web frameworks
JOY CLARK: Awesome. I'll have to check that out. In your opinion, is there a benefit to opinionated approach to program architecture? I have some people who talked to me about Clojure and they're coming from the Rails world, or the Spring Boot in Java, and they're like "How do I write a web application in Clojure?" and I'm like, "Well, you can use all these different libraries, and they compose together, but you can pick and choose." And I think one of the reasons it's difficult -- well, it's not that difficult, but it's a reason that makes it more difficult to get started, because there's so many options. So is there a benefit to having a standard stack, where you can say "This is what you should use?"
RICH HICKEY: Well, some parts of that question are social, which I can't really speak to... I think certainly when somebody figures out how to do web development, they should encode it in a framework. But I'm not sure that that's a solved problem, and I think until it is a solved problem, opinions are very much opinions, and therefore you're at risk adopting a set of opinions that may not be an answer. I certainly let the community find its own way in this area, I think we have some very talented people doing really good work, including David Nolen...
RICH HICKEY: I think that it's really important to be able to say "I don't know yet." I'm not gonna go curt up this big thing, because you know, some of the things that you're talking about as being standard, they also have a bunch of known shortcomings... So while socially it's straightforward to say "Everybody's doing X", you may not like doing X after you've done it for a while and found all their problems.