He misses the point. You still need to operate in two different environments, but it's possible to share a large set of code, business logic and helper functionality.
Why node.js disappoints me
21–30 of 92 posts
Re: Why node.js disappoints me
#22Node's strength are in doing streaming UIs. Like realtime twitter feeds that push new tweets to the UI the moment they come in. It also does allow sharing code such as client side and server side validation. And if you use require.js you can develop modules that work server aide and client side.
Node.js does add new features, it's ease of use is a feature. Server side push used to be more complicated than it had to be. Python has twisted which I found difficult to setup as it required Python skills which I was rusty on and was more abstracted than I needed.
And of course server side JavaScript really is great, I don't see how it's that hard to understand two environments. You can't get rid of that they are different environments but they can share much code and does require one less language to use than most web app frameworks.
Re: Why node.js disappoints me
#23Earlier quoted context omitted.
Well some of the libraries out there are glue for C++ code. I think that is what he was inferring anyways.
I don't see how the argument is any different than saying you have to use a "different Python" for web development and client-server development.
It's a little bigger consideration in this case imo, because one of the big selling points is the ability to do "JS everywhere" and share code between the browser and server side of apps. Not that that's the only reason node.js exists, but it's a nice aspect that becomes harder if the server and browser sides diverge more.
Re: Why node.js disappoints me
#24I am of the opinion that there is no longer a need for server side templating languages and that they only serve to complicate the technology stack. With REST services, Javascript, CSS and HTML the technology stack for web development has become significantly simplified due to the fact that it is once again digestible. A designer can know HTML and CSS and provide designer services without having to know the intricaci…
> I am of the opinion that there is no longer a need for server side templating languages This makes the assumption that all apps are dumb frontends to a database.
Why? You can have arbitrarily complex logic and computation in client-side JavaScript. Whether it's a good idea is another question.
Re: Why node.js disappoints me
#25I am of the opinion that there is no longer a need for server side templating languages and that they only serve to complicate the technology stack. With REST services, Javascript, CSS and HTML the technology stack for web development has become significantly simplified due to the fact that it is once again digestible. A designer can know HTML and CSS and provide designer services without having to know the intricaci…
agreed. My first bigger node project ( http://tempalias.com ) works without generating even a single byte of HTML dynamically on the server. It's all plain HTML and JavaScript statically served and talking to the server via a REST API. This way I don't have to "bolt on" an API that might be incomplete. Instead, the frontend uses exactly the same API as any prospective client would. When I started the thing, I was usi…
Thanks for the reply, my next project is going to be doing the REST services with Node. I have been using Java for my services because until Node I really did not see a big enough reason to move platforms. What are you using for your REST services implementation, a Node library or did you roll your own? I did not know about Paperboy so thanks for pointing me to that project.
Re: Why node.js disappoints me
#26Earlier quoted context omitted.
I don't see how the argument is any different than saying you have to use a "different Python" for web development and client-server development.
It's a little bigger consideration in this case imo, because one of the big selling points is the ability to do "JS everywhere" and share code between the browser and server side of apps. Not that that's the only reason node.js exists, but it's a nice aspect that becomes harder if the server and browser sides diverge more.
Ah, if that's the case then I misread.
If the problem is the broken promise of writing code once than runs perfectly well on the server or in the browser then I guess I could see the frustration. Although, I'm not sure that's an entirely realistic expectation given the different roles you'd expect the server and client to fill.
Re: Why node.js disappoints me
#27I am of the opinion that there is no longer a need for server side templating languages and that they only serve to complicate the technology stack. With REST services, Javascript, CSS and HTML the technology stack for web development has become significantly simplified due to the fact that it is once again digestible. A designer can know HTML and CSS and provide designer services without having to know the intricaci…
> I am of the opinion that there is no longer a need for server side templating languages This makes the assumption that all apps are dumb frontends to a database.
No it makes the assumption that UI logic provides the best user experience when it is closest to the UI. Services can provide any form of calculation logic that one needs them too. UI logic is removed from the server and placed with the UI while business logic and data services remain with the business systems.
Re: Why node.js disappoints me
#28I don't understand the applause for Javascript. Yeah, we've unified on one language for client-side and server-side, but I don't like programming in Javascript. Why would I move to Javascript for server-side when I could program in Python and minimize the amount of JS I actually have to write?
Does everyone just like Javascript?
Re: Why node.js disappoints me
#29I don't understand the applause for Javascript. Yeah, we've unified on one language for client-side and server-side, but I don't like programming in Javascript. Why would I move to Javascript for server-side when I could program in Python and minimize the amount of JS I actually have to write? Does everyone just like Javascript?
To which I ask you to check out Objective-J.
Re: Why node.js disappoints me
#30I came into this one language concept in 2006. Back then there were already helma.org, which has functionality of RoR but it has being around since 1999.
Now Helma NG is relunched as RingoJS.org I would highly recommend checking it out.