4 ms·

Thought process: Rails or Django will stand you in good stead for future projects and 'hire-ability' versus any PHP framework. Rails has easy hosting with Her

by wgx 15y ago

Thought process: Rails or Django will stand you in good stead for future projects and 'hire-ability' versus any PHP framework. Rails has easy hosting with Heroku. Django has a (slightly) less welcoming/active community than Rails. [1] A: Rails. [1 http://www.embracingchaos.com/2010/05/choosing-a-web-framework-python-django-vs-ruby-on-rails.html http://www.embracingchaos.com/2010/05/choosing-a-web-framewo...] Edit: +1 for the comment regarding timescales - you will likely need a substantial extension.

kls 15y ago
While I don't really do any of these, I would second this recommendation, Rails and Django are growing where PHP has kind of peaked. For me personally I don't use any of them anymore, I write web apps with JavaScript/CSS/HTML and I write back end services with Java or Node. Once mastered it is simpler than the server side frameworks, but it require understanding of the core technologies, it may be a little daunting for a beginner to start writing apps this way, because no one has packaged it up into a platform like ROR. You have to go out and assemble the pieces because they have not been assembled for you.
- swah 15y ago
  What are your experiences with this style of writing web apps and SEO?
  - kls 15y ago
    Most web apps that I create don't have SEO concerns, the sites that market them have SEO concerns. Lets delineate them as web sites and web apps for the sake of this conversation. A web app for me, replaces a desktop app, and does not need to be index-able by the search engines. There are exceptions like social type web apps, but for the most part it is not a concern in the apps I build. If I do have SEO concerns for a web app, I use Googles #! fragments, so that Google can parse the web app, in which case I just put a headless web browser on a server and serve the Google crawler through that headless browser. Now that Google can index sites that use JavaScript it is even less of a concern. Now for web sites that are used to market the application, I use Wordpress, Drupal, Alfresco, or some other content management system. I try to stick to pure web technologies like HTML and CSS and push them out to a standard web server, I am not a big fan of having a CMS that dynamically serves content, sometimes there is no other choice but I try to minimize it. Delineating web apps from web sites and using the appropriate technologies for each, usually keeps the two very clean, if I cannot delineate the two and I have heavy app requirements I will mix the two but I have only had to do that with one app I ever built and that was before the #! pattern was available.

by wgx 15y ago

kls 15y ago

While I don't really do any of these, I would second this recommendation, Rails and Django are growing where PHP has kind of peaked. For me personally I don't use any of them anymore, I write web apps with JavaScript/CSS/HTML and I write back end services with Java or Node. Once mastered it is simpler than the server side frameworks, but it require understanding of the core technologies, it may be a little daunting for a beginner to start writing apps this way, because no one has packaged it up into a platform like ROR. You have to go out and assemble the pieces because they have not been assembled for you.

swah 15y ago
What are your experiences with this style of writing web apps and SEO?
- kls 15y ago
  Most web apps that I create don't have SEO concerns, the sites that market them have SEO concerns. Lets delineate them as web sites and web apps for the sake of this conversation. A web app for me, replaces a desktop app, and does not need to be index-able by the search engines. There are exceptions like social type web apps, but for the most part it is not a concern in the apps I build. If I do have SEO concerns for a web app, I use Googles #! fragments, so that Google can parse the web app, in which case I just put a headless web browser on a server and serve the Google crawler through that headless browser. Now that Google can index sites that use JavaScript it is even less of a concern. Now for web sites that are used to market the application, I use Wordpress, Drupal, Alfresco, or some other content management system. I try to stick to pure web technologies like HTML and CSS and push them out to a standard web server, I am not a big fan of having a CMS that dynamically serves content, sometimes there is no other choice but I try to minimize it. Delineating web apps from web sites and using the appropriate technologies for each, usually keeps the two very clean, if I cannot delineate the two and I have heavy app requirements I will mix the two but I have only had to do that with one app I ever built and that was before the #! pattern was available.