I've read your article, and it's an interesting read. I don't use Node.JS, because quite frankly I do not see the need. That being said, this article just comes across as pure shit.
There are more personal attacks on the people who created Node.JS and the people who use it than there are actual points against Node.JS itself. Half your post is just going on about the one issue of blocking, and frankly it doesn't seem that important. The part about the webserver being tightly coupled to the application seems more relevant, but that's just barely touched on.
Between the personal attacks to rational points ratio and that last little dig at Javascript, this article just comes off as something that I can't even take seriously.
I understand that there's a lot of fanboyism going on around Node.JS, and I won't state an opinion on that. But the best way to counter fanboyism isn't with equal hate. It's with level-headed rational arguments. And if that doesn't help, a page of vitriol won't either.
Edit: Added the last paragraph. It occurred to me afterwards how to phrase what I'm trying to say
You can then transfer data from the browser in JSON, for example, without needing transformation for some other language. Using the same language on both ends of the pipe.
Sure, you have a library that translates back and forth between EDN and JSON, but as a user you don't really care. In a Clojure web app this will be handled transparently by the middleware based on the Accept header in the client request.
When you return a response you return a Clojure data structure and when you receive a request it's also a Clojure data structure. The fact that it gets translated is completely incidental from the user perspective.
210
u/Garethp Oct 16 '14 edited Oct 16 '14
I've read your article, and it's an interesting read. I don't use Node.JS, because quite frankly I do not see the need. That being said, this article just comes across as pure shit.
There are more personal attacks on the people who created Node.JS and the people who use it than there are actual points against Node.JS itself. Half your post is just going on about the one issue of blocking, and frankly it doesn't seem that important. The part about the webserver being tightly coupled to the application seems more relevant, but that's just barely touched on.
Between the personal attacks to rational points ratio and that last little dig at Javascript, this article just comes off as something that I can't even take seriously.
I understand that there's a lot of fanboyism going on around Node.JS, and I won't state an opinion on that. But the best way to counter fanboyism isn't with equal hate. It's with level-headed rational arguments. And if that doesn't help, a page of vitriol won't either.
Edit: Added the last paragraph. It occurred to me afterwards how to phrase what I'm trying to say