There seems to be a lot of complaining about this article being too simple. Hopefully you all noticed that this was part 1 of 4, and it gets pretty complicated and useful (to me at least) by the end.
part1:http://blog.wolfire.com/2009/07/linear-algebra-for-game-deve...
curious, in what comments do you see "complaining about this article being to simple"? I see complaints that it doesn't cover the underlying basics well, but nothing that to me seems to be what you mention?
It is a useful feature, and it was already there prior to this version. It could be turned on before, and looking at it, Arch and Debian are going to ignore upstream here (which is unusual for ARch, showing how dumb they think this is) and keep it off by default.
All that happened in v230 is that a default of off was flipped to on, nothing more.
What people criticize is that a default was change breaking behaviour and biting people who don't expect it. The feature is useful for system administrators who want it of course
KCacheGrind relies on using valgrind, which gives you extremely detailed information on runtime information by wrapping your execution context at a very low level. For this reason, it can track individual memory allocations, function call statistics, etc. However, for Python, that can be a bit overkill; usually you're just looking to measure what parts of your code are taking up executing time and heap space.
This package uses cProfile, psutils, and pstats go get runtime information on your code as it's running. It's doing what valgrind does but in a much "higher-level" fashion, in pure Python. This means that it can give you more relevant information about your Python code.
I really do believe some of the more negative stereotypes and stigma is beginning to lift surrounding the therapeutic use of entheogens. Like you stated time and accurate information with disciplined research hopefully leads to change. I think we have all seen that occur with marijuana for both medical and recreational use. I am very optimistic about the future of psychedelic use for those that need it and those that desire it.
I found Node.js a much simpler platform to use, mainly because there is no worrying about concurrency.
Because of the asynchronicity of Node, don't you explicitly have to worry about concurrency issues? I understand that with callbacks you can make things essentially linear from an execution standpoint (per connection), but I guess I'm a little confused by this statement.
Sorry to bring it up here, but can you check your email for an email from david@daviddworken.com? I previously sent in an XSS vulnerability that you fixed quickly, but I found a second one that has not been patched yet (despite being reported on March 26th).
It has now been fixed. The problem stemmed from allowing the `Javascript:` scheme for the home_page, download_url, and the url parameters in the setup.py.
Depends on what you mean by "parse". If all you want is to search a document that is known to be well-formed, find an element that meets a few criteria, and grab a value out of that element, you can sometimes get away with using regex to find a substring that "looks right" without actually parsing the document.
Running your document through an actual parser gives you access to more information about the structure of the document and the context of the elements of interest. Actually parsing your input is therefore more robust to unexpected variations than any of the superficially-cheaper alternatives that people try.
