Why ClojureScript Matters
I think that the main argument presented in this blog -- "avoiding splitting" is  wrong :Splitting the development into frontend and backend is essential for developing maintainable code for large projects. Having a  well defined communication api  between backed and frontend defines responsibility for front end and backend developers and also enable better (j)unit  test cases. The communication overhead and associated documentation is beneficial in the long run as the code that is produced will be better understood by all , not just the lone developer; it also makes code reviews easier and allows new developers to take over existing code base when necessary. It is immature to think developers will only feel pride in their when they own the entire codebase, the ui-to-db stack;   The idea that "Lovingly crafted aesthetics in a codebase is key" is silly; code needs to be testable, well documented and highly optimized and re-usable.The "jostling of positions" are design discussions and they are important  part of the software development cycle.<p>I like Clojure and I am interested in learning ClojureScript but this blog post makes a poor case for it.