`ack -a` is your friend, Zed. No snark intended, that's all I have to say.
334 karma · joined December 17, 2008
`ack -a` is your friend, Zed. No snark intended, that's all I have to say.
Moreover, it did not take four years to develop multi-db support. This was a GSoC 2009 project that was merged in 2009.
http://www.microsoft.com/Security_Essentials/
It runs unobtrusively in the background (only a tray icon), is simple to use, and doesn't install additional cruft (e.g., the AVG IE toolbar).
However, if you do wish to proceed the best play to start would be with the official Manual of Patent Examining Procedure (MPEP):
Why read the documentation or look for examples when you can write a blog post screed and post it on HN?
This stereotypical perception of Houston is false, as it does have a diversified economy. For example, it is home of the Texas Medical Center -- the largest medical center in the world. In addition, is also as industrial center for aerospace, as NASA's Johnson Space Center is also located in Houston.
Unlike a simple civil contract dispute, for example, where the ambiguity usually lies in the terms of the agreement between the parties, what I'm referring to is the ambiguity inherent in the federal case law precedent surrounding derivative works -- let me explain.
Derivative works, as defined by the Copyright Act of 1976, are those "based upon one or more preexisting works" that have been recast, transformed, and/or adapted from their original form. [1] Specifically, there is differing authority as to the requisite level of originality required for a derivative work. For example, in Gracen v. Bradford Exchange, Judge Posner held that a "derivative work must be substantially different from the underlying work to be copyrightable." [2] Compare this approach with that of the second circuit in Alfred Bell & Co. v. Catalda Fine Arts, Inc., which rejected any novelty requirement, holding that a "distinguishable variation" of the original work would suffice to trigger copyright for a derivative work based on public domain sources. [3]
The required amount of originality has produced a circuit level split in cases involving the infringement of the exclusive right to prepare derivative works. Particularly, pictures taken from lawfully purchased books and mounted to a tile were considered, by the ninth circuit, a "recast or transform[ation of] the individual images" sufficient to infringe the original artist’s section 106(2) right. [4] The seventh circuit, in a strongly worded opinion by Judge Easterbrook, rejected this approach finding that the pictures were merely "bonded to a slab of ceramic ... [and] not changed in the process." [5] Easterbrook opined that the seventh circuit’s inclusive view of derivative works would create an expansive moral rights regime not explicitly authorized in the 1976 Act. [6]
In other words, until the Supreme Court rules definitively and resolves the circuit split, the threshold of originality necessary for a derivative work depends on the precedent your jurisdiction follows. Hence why it's more ambiguous than is typical of other topics in federal law.
[1] 17 U.S.C. § 101.
[2] Gracen v. Bradford Exchange, 698 F.2d 300, 305 (7th Cir. 1983).
[3] Alfred Bell & Co. v. Catalda Fine Arts, Inc., 191 F.2d 99, 102 (2d Cir. 1951) ("It is clear, then, that nothing in the Constitution commands that copyrighted matter be strikingly unique or novel. Accordingly, we were not ignoring the Constitution when we stated that a 'copy of something in the public domain' will support a copyright if it is a 'distinguishable variation' ").
[4] Mirage Editions v. Albuquerque A.R.T., 856 F.2d 1341, 1344 (9th Cir. 1988).
[5] Lee v. A.R.T. Co., 125 F.3d 580, 582 (7th Cir. 1997).
[6] See id. at 582. Easterbrook observed: "If Lee (and the ninth circuit) are right about what counts as a derivative work, then the United States has established through the back door an extraordinarily broad version of authors’ moral rights, under which artists may block any modification of their works of which they disapprove. No European version of droit moral goes this far."
http://ssrn.com/abstract=585922
Ambiguities in copyright precedent about what actually constitutes a derivative work will continue to vex the GPL for some time. The unfortunate truth is that there are no clear legal answers to many of these questions -- and that's kind of the point that Jacob is making in asking them in the first place.
Unfortunately, this is my typical experience with most Microsoft software products.
(1) DEBUG=False is not a fault of GeoDjango. By default when DEBUG is set, Django logs all queries put through the ORM. When you're using SQL statements with geometry values (which can be large), it's easy to exhaust the memory. I'll make this clear when I complete the docs prior for 1.0.
(2) You are using DWithin at your own peril. DWithin can use indexes cause because its a wrapper around Distance. Since you read the PostGIS docs so closely, then I'm sure you're aware that Distance returns the "cartesian distance between two geometries." If you're using WGS84 lat/lon coordinates, then you're also using a cartesian distance calculation method on coordinates in angular units. In other words, your distance calculations are wrong -- getting it right requires extra computation time.
(3) I've experienced problems with FastCGI, but have had no confirmations of this problem outside my laptop. My guess it's actually an underlying conflict with the latest version of flup and the use of ctypes. If you had taken this part of your post and placed it in a ticket it could be fixed; at the least a workaround would be provided. [Update: this problem is actually not related to ctypes/flup -- see Django ticket #9437]
Finally, at no point did you try and address your problems by (i) writing a message to the django-users list, (ii) filing a ticket explaining your problem, or (iii) visiting the #geodjango IRC channel and simply asking a question. Open source software is not a one-way street. If you had spent as much effort on this gripe post as participating in the community then your bugs and/or questions would have been addressed.