Can you please point me some of the information sources you used.
Thanks again.
Can you please point me some of the information sources you used.
Thanks again.
Online tutorials are good for a quick, down and dirty overview of a topic. But, if you're going to learn something a bit more in depth, I'd think that you're better off looking at a book. It's pricey, but it's worth it for me. I figure I'd spend $40 a month on tech books anyway. I'd might as well pay them and get the whole library as well as the Lynda.com video all at the same time.
Also, if you're really serious about it, I might consider finding a web database development class or certificate program somewhere. It might be slower going than you want, but you'll have a more complete understanding of the subjects once you were done.
Good Luck!
(PS: In the Bay area, foothill college is great, IMHO, for continued education)
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.
Python is a little more "corporate", with a little more regimented style (e.g. significant whitespace, PEP style guide - http://www.python.org/dev/peps/pep-0008/). CherryPy is super-simple to get started.
Ruby is a little more "hacker", with a more idiosyncratic cast of characters such as DHH and _Why and a little more focus on coolness and tricks. Rails is the way to go, but you can get up and running with the basics with the Camping Framework in about 10 minutes.
And from there you can start playing with Rails, which is a joy to use. I recommend starting with "Agile Web Development with Rails". I've only read excerpts from "The Rails Way" but it seems good, too.
Bottom line for me -- programming Ruby and building Rails apps is fun.
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.