I don't necessarily mind having to ignore some ads (otherwise, how could I browse the web?) but inability to download to my iPod would be a showstopper for me. That's how I listen to almost all my music these days, whether on the car stereo, home stereo, or out walking with earbuds.
I've been using Batik to view and convert SVG image files, and had some problems with incorrect rendering (e.g. dashed strokes getting inconsistent dash lengths). Seems to be all fixed with this new version.
Python has a large convenient featureful library, but so do many other languages. The biggest advantage it has for me is that Python looks almost exactly like pseudocode, without the overhead (braces, variable type declarations, etc) other languages make you go through. The effect is that coding is much easier and the results are much more readable when you come back to your code later and want to understand what you did.
The WiFi is interesting, but the lack of firewire is a disappointment, and in terms of shooting features (resolution, frame rate, etc) it is pretty much the same as the Canon 1D, a camera which Canon is expected to replace this fall. The low resolution and high frame rate show that it's intended for photojournalists rather than the general consumer market. The D2H will probably slow or stop the flow of photojournalists switching from Nikon to Canon, and maybe put a little more pressure on Canon to improve their own cameras, but I'm not sure it will have much other effect.
It's a.pdf.gz -- you have to gunzip it first. Unfortunately my browzer (Moz 1.2b) seems to think it's just.pdf and tries to open it directly in Acrobat; maybe their server is sending the wrong MIME type?
In scientific publishing, papers are sent around to the authors' competitors, who (along with checking correctness etc) have a vested interest in making sure their own prior art is properly cited.
In patents, applications are sent to patent examiners who have a vested interest in processing them as quickly as possible so they will be seen as "efficient" at their jobs.
Perhaps any reformed patent system should include some kind of formal peer review process?
It may be that we just haven't learned to see the JPEG2000 artifacts, unlike JPEG which we're much more familiar with.
On the dpreview page, the highest-quality (1Mb) files of JPEG and JPEG2000 look very similar, but even at the next lower setting (568k) the JPEG2000 has started to blur the subtle texturing on the watch faceplate into smooth blankness. Maybe ok for web viewing but not what I'd want happening automatically when I save a full-resolution image from my digicam.
That said, at anything below the 1M file size on that page, the JPEG2000's clearly look better than the corresponding JPEG's.
The Monthly article in question appears to be
"Morley Related Triangles on the Nine-Point Circle",
by Floor van Lamoen, Amer. Math. Monthly vol. 107, no. 10, Dec. 2000, pages 941-945.
The introduction says: "We identify two points M and H on Euler's nine point circle CN, found as intersections of three reflected lines. M and H each depend on the direction of a set of parallel lines. Posing the condition that M and H coincide for a certain direction, or that MH is a diameter of CN, we find two equilateral triangles in CN homothetic to Morley's famous trisector triangles."
More specifically, it reports "Error: The defined widths of table cells are not consistent." The problem seems to be a width="25" in one of the td tags, which should be width="25%" to match the other rows.
I think if more browsers adopted an always-there error-checking interface like iCab's (a small face icon that is either a smiling green or frowning purple; clicking on it produces a detailed error report) then there would be a lot more pressure on developers to produce decent HTML. It is amazing how few web pages actually get it to smile.
BTW,/.'s HTML gets a much longer error report with its frowny face.
Slashdot Mirror
Brooks Moses has some additional explanation which I found helpful: http://notes.dpdx.net/2006/10/06/penny-smiths-proo f-on-the-navier-stokes-equations/
I don't necessarily mind having to ignore some ads (otherwise, how could I browse the web?) but inability to download to my iPod would be a showstopper for me. That's how I listen to almost all my music these days, whether on the car stereo, home stereo, or out walking with earbuds.
At the Univ. of California, at least, we are not allowed to release student information such as grades to anyone, including parents, without the student's permission. See e.g. Section IV(B) of http://www.ucop.edu/ucophome/policies/bfb/rmp11.ht ml.
I've been using Batik to view and convert SVG image files, and had some problems with incorrect rendering (e.g. dashed strokes getting inconsistent dash lengths). Seems to be all fixed with this new version.
Python has a large convenient featureful library, but so do many other languages. The biggest advantage it has for me is that Python looks almost exactly like pseudocode, without the overhead (braces, variable type declarations, etc) other languages make you go through. The effect is that coding is much easier and the results are much more readable when you come back to your code later and want to understand what you did.
The WiFi is interesting, but the lack of firewire is a disappointment, and in terms of shooting features (resolution, frame rate, etc) it is pretty much the same as the Canon 1D, a camera which Canon is expected to replace this fall. The low resolution and high frame rate show that it's intended for photojournalists rather than the general consumer market. The D2H will probably slow or stop the flow of photojournalists switching from Nikon to Canon, and maybe put a little more pressure on Canon to improve their own cameras, but I'm not sure it will have much other effect.
You do know that you can program using the native Cocoa toolkit in Python, right? If not, check out http://pyobjc.sourceforge.net/
It's a .pdf.gz -- you have to gunzip it first. Unfortunately my browzer (Moz 1.2b) seems to think it's just .pdf and tries to open it directly in Acrobat; maybe their server is sending the wrong MIME type?
Some problems can be approximated nearly optimally, yes, but the paper proves that Tetris isn't one of them, it's NP-hard even to approximate well.
In scientific publishing, papers are sent around to the authors' competitors, who (along with checking correctness etc) have a vested interest in making sure their own prior art is properly cited.
In patents, applications are sent to patent examiners who have a vested interest in processing them as quickly as possible so they will be seen as "efficient" at their jobs.
Perhaps any reformed patent system should include some kind of formal peer review process?
It may be that we just haven't learned to see the JPEG2000 artifacts, unlike JPEG which we're much more familiar with.
On the dpreview page, the highest-quality (1Mb) files of JPEG and JPEG2000 look very similar, but even at the next lower setting (568k) the JPEG2000 has started to blur the subtle texturing on the watch faceplate into smooth blankness. Maybe ok for web viewing but not what I'd want happening automatically when I save a full-resolution image from my digicam.
That said, at anything below the 1M file size on that page, the JPEG2000's clearly look better than the corresponding JPEG's.
The Monthly article in question appears to be "Morley Related Triangles on the Nine-Point Circle", by Floor van Lamoen, Amer. Math. Monthly vol. 107, no. 10, Dec. 2000, pages 941-945. The introduction says: "We identify two points M and H on Euler's nine point circle CN, found as intersections of three reflected lines. M and H each depend on the direction of a set of parallel lines. Posing the condition that M and H coincide for a certain direction, or that MH is a diameter of CN, we find two equilateral triangles in CN homothetic to Morley's famous trisector triangles."
http://www.webstandards.org/ gets a frowny face from the HTML validity checker in my current primary browser, iCab.
More specifically, it reports "Error: The defined widths of table cells are not consistent." The problem seems to be a width="25" in one of the td tags, which should be width="25%" to match the other rows.
I think if more browsers adopted an always-there error-checking interface like iCab's (a small face icon that is either a smiling green or frowning purple; clicking on it produces a detailed error report) then there would be a lot more pressure on developers to produce decent HTML. It is amazing how few web pages actually get it to smile.
BTW, /.'s HTML gets a much longer error report with its frowny face.