41–50 of 58 posts
Write a toy web server. It'll get you up to par with how the requests actually happen which is a good base for understanding CGI and the more complex systems.
He is just figuring out HTML. You are joking right?
It's practically requisite to understanding Rails or Django and is not so hard a project that you can't start to tackle it quickly (by reading any of the hundreds of simple web server tutorials online)
Write a toy web server. It'll get you up to par with how the requests actually happen which is a good base for understanding CGI and the more complex systems.
He is just figuring out HTML. You are joking right?
Blah, blah, blah. I think most of these recommendations are from 15-year-olds who just read about a cool web framework and are now spouting how damn good it is. Anyone recommending a framework before someone understands web programming isn't someone I would hire. Frameworks are where you go when you finally get what is missing with your web programming language. It might take you years to get to that point. Go with P…
Go to your local craigslist web/info design job page and run a search for PHP and count how many ads come up. Then run searches for Python and Ruby. That's enough help for me when it comes to making a decision.
Blah, blah, blah. I think most of these recommendations are from 15-year-olds who just read about a cool web framework and are now spouting how damn good it is. Anyone recommending a framework before someone understands web programming isn't someone I would hire. Frameworks are where you go when you finally get what is missing with your web programming language. It might take you years to get to that point. Go with P…
Earlier quoted context omitted.
Because I've seen PHP code and it looks too messy for me. Just my opinion.
Learn it with a framework, like CakePHP. Turns it into MVC programming like Rails or anything else.
Why not then just use Django or Turbo Gears or Ramaze or Nitro then?
In the end, you have to live with the underlying language.
Earlier quoted context omitted.
I agree. Rails is currently the way to go. It's much more mature than Django and has more flexibility and more mature gems/plugins. Lynda tutorials are great. I'd also recommend free ones: http://railscasts.com/ http://www.akitaonrails.com/2008/2/1/rolling-with-rails-2-0-... And for-pay ones at http://www.peepcode.com Also, grab "The Rails Way" book by Obie Fernandez (it's THE BEST book on Rails.. when you learn the…
I'll second the suggestion for "The Ruby Way" - it's under-rated and deserves more attention. I've heard good things about "The Rails Way" but haven't yet had a chance to look at it.
I also suggest The Ruby Way (though perhaps I'm biased); however, the Web dev section is dated. :(
Earlier quoted context omitted.
Thanks a lot, you really understood my problem :) I don't want to learn PHP, now I have to decide if it's going to be Python or Ruby. Can you please point me some of the information sources you used. Thanks again.
If you do decide to go with Python, web.py ( http://webpy.org/ ) is simple and you'll be up and running fast. If you're interested in how it all works, dig into WSGI. And if you find that web.py is too low level, transition to Django after you have a feel for how web apps work.
While webpy is small, I found myself often looking at the code, which has little commenting, to understand what's going on, or how to use a certain feature, mainly b/c the documentation is so lacking.
CherryPy might be a better choice.