On Sep 17, 2011 1:13 PM, "Brandon McCaig" <bamcc...@gmail.com> wrote: > > On Fri, Sep 16, 2011 at 7:10 PM, Rajeev Prasad <rp.ne...@yahoo.com> wrote: > > why do i need a web app? becuase of size of my project? I mean if it is going to be a very big website with lot of pages and tables etc. should i have a webapp? > > Could you please explain what you mean by "website" [sic] and "web > app" [sic]? The meaning of each will vary by context and audience. >
Darn it, you and Lawrence beat me to it... At any rate, make you a web 2.0 app in the cloud and fend off tons of APT. Any buzz words I left out? Virtualization is so 2000 so I figured I could do without Here, let me try to help some: nytimes ok for general articles, wired isn't good for much, popular science is good for general science, etc. Uri has said to stay away from google when trying to learn how to program and good technique. While I disagree with this in general I would say that if you don't know the author, forum, or topic you're as likely to get absolute bullshit as not. It seems you've read an article written by a non technical person or idiot (one in the same maybe ;-) ) and decided to apply a *lame* term to a technical list. Webapp, really? And the difference between a web application and a CGI script 15 years ago? JavaScript maybe? Nope, not even that - ecmascript was already a standard. So, the difference might be that my cell phone has 100x the bandwidth my computer had access to 15 years ago. Heh, I doubt even that. I think the issue is that Americans got lazy once again (I love my kin) and thought typing app would save .... something (time, keyboards, discs, lives) who knows. But really, who cares. Technology has evolved in this space a bit but nothing revolutionary. I like json a shit ton better than soap (or other xml stuff), web browsers have gotten better, apache has gotten more bloated and I now have learned to favor nginx, mysql still does tons of stupid shit and most web sites still use it (?), etc. Lastly, if you have a bit site with tons of mainly dynamic content, you must be making major $$$ because you're going to be using tons of your resources to serve up (and develop, secure, and maintain) that content. No matter what, your jquery library should be static and perl should not touch it. CSS should generally be static (maybe you want to fix some browser issues - I wouldn't but whatever). Here's what you have, no matter what you do: a CGI, HTTP/1.1 (max) web site. That's it. You can put tons of stuff on the front end, tons more on the back end. But nothing you do will change that. This is 20 year old tech and it'll probably be another 10 years before either of these two things are upgraded.
