Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
So, in every case they choose a different ranking function, one that suits them. But of course, who would expect otherwise...
I actively tried to switch the default search engine to Google, and guess what, it was hard to find even knowing what I'm looking about.
If I was Google, I'd file an antitrust petition against this NOW.
Just sit down with it, but instead of writing new code, clean it up, or add some tests around it. There are two benefits:
- It will start looking much better, and you'll have a better feeling about it.
- You'll get yourself back into context, and before you know it, you'll find you want to do some development at it.
I have a similar problem: I have a project that I would really like to work on, but can find time only occasionally. I have found that coming back to it after a long time is very hard. I have my lists, but starting something is just formidable. So, I start by reading around, doing little stuff here and there and just cleaning it up, until I feel confident enough to do something.
And in general, it's very good to have your code thoroughly tested. Read about it here: http://manent-notes.blogspot.com/2008/08/developing-under-severe-time.html
Even nicer, try to search "google" and "microsoft" on bing. Compare.
I for one wouldn't trust a search engine so biased.
Link to Original Source
"Python 3000 (a.k.a. "Py3k", and released as Python 3.0) is a new version of the language that is incompatible with the 2.x line of releases. The language is mostly the same, but many details, especially how built-in objects like dictionaries and strings work, have changed considerably, and a lot of deprecated features have finally been removed."
Python 3k engines are up and running!"
Link to Original Source
- The Scope clause in Part 1 is inappropriate for an ISO standard
- Rework into an ISO-style multi-part standard
- Rework into a much more concise standard
- The information model in unnecessarily complex
- All examples should confirm to the XML specification
- DrawingML should be a separate standard
- OPC should be a separate standard
- The specification should not include binary notations
- The specification should not include unspecified features
- Option sets should be extensible and should avoid cultural bias
- OOXML should reference, use, and confirm to existing standards where applicable
- Lack of consistency in notation of values and dimensions
Fortress is released under a BSD license"