- Multithreading is Hard — The compiler and the processor both conspire to defeat your threads by moving your code around! Be warned and wary! You will have to do battle with both. Sample code and explanation of WTF the eieio barrier is (hint: nothing to do with Old McDonald’s server farm). (via Erik Michaels-Ober)
- Improving Photo Search (Google Research) — volume of training images, number of CPU cores, and Freebase entities. (via Alex Dong)
- Is Google Dumping Open Standards for Open Wallets? (Matt Asay) — it’s easier to ship than standardise, to innovate than integrate, but the ux of a citizen in the real world is pants. Like blog posts? Log into Facebook to read your friends! (or Google+) Chat is great, but you’d better have one client per corporation your friends hang out on. Nobody woke up this morning asking for features to make web pages only work on one browser. The user experience of isolationism is ugly.
- GitHub Renders GeoJSON — Under the hood we use Leaflet.js to render the geoJSON data, and overlay it on a custom version of MapBox’s street view baselayer — simplified so that your data can really shine. Best of all, the base map uses OpenStreetMap data, so if you find an area to improve, edit away.
"open standards" entries
Engaging in-depth on the web with peer-to-peer connections.
As the web platform continues to evolve, tools have emerged for connecting people and computers in new and interesting ways. Web Real-Time Communication (WebRTC) stands out as one of the most significant and disruptive of these emerging technologies, allowing developers to embed peer-to-peer real-time communication in the browser without proprietary plugins, while breaking away from the traditional client-server paradigm.
Since Google released and open-sourced the WebRTC project in early 2011, the Internet Engineering Task Force (IETF) and the World Wide Web Consortium (W3C) have been working together to formalize the WebRTC standard and 1.0 stable release. Companies like Twilio and Vidyo have adopted WebRTC as a protocol for video chat in the browser, and established telco and VoIP players such as Cisco, Ericsson, and Telefónica have also lent support to the project.
At the most recent meeting of the IETF, Simon Pietro Romano, author of Real-Time Communication with WebRTC, hosted a panel to discuss developments in the WebRTC community and the road ahead. The panel, who are driving forces behind ongoing standardization and implementation, included:
- Justin Uberti, tech lead for the WebRTC team at Google
- Eric Rescorla of Mozilla
- Dan Burnett, editor of the PeerConnection and getUserMedia W3C WEBRTC specification
- Cullen Jennings, Cisco Fellow and Co-Chair of the IETF RTCWeb
I’d encourage you to listen to the whole conversation, but to get started, you might explore these highlights.
Thread Problems, Better Image Search, Open Standards, and GitHub Maps
An open standards battle in the U.K., mobile web development keeps growing, the upside of functional languages.
This week on O'Reilly: We learned how the U.K. government is facing pressure from all sides as it evaluates open standards, Maximiliano Firtman evaluated two years' worth of mobile web developments, and the utility of functional languages was put in the spotlight.
History of Keys, Open Standards, Values, and A Technology Stagnation
- The History of Key Design (Slate) — fascinating and educational. I loved the detector lock, which shows you how many times it has been used. Would be lovely to see on my Google account. (via Dave Pell)
- Why Telcos Don’t Grok Open Standards (Simon Phipps) — Their history is of participants in a market where a legally-constituted cartel of suppliers commission specifications for key shared standards. Technologists contribute freely on the expectation they will recoup their costs through royalties for licensing the patents on their contributions. […] Since every participant usually ends up having at least some ideas accepted, most participants in the process have some claims on each standard, with the result that net royalties payable between the participants may not be the relative burden they appear if taken in isolation. But it does mean that late entrants to the market can face an insurmountable cost barrier.
- The Next Big Thing (Umair Haque) — Umair frequently skirts the boundaries of Deepak Choprah-esque vacuous self-help, but I applaud his constant challenge to know your values and live truthfully by them. Hence here’s a minor challenge. Unless you want to spend your valuable life painstakingly eking out barely better solutions to problems we’ve already solved which give us answers that fail to matter in the enduring terms of the questions which do, consider the following: If we’re going to reboot our institutions, rethink our way of work, life, and play, then what are we going to redesign them for?
- The Jig Is Iup (The Atlantic) — The thing about the advertising model is that it gets people thinking small, lean. Get four college kids in a room, fuel them with pizza, and see what thing they can crank out that their friends might like. Yay! Great! But you know what? They keep tossing out products that look pretty much like what you’d get if you took a homogenous group of young guys in any other endeavor: Cheap, fun, and about as worldchanging as creating a new variation on beer pong. A different angle than Umair, but a challenge to think beyond building another declining value acquisition for your own personal benefit.
The UK government is fighting for open standards, but it needs help.
Influence, money, a bit of drama — not things you typically associate with open standards, yet that’s what the U.K. government is facing as it evaluates open options.
Network Snooping, Traffic Growth, Data Munging, and Open Interop
- Charles — a debugging proxy that lets a developer view all HTTP and SSL traffic between their machine and the Internet. (via Andy Baio’s excellent “How I Indexed The Daily)
- The Rise and Rise of Mobile Broadband — the Blackberry is now the standard measure of traffic, apparently. The outcome is simple – Cisco estimates that global mobile data traffic grew 159% last year and will grow another 131% this year. They contend traffic will increase 26 times versus 2010 levels, a 92% cumulative annual growth rate. I hope the network engineers are ready.
- Pattern — BSD-licensed Python tools for data retrieval (Google + Twitter + Wikipedia API, web spider, HTML DOM parser), text analysis (rule-based shallow parser, WordNet interface, syntactical + semantical n-gram search algorithm, tf-idf + cosine similarity + LSA metrics) and data visualization (graph networks). (via Hacker News)
- ODF Plugfest — when you have open standards, you need interop events like this to ensure that theoretically compatible programs are actually compatible. (via Jono Bacon on Twitter)