Google Introduces Portable Native Client, Makes It Easier For Developers To Add C And C++ Code To Their Web Apps
Native Client - a technology that allows developers to run native compiled C and C++ code as part of their web apps - has long been a part of Google Chrome. Even though other browser vendors haven't adopted it yet, Google is clearly putting quite a few resources behind this technology and at I/O this year, it announced Portable Native Client (or PNaCl, which Google says we should pronounce as "pinnacle"). PNaCl is now available in developer preview in Chrome 29 and will slowly find its way into the stable version over the coming months.
Qt 5.1 enters beta
Qt 5.1 comes a step closer with the release of the first beta of the next version which includes technology previews of Qt for iOS and Android, new controls and layout modules
The New Yorker Launches 'Strongbox' For Secure Anonymous Leaks
Today The New Yorker unveiled a project called Strongbox, which aims to let sources share tips and leaks with the news organization in a secure manner. It makes use of the TOR network and encrypts file uploads with PGP. Once the files are uploaded, they're transferred via thumb-drive to a laptop that isn't connected to the internet, which is erased every time it is powered on and booted with a live CD. The publication won't record any details about your visit, so even a government request to look at their records will fail to find any useful information. "There’s a growing technology gap: phone records, e-mail, computer forensics, and outright hacking are valuable weapons for anyone looking to identify a journalist’s source. With some exceptions, the press has done little to keep pace: our information-security efforts tend to gravitate toward the parts of our infrastructure that accept credit cards." Strongbox is actually just The New Yorker's version of a secure information-sharing ...
Paul Irish on Chrome Moving to Blink
I know you’ve been asked this plenty of times already, but: no new vendor prefixes, right? Right? Nope, none! They’re great in theory but turns out they fail in practice, so we’re joining Mozilla and the W3C CSS WG and moving away them. There’s a few parts to this. Firstly, we won’t be migrating the existing -webkit- prefixed properties to a -chrome- or -blink- prefix, that’d just make extra work for everyone. Secondly, we inherited some existing properties that are prefixed. Some, like -webkit-transform , are standards track and we work with the CSS WG to move ahead those standards while we fix any remaining issues in our implementation and we’ll unprefix them when they’re ready. Others, like -webkit-box-reflect are not standards track and we’ll bring them to standards bodies or responsibly deprecate these on a case-by-case basis. Lastly, we’re not introducing any new CSS properties behind a prefix. Pinky swear? Totes. New stuff will be available to experiment with behind ...
Quickoffice In The Browser: The Reason Why Is Microsoft Suddenly So Scared Of Google's Productivity Tools
We’re just a few days away from the start of Google I/O, the search giant’s annual developer conference, and while we actually know very little about what Google plans to announce during its massive, 3-hour keynote on Wednesday, there is something brewing in Mountain View that has Microsoft’s Office division on edge. Over the course of the last week, Microsoft started a very negative anti-Google Docs campaign that fits the mold of its more general Scroogled anti-Google ads. But why the sudden focus on Google’s productivity tools? That reason, I believe, is Quickoffice in the browser. Quickoffice, which Google acquired last June, allows users to read and edit Word, Excel and PowerPoint documents on the iPad, iPhone and Android. Unlike Google Docs, which remains a relatively limited productivity suite when compared to Microsoft Office, Quickoffice does a very nice job at allowing you to open and edit Office files without losing the document’s layout and other advanced features that ...