Mac App Store Guidelines — Apple announce an app store for the Macintosh, similar to its app store for iPhones and iPads. “Mac App” no longer means generic “program”, it has a new and specific meaning, a program that must be installed through the App store and which has limited functionality (only one can run at a time, it’s full-screen, etc.). The list of guidelines for what kinds of programs you can’t sell through the App Store is interesting. Many have good reasons to be, but It creates a store inside itself for selling or distributing other software (i.e., an audio plug-in store in an audio app) is pure greed. Some are afeared that the next step is to make the App store the only way to install apps on a Mac, a move that would drive me away. It would be a sad day for Mac-lovers if Microsoft were to be the more open solution than Apple. cf the Owner’s Manifesto.

Cloudtop Applications (Anil Dash) — Anil calling “trend” on multiplatform native apps with cloud storage. Another layer in the Web 2.0 story Tim’s been telling for years, with some interesting observations from Anil, such as: Cloudtop apps seem to use completely proprietary APIs, and nobody seems overly troubled by the fact they have purpose-built interfaces.

Component Costs, Streaming Server, RC Parts, and MySQL SSD Goodness

Conflict Minerals and Blood Tech (Joey Devilla) — electronic components have a human and environmental cost. I remember Saul Griffith asking me, “do you want to kill gorillas or dolphins?” for one component. Now we can add child militias and horrific rape to the list. (via Simon Willison)

The SimpleGEO CTO and former Digg architect discusses NoSQL and location's future

I recently had a long conversation with Joe Stump, CTO of SimpleGeo, about location, geodata, and the NoSQL movement. Stump, who was formerly lead architect at Digg, had a lot to say. Here’s the highlights, you can find the full interview elsewhere on Radar.

Database expert Ronald Bradford on the pros and cons of migrating from Oracle to MySQL

Ronald Bradford has been guiding DBAs through key aspects of database integration for years. In this Q&A, he discusses the pros and cons of migrating from Oracle to MySQL (hint: it's not just about cost savings). He also weighs in on how Oracle's acquisition of Sun will shape the future of MySQL and its community.

Top for MySQL, Project Surprises, and Two Odd Little Programming Languages

mytop — a MySQL top implementation to show you why your server is so damn slow right now.

What Could Kill Elegant High-Value Participatory Project? — The problem was not that the system was buggy or hard to use, but that it disrupted staff expectations and behavior. It introduced new challenges for staff […]. Rather than adapt to these challenges, they removed the system. […] No librarian would get rid of all the Harry Potter books because they are “too popular.” No museum would stop offering an educational program that was “too successful.” These are familiar challenges that come with the job and are seen to have benefit. But if tagging creates a line or people spend too much time giving you feedback? Staff at Haarlem Oost likely felt comfortable removing the tagging shelves because they didn’t see the tagging as a patron requirement, nor the maintenance of the shelves as part of their job.

Gremlin — a Turing-complete, graph-based programming language developed in Java 1.6+ for key/value-pair multi-relational graphs known as property graphs. Graph structures underly a lot of interesting data (citations, social networks, maps) and this is a sign that we’re inching towards better systems for working with those graphs. (via Hacker News)

Anic — programming language based on stream and latches. I still can’t figure out whether it’s an elaborate April Fool’s Day joke that was released too soon, because the claim of “easier than *sh” is a bold one given the double-backslash and double-square-bracket-heavy syntax of the language. Important because it’s built to be parallelised, and we’re in transition pain right now between well-understood predictable languages for single CPUs (with hacks like pthreads for scaling) and experimental languages for multiple CPUs.

Toiling in the Data Mines — Tom Armitage describes the process that Berg calls “material exploration”. Programmers very rarely talk about what their work feels like to do, and that’s a shame. Material explorations are something I’ve really only done since I’ve joined BERG, and both times have felt very similar – in that they were very, very different to writing production code for an understood product. They demand code to be used as a sculpting tool, rather than as an engineering material, and I wanted to explain the knock-on effects of that: not just in terms of what I do, and the kind of code that’s appropriate for that, but also in terms of how I feel as I work on these explorations. Even if the section on the code itself feels foreign, I hope that the explanation of what it feels like is understandable.