The laptop is a great thing. It allows you to use your computer without having to be plugged up to a wall. However, back in the day you could not run your laptop off the batteries alone for too long. Thanks to people always looking to improve what we already have, we have made great jumps in the history of the batteries. When we think of laptop batteries many of us think about the rechargeable ones that we use today. However, did you know that they used to make laptops that ran off AA batteries? Not only did it take a lot of AA batteries to run a laptop, but they could not run it for long. Many people today remember the laptops running off the very heavy lead acid based batteries. Not only did these batteries not last long, but it made your laptopF3172A, very heavy. You might as well been carrying around a desktop. Since then the history of laptop batteries have kept improving. In fact, after we turned in the old lead acid batteries we moved on to the nickel cadmium batteries.
Third, the problem people have with Python’s “functions” is actually that they don’t understand the reason behind things like "".join(stuff) or even worse str(mything) which then just calls __str__. The problem is in most other languages Objects have methods you access with “.” and rarely do they use multimethods. Python however mixes these multimethods with regular methods, and sometimes inconsistently. This design choice has advantages in that common things like converting to a string don’t pollute the public name spaceion ZT1000,, but the disadvantage is that it is honestly kinda ugly.
If you can deal with these three things, then Python is actually very nice and easy. The most important advantage to using Python that I’ve found is that what you want to do and what you end up writing are actually very closely aligned. Given the above “problems” with the language (to outsiders) the end result is actually very readable. Things like docstring comments (if you start a block, don’t use pass to defer it, write the comment)Pavilion XZ200, and self for everything (never having to explain scoping is great) just make it easier to see what’s going on.
#10) Pinax
Pinax is a series of reusable Django components that you find on almost every site done today. Here’s the short list from their site:
openid support
email verification
password management
site announcements
a notification framework
user-to-user messaging
friend invitation (both internal and external to the site)
a basic twitter clone
oembed support
gravatar support
interest groups (called tribes)
projects with basic task and issue management
threaded discussions
wikis with multiple markup support
blogging
bookmarks
tagging
contact import (from vCard, Google or Yahoo)
photo management
Now, normally when someone throws a laundry list of components at you,Pavilion ZT1100,the experienced reader says, “Yeah, those will be great until I have to modify the damn curved corner to be cornflower blue.” In this case though, I’m seeing that because of Django’s heavy focus on allowing for modular components right from the start, you can use these or modify them easily without having to tear your hair out. If one of the above components doesn’t quite work, then you should be able to (in theory) write your own and plug it in.
My guess though is that you’ll probably end up just modifying what they have since there’s like 90% of the functionality you’d find on nearly any social network site. In fact, I’d say Pinax is basically the same functionality that companies have paid huge consulting fees to have implemented.
I would be very careful running to use this on a major site or paid gig before you’ve actually sat down and put something real-ish together. James Tauber and friends are more than eager to probably work with you if you got ideas (and hopefully code), but if you start drooling when you read the above list and then expect it to magically reduce your time to delivery for a million dollar project, then you are probably going to get bitten.
Then again, I could see using Pinax to start many different sites and use it as the basis for getting your potential users/customers to tell you what they don’t like. My experience has been that users can’t tell you what they want since theyOmnibook XT1000, can’t conceive of the web site in their head, but if you show them something they’ll have plenty of ideas and needs for you.
That’s My One Battery Review Of Django
Alright, so I’ve laid out what I like, but I really only found these things by giving Django a go. Will I use it in the future? Sure, I’m planning on changing Son of Sam’s name to something more reasonable and doing a couple of sites with it. Now that I’ve used Django, I’m just gonna integrate SoS with Django and make things easy on myself. The sites I want to do can easily reuse portions of Pinax so it’ll be interesting to see how far along I can get before I hit a wall.
At this point, the only warning I’ve received is that deployment is hard, but then, Omnibook XT1500,deployment is hard with every web application once you start getting serious. No reason why Django would be any easier or harder.
You Wanna Try, But You Don’t Know Python?
I’ll tell you a secret, I didn’t type much Python to go through this tutorial. I actually just whizzed through it and cut-paste most of the code right off the web page. My goal was to go through the sample to understand the system, not to exercise my typing abilities. If you don’t know Python, then just try some cut and paste yourself.
Or, if you want to just try setting up a real Django app for yourself, try this tutorial on getting Pinax running. That’ll let you play with some of the gear without doing much.
Then, try out the tutorial anyway. F2019,It’ll be interesting to see how far someone can get without actually knowing much Python.
Of course, if you find you need to first learn some Python, then please don’t tell anyone I told you to skip the RTFM ritual.
没有评论:
发表评论