We had this 21 years ago: http://en.wikipedia.org/wiki/Netscape_Enterprise_Server
That was before async was discovered, an innovation by the Node development team.
CGI Using Node.js
71–80 of 88 posts
Re: CGI Using Node.js
#72Earlier quoted context omitted.
I don't think so. I'm all for lowering barriers to entry but there is a point where it becomes harmful to the ecosystem and to the developers themselves. Software development is, in my opinion, an engineering discipline, and so it's hugely important to use the right equipment for a specific task. If somebody truly can't learn how to do server-side development properly then they need to pass the job onto someone who c…
> it's hugely important to use the right equipment for a specific task Yet almost everything is built with a tool that's merely good enough for the task. Which usually makes it one of the right tools. You mention that "software development is hard" and even manage to talk about advancing the STEM field, but we're talking about handling some http requests and someone's weekend project that managed to register a domain…
> Yet almost everything is built with a tool that's merely good enough for the task. Which usually makes it one of the right tools.
I agree with you there so long as you understand which tools are good for which tasks.
> we're talking about handling some http requests and someone's weekend project that managed to register a domain name.
Node.js and cgi-node are not marketed as being strictly for weekend or toy projects. In fact, cgi-node is marketed as a tool that can do everything except cook your breakfast (see the last sentence of the cgi-node homepage). This just shows how badly over-marketed these products are.
> What is the right tool anyways
It's going to depend on the problem. Node.js's major failings are in the (arguably) poorly designed programming language and the continuous passing of callbacks. If your product can work within those constraints then Node.js might be the right choice. For most people Node.js will not be the right choice.
> Bottom line is that you're getting wound up by a project that has 9 commits
I don't care about how big or small the codebase is. I just care about it being marketed as a valid solution to most problems when it's really just a trap in most cases.
> I think your PHP job security is safe for now, my friend.
Pointless personal jab based on an incorrect assumption. I do not work in PHP and I don't see Node.js as a threat to the job security of any competent developer.
Re: CGI Using Node.js
#73Earlier quoted context omitted.
I'm not familiar with the benefits of HostGator but how is this better than spinning up a free Heroku dyno to serve your node.js app? That's also a very effective solution for low-traffic sites with a modest amount of host-side processing and more than enough for one sale a minute. It's got great options for 3rd-party service integration too (e.g. free MongoDB hosting for Not trolling, genuinely curious what the bene…
How is this better than spinning up a free Heroku dyno to serve your node.js app? Heroku's free service is more limited than it was in 2012. Current policy: "Heroku comes with 750 free dyno hours for development use. Beyond that you must pay for what you use."
That's 750 per month (a nice round number to cover a 31 day month):
https://devcenter.heroku.com/articles/usage-and-billing#750-...
Re: CGI Using Node.js
#74I much prefer meteors approach to all this.
Re: CGI Using Node.js
#75We had this 21 years ago: http://en.wikipedia.org/wiki/Netscape_Enterprise_Server
That was before async was discovered, an innovation by the Node development team.
Irony does not work well on the interweb, my friend.
To clear things up:
a) the Node team did not invent async programming
b) you kill the event loop, if you spawn it per request using CGI
Re: CGI Using Node.js
#76We had this 21 years ago: http://en.wikipedia.org/wiki/Netscape_Enterprise_Server
I only remember the server supporting Java servlets and Perl/sh/etc. CGI. Was there a JavaScript interpreter/runtime built into it, too?
I am actually just 2 years older than this thing, but Wikipedia said so, yes.
Re: CGI Using Node.js
#77Earlier quoted context omitted.
I'm not familiar with the benefits of HostGator but how is this better than spinning up a free Heroku dyno to serve your node.js app? That's also a very effective solution for low-traffic sites with a modest amount of host-side processing and more than enough for one sale a minute. It's got great options for 3rd-party service integration too (e.g. free MongoDB hosting for Not trolling, genuinely curious what the bene…
Free dynos shutdown every hour when it's not active.Starting up can take next to 10 seconds.Furthermore it's a free service,I don't think people should abuse their generous offer meant for testing purpose. There is no guarantee they will continue offering free dynos forever. Some people got burned recently hosting mongodb servers on a popular Saas that used to provide free mongodb hosting.Now that Saas is paid only,a…
I don't think it's just meant for testing. They choose to make the first dyno free so people will build on their platform. I have a couple of low traffic production apps that run fine at one dyno. If these apps ever get more traffic then maybe I'll scale them up and Heroku will get some money. I think that's the deal that Heroku is offering. I don't think I'm abusing their "generous offer". It's just business, from both sides.
Re: CGI Using Node.js
#78Earlier quoted context omitted.
This is designed to run without shell access, and without installing Node.js. Users on shared hosting cannot normally install Node.js, so are restricted to the usual LAMP stack, however this allows users to bypass this and process everything with Node.js.
> This is designed to run without shell access, and without installing Node.js. How can you run that without installing node itself? the godaddy tutorial specifically says one needs to upload nodejs on the server.Whether you are running apt-get install node or uploading it,you are still installing node on the server
apt-get requires root and can set up an http service as part of the installation. uploading it doesn't do that.
Re: CGI Using Node.js
#79We had this 21 years ago: http://en.wikipedia.org/wiki/Netscape_Enterprise_Server
Yes, I remember this. It had Netscape Livewire (I think that's what it was called?) that let you write very PHP-like server-side JS.
(It was terribly unstable, by the way.)