> Thanks on those comments. I don't know python and neither > ruby, my question is is python hard to learn of a guy who has > pascal
As a former Pascal coder, it was a hard transition to go from a truly strongly-typed language (none of this wishy-washy pseudo-strong-typed stuff of C or C++, but true B&D typing of Pascal) to a duck-typed language. I occasionally miss the B&D typing of Pascal, and have considered going back to it on occasion, but I'm much more productive in Python, so I haven't. And I don't miss the edit-compile-execute-debug cycle, instead just using the edit-execute-debug cycle. I find Python very readable which is also the reason I find Ruby/Perl so infuriating. Ruby & Perl are write-only languages in the little experience I've had with them unless the author is very disciplined in coding readibly. However, I can come back to Python code I wrote a year ago and pick it up quite quickly. My kvetch with PHP is comprised of the flat namespace (everything is a function available from everywhere, whereas Python has a nice namespace using modules) and a radically changed object-oriented scheme between versions 4.x and 5.x even if PHP does have readily available cheap hosting services as a plus. > advantage I know for python over ruby is speed. Speed cuts both ways. The only way to be sure is to write the germane code in both and compare the particular task. I reiterate readability, good documentation, a helpful mailing list, "batteries included", and a powerful-yet-small working set of pieces that combine well as Python advantages. > I have heard people saying ruby on rails is a full stack web > application framework, is this the same for django? Without a clear definition of what's meant by "full stack web application framework", it's somewhat hard to answer that. Yes, Django provides an ORM layer to abstract the database layer (MySQL, PostgreSQL, or sqlite); separates aspects of the project into views/models/templates; can be served from the internal development server as well as apache or lighty; and even offers a simple-yet-powerful admin interface for getting up and running without the need to create a bunch of data-manipulation code yourself. > Which is better mod_python or FCGI? The core Django team seems to recommend MP over FCGI. However, a number of factors may contribute to the choice. MP can involve more system memory on the system, whereas FCGI (especially with lighty) has a smaller core footprint. FCGI can have your web server on one machine and your application server on another machine (or behind a load-balancer) if needed whereas MP runs the process in-line. You might have certain system constraints such as an old version of Apache or an admin that doesn't trust MP because it gives a lot of access to the server if it's shared; whereas I've seen more shared-hosting plans where FCGI is an option. FCGI is also a standard supported by a variety of servers while MP is an Apache-only module. Just a few more thoughts on things... -tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
