posted: 2005-09-11 12:46:38 perma-link, RSS comments feed
[LAFKON] - A movie about Trusted Computing.
ryvolcfr commented, on September 23, 2012 at 9:44 p.m.:
WIO8P1 <a href="http://hywkbnmlinis.com/">hywkbnmlinis</a>
lebron 15 commented, on January 7, 2018 at 5:37 a.m.:
I simply had to appreciate you yet again. I am not sure the things that I would've created without the actual ideas revealed by you regarding my industry. It was a daunting circumstance in my view, nevertheless seeing a well-written style you solved that made me to weep over joy. Now i am grateful for this guidance and then sincerely hope you are aware of a great job you're accomplishing teaching most people via your web page. Most likely you haven't encountered all of us.
[url=http://www.lebron15.net]lebron 15[/url]
Based upon your reading habits, might I recommend: Or, you might like: |
hosting: slicehost.com.
powered by: django.
written in: python.
controlled by: bzr.
monsters by: monsterID.
You've been exposed to: {'Science & Technology': 1}
Javier commented, on September 23, 2012 at 1:28 a.m.:
Thanks for the comments, Joe! I still have a lot to learn with Django, so some of the feteuras mentioned may take a while (plus I'm spending this week in classes and next week on vacation in Oregon, so I may not get back to things soon).I recommend giving Django a try, if only to see how it feels to you. I think that the major factor on deciding between the two is how easy it is for you to use, especially in my case. There happened to be a lot of things leading me to Python, so that may have helped push me toward Django some, too. It kind of felt like Rails was pushing me to do one thing when I expected another, and that might just have been the fact that I was less experienced with MVC frameworks in general.I've found a few examples of how to integrate Django with AJAX, but they're not as easy to follow (or as plentiful) as the Rails examples. I realized coming in that it wouldn't be as easy, but Django does let you choose your own JavaScript library, so maybe that's good in the end. Deployment seemed to be easier with Django, but that might also be because I'm more familiar with the environment on which I was deploying it.So basically there are tons of factors, but since in my case I got to choose whichever I was more comfortable with and I don't have any outside pressure to choose one over the other, I think I'm going with Django.