I think of the difference in terms of what the architecture of your "site" or "app" actually is. For example, there's a LOT of jQuery out there used on websites for the express purpose of enhancing web pages...whether it's animations, form validation, etc. In these cases, however, the JS library is being used to enhance existing HTML pages.
Originally Posted by andjarnic
What I think of as web "apps", on the other hand, are those sites (typically single page, like Gmail) which are built particularly using a specific framework in order to deliver a cohesive, unified experience.
As others have mentioned, there's no right answer regarding which to use. I use jQuery at work all the time when I have a simple web form that needs a date picker and simple form validation. To me, this is using jQuery advantageously for what it's really good at--lightweight, simple enhancement.
Excellent response. That makes sense. Because I am not a strong html/css UI developer, more back end stuff, I am hoping ext-js fills that void where I feel like I can't build a fully functional site because I don't know enough of the web UI to really make it shine. Even for a small site I would consider ext-js + back end rest api to interact with the ext-js UI simply because I'd rather take advantage of what ext-js provides for me that I lack. It reminds me a bit of some Swing frameworks that built on swing to provide a Eclipse like application framework with menus, widgets, etc so that you didn't have to do all that yourself. You simply glued the code behind the components/events and database side of things.
Tags for this Thread