PUBLIC MARKS with search slow

I feel a lot of anger and frustration in this list.

Some of the items seem fine to me. I would not have written them like this ;). I disagree strongly with the last one, not because of the rationale but the form. It’s an unproven affirmation. There will be cases where it will be indeed the case and some not. :)

About geolocation privacy, the issue has hit the fan already ;) Advertising the user’s location is one way to make aware the user (or users in developping countries) of a mobile device. Blocking access to the location is *not always* a solution either. Sometimes the solution will be in how long the data can be kept, sometimes the solution will be in how the data will be used.

Repeat after me 1000 times: It is not a privacy issue, but a lack (or very thin) opacity issue. The network makes the access to information very quick and easy. There’s no need or no use to block it. There is need to be able to slow down the stream at will.

If anyone has ever been involved in Industrial Design, Interior Design or Architecture for a large (or even mid sized) corporation you will know the pain of an incredibly slow process punctuated by hours of mind numbing meetings where an original concept is diluted beyond recognition by accounts, engineering, marketing, middle management, upper management, directors and the weird guy who is either in the IT department or servicing the coffee machine.

Adding persistence is something that we will typically all have to do at sometime in most real world web applications and will definitely slow things down a little; so I thought I’d approach the problem using my latest favourite storage engine, CouchDB

a Restish example using CouchDB

Stop refreshing this page repeatedly

• Libraries - All libraries must be placed in a folder named "libraries", inside the sketchbook folder. Do not use the main "libraries" directory in the Processing distribution, as it is reserved for the core libraries, and is not visible on Mac OS X.
• XML - The XML library is now included by default, so you won't find it in the Import Library menu anymore. In addition, the XML library since 0135 has been greatly improved, making it compatible with far more documents.
• Processing.app - The Mac OS X release of Processing is now a single .app file, more befitting an OS X application.
• Processing.exe - The Windows release has a new launcher based on launch4j. Unfortunately, some machines have a problem with the new launcher that we haven't been able to track down. If you have trouble, please help us find the problem. PDE files are also now double-clickable on Windows.
• OpenGL - All OpenGL sketches now use 2x full screen anti-aliasing. This means that these sketches are always smooth, and the smooth() and noSmooth() commands are ignored. To return to the behavior found in the beta releases, see the hint() reference.
• P2D and P3D - The P2D renderer has returned (see the size() reference) and smoothing is now enabled for both P2D and P3D. Smoothing support is unfortunately incomplete, however, and sometimes thin lines can be seen inside shapes. This is a very high priority bug to be fixed in a future release.
• Candy and PShape - The Candy SVG library has been merged into the core, which brings along a new loadShape() command and a new PShape object. The special powers of PShape will be rolled out in future releases. For the time being, loadShape() works best with the default renderer (JAVA2D). Complex shapes will often appear jagged or not at all when rendered with P2D, P3D, and OPENGL. We've also added better support for SVG files created with Inkscape.
• PVector - We've added a new class called PVector, which is a simple three-dimensional vector (also known as point or tuple) class. This is useful for storing point data, or operations on 3D points.
• Tools - A new Tools API has been created for developers who want to contribute code that extends the Processing Development Environment in some fashion. Let your creativity flow with fantastical contributions like "Color Selector 2.0", "ROT13 Code Mangler", and "I Am Rich". Visit the developer page on tools for more information. Similar to libraries, tools are installed in a folder of the same name within your sketchbook folder.
• Asynchronouse Images - Big JPEGs and small pipes? We've added a new requestImage() that loads an image in the background so that your sketch doesn't freeze when loading lots of large images over a slow connection.
• Present - Present mode (full screen) is handled differently. When run inside the PDE, only Mac OS X uses exclusive mode with Present. Windows and Linux just do full screen windows. When run outside the PDE, all three simply create an undecorated window the size of the entire screen, and on the Mac, an option is added to the Info.plist file to hide the dock and menubar (since that cannot be done programatically from Java).
• Compiler - We've removed the old Jikes compiler and are now using another. We've also tried hard to improve the quality of error messages, though some are still real gems that invoke the complaints of mainframe computers in 1970s films.
• Internationalization - For better internationalization support, we've changed to UTF-8 encoding when loading and saving sketches. Sketches that contain non-ASCII characters and were saved with Processing 0140 and earlier may look strange when opened. Garbled text and odd characters may appear where umlauts, cedillas, and Japanese formerly lived. If this happens, use the "Fix Encoding & Reload" option under the Tools menu. This will reload your sketch using the same method as previous versions of Processing, at which point you can re-save it which will write a proper UTF-8 version.
• Java - Linux and Windows now inlude Java 6 update 10 with the download. We still don't have support for Java 1.5 syntax yet, but we hope that the performance boosts in Java 6 will help applications run well.

blessings and curses of magazines is that they take months to develop so there’s actual time to construct out a well thought argument