Using '<?' for embedded code is generally a bad idea since it conflicts with xml. PHP has had it disabled by default and not recommended for years.
CGI Using Node.js
81–88 of 88 posts
Re: CGI Using Node.js
#82I still prefer PyHP: http://www.ccraig.org/software/pyhp/manual/sample.html
Re: CGI Using Node.js
#83I was under the impression Node.js could already be used to run back end code? Could someone explain to me (who is new to the industry) the difference between what this does and what Node.js already did?
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.
Thanks for the clear explanation!
Re: CGI Using Node.js
#84Anyone have any ideas on the performance impact of this vs a typical NodeJS installation? I imagine there's a lot more overhead from starting up the process each time. A pretty cool idea but seems like this loses the benefits of NodeJS, speed and scalability.
Yes, but don't underestimate the value of penetration into cheaper hosts like DreamHost and Godaddy. PHP has always had quality issues, but survives on its eternal ubiquity, which is in no small part because of the CGI model.
Um, I would say it's mostly cause of mod_php support in apache, not cgi mode. Also, the fact that 5 minutes gets you AMP installed on just about any OS.
On the topic of this site though, 3 exclamation marks on the title? Really???
Re: CGI Using Node.js
#85This might be a really bad question that is just as applicable to Node.js in general, but doesn't this get confusing distinguishing between the server-side and client-side aspects?
Not really. Compared to using separate languages on the server and client, I feel that using the same language makes it a bit easier because I don't need to switch "mode" when jumping back and forth in the code. Like, when working on iOS apps, I sometimes write `self` instead of `this`. I have sometime seen the argument for Node of using the same code on client and backend simultaneously, but in practice I haven't fo…
Isomorphic apps. I've been playing around with React+Flux, and it's perfect. You can write your API in any language you want (even keeping it as part of node if you wish!), but the client is React. This means you can re-use almost exactly the same code for the frontend and backend. You get server-side rendering that delegates to the client once it has loaded.
I recently re-wrote my blog (https://blog.cesarandreu.com/) to take this approach. Repo: https://github.com/cesarandreu/trois-blog
The client bootstrap code that's used on the server is in client/middleware.js. Aside from that it reuses the exact same code.
Re: CGI Using Node.js
#86Earlier quoted context omitted.
I don't understand what you mean by "shoving it further down the throats of the masses". Are people being ordered to use Node.JS against their will somewhere?
Yes, usually by their manager. Things like Node.js get over-marketed to the public, managers are fooled into thinking it's a valid solution to their problem, then they force developers to use it against their will. node-cgi increases the number of scenarios where Node.js can be inappropriately forced down the throats of otherwise competent developers. And there's also the long tail of inexperienced developers who mad…
Well, if that is the case, maybe the issue is that such a person works in a bad environment? If you have a boss foisting technical decisions on you that are not suitable for the project, I'd expect that is a messed up environment in a lot of other ways. Is that Node's--or it's practitioners'--fault?
Re: CGI Using Node.js
#87Earlier 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."
How is that different from 2012 (or earlier)? I've had stuff on Heroku for years, never had a problem with this.
Re: CGI Using Node.js
#88Earlier quoted context omitted.
Use cases like Walmart, LinkedIn, Paypal, Ebay, the New York Times, Uber, Voxer, Microsoft and Yahoo?
They aren't use cases. They are company names. Which parts of their product runs on Node.js? And have you spoken to their developers about their projects? Just because a big company deployed something doesn't make it viable.