mikejuk writes "Google and Opera split from WebKit to create Blink, their own HTML rendering engine, and everyone was worried about the effect on standards. Now we have the first big example of a split in the form of CSS Regions support. Essentially Regions are used to provide the web equivalent of text flow, a concept very familiar to anyone who has used a desktop publishing program. The basic idea is that you define containers for a text stream which is then flowed from one container to another to provide a complex multicolumn layout. The W3C standard for Regions has mostly been created by Adobe — a long time DTP company. Now the Blink team has proposed removing Regions support to save 10,000 lines of code in 350,000 in the name of efficiency. If Google does remove the Regions code, which looks highly likely, this would leave Safari and IE 10/11 as the only two major browsers to support Regions. Both Apple and Microsoft have an interest in ensuring that their hardware can be used to create high quality magazine style layouts — Google and Opera aren't so concerned. I thought standards were there to implement not argue with." Although mikejuk thinks this is a bad thing, a lot of people think CSS Regions are awful. Mozilla has never intended to implement them, instead offering the CSS Fragmentation proposal as an alternative. One major flaw of CSS Regions is its reliance upon markup that is used solely for layout, violating the separation of content and style that CSS is intended to enforce.

An anonymous reader writes "Google has launched Chrome apps for Android and iOS. The company is offering an early developer preview of a toolchain based on Apache Cordova, an open-source mobile development framework for building native mobile apps using HTML, CSS, and JavaScript. Developers can use the tool to wrap their Chrome app with a native application shell that enables them to distribute it via Google Play and Apple's App Store."

An anonymous reader writes with news of an interesting demo for clmtrackr (a Javascript library for tracking of facial features) that hides your face using 3D masks overlayed on the video from your webcam using WebGL. The effect is kind of neat, and a bit creepy. The demo works in Chromium here, but not in Firefox (Debian unstable). There are a couple other demos; the facial deformation demo is reminiscent of the intro screen to Mario 64.

mikejuk writes "Google's Dart just reached version 1.0, but now it seems that it has aspirations to being an international standard. The question is will this make any difference to the language's future? Given that Google effectively owns Dart, what advantage does standardization bring? The answer to what Google thinks it brings is indicated in the Chromium blog: 'The new standardization process is an important step towards a future where Dart runs natively in web browsers.' and this seems reasonable. A standard is something that would be required before other browser makers decided to fall in line and support native Dart. It is probably a necessary but far from sufficient condition, however, with Microsoft, Apple and Mozilla having other interests to further. Last but not least, having the backing of a standard might just encourage possible users to believe that the language won't sink if Google gets distracted with other projects and decides that Dart is dispensable. However, a strong open source development community capable of supporting Dart without Google's input would be a better reassurance. If you want to help, Google would like you to join the committee. After all, it still doesn't have a Vice Chair. So can we expect to see ECMA CoffeeScript or TypeScript in the near future? Probably not."

An anonymous reader writes "Google really wants Chrome apps to take off. Not only has the company added rich notifications, in-app payments, and an app launcher into its browser, but now it's developing ephemeral apps that launch by just clicking a link. There are two separate components here. Ephemeral apps (you can enable this under the chrome://flags/#enable-ephemeral-apps flag) let you try a Chrome app before installing it. Linkable ephemeral apps (under the chrome://flags/#enable-linkable-ephemeral-apps flag) meanwhile allow you to launch said apps from hyperlinks."

An anonymous reader writes "Google's Chromium team never ceases to amaze. Its latest project is a Chrome app-based Integrated Development Environment (IDE) codenamed Spark. For those who don't know, Chrome packaged apps are written in HTML, JavaScript, and CSS, but launch outside the browser, work offline by default, and access certain APIs not available to Web apps. In other words, they're Google's way of pushing the limits of the Web as a platform."

stoolpigeon writes "Yesterday marked the release of Dart SDK 1.0, a cross-browser, open source toolkit for structured web applications. The Dart SDK 1.0 includes everything you need to write structured web applications: a simple yet powerful programming language, robust tools, and comprehensive core libraries. The language has been somewhat controversial, but Google continues to move it forward." Reader slack_justyb adds some more detail: "The new release brings a much tighter dart2js compiler reducing overall JavaScript output up to 40%; Dartium — a version of Google Chrome that has the DartVM in addition to the JavaScript VM as native to the browser; PUB, a package manager for Dart add-ons; and several favorite 3rd party plug-ins that now come out-of-box, in addition to a lot of work for Dart server-side tools that can work to automate server side tasks and help in the construction of web pages. However Dart has many critics not only from the IE and Apple camps, as one would guess, but from the Firefox and Opera camps as well. In addition to the low adoption of Dart from third parties there are some asking where does Dart go from here? Especially considering that Google is one of the strongest pushers for EcmaScript 6."

An anonymous reader writes "Google today released Chrome version 31 for Windows, Mac, and Linux. The new version includes support for Web payments, Portable Native Client, and 25 security fixes. 'Under the hood, PNaCl works by compiling native C and C++ code to an intermediate representation, rather than architecture-specific representations as in Native Client. The LLVM-style bytecode is wrapped into a portable executable, which can be hosted on a web server like any other website asset. When the site is accessed, Chrome fetches and translates the portable executable into an architecture-specific machine code optimized directly for the underlying device. This translation approach means developers don’t need to recompile their applications multiple times to run across x86, ARM or MIPS devices.' You can update to the latest release now using the browser's built-in silent updater, or download it directly from google.com/chrome."

agizis writes "Google presented their new QUIC (Quick UDP Internet Connections) protocol to the IETF yesterday as a future replacement for TCP. It was discussed here when it was originally announced, but now there's real working code. How fast is it really? We wanted to know, so we dug in and benchmarked QUIC at different bandwidths, latencies and reliability levels (test code included, of course), and ran our results by the QUIC team."

sfcrazy writes "Chromium developers have started porting Chromium to X11 alternatives such as Wayland. Tiago Vignatti sent a message to the freedesktop mailing list, 'Today we are launching publicly Ozone-Wayland, which is the implementation of Chromium's Ozone for supporting Wayland graphics system. Different projects based on Chromium/Blink like the Chrome browser, ChromeOS, among others can be enabled now using Wayland.'"

An anonymous reader writes "Google today announced it is dropping Netscape Plugin Application Programming Interface support in Chrome. The company will be phasing out support over the coming year, starting with blocking webpage-instantiated plugins in January 2014. Google has looked at anonymous Chrome usage data and estimates that just six NPAPI plug-ins were used by more than 5 percent of users in the last month. To 'avoid disruption' (read: attempt to minimize the confusion) for users, Google will temporarily whitelist the most popular NPAPI plugins: Silverlight, Unity, Google Earth, Google Talk, and Facebook Video." Google offers NaCl as an alternative, and "Moving forward, our goal is to evolve the standards-based web platform to cover the use cases once served by NPAPI."

Last week you had a chance to ask Guido van Rossum, Python's BDFL (Benevolent Dictator For Life), about all things Python and his move to Dropbox. Guido wasted no time answering your questions and you'll find his responses below.

Two bits of Google news from today/yesterday. This morning, Google started rolling out a major update to mobile Maps. They've created a new tablet interface, improved integration with local places, integrated the Zagat guide, and enhanced navigation to automatically route you around traffic incidents. As usual lately, Google also removed a few features: Latitude and Check-ins. If you used those you'll have to use the Google+ application now. They also made a strange change to offline maps: instead of a menu option, you now access the area you want to make available offline and search for "OK Maps." On the Chrome front, Google released Chrome 28 yesterday, the first release featuring the WebKit fork Blink. The under-the-hood changes look promising, quoting the H: "The developers say that the increased speed is also thanks to the new threaded HTML parser, which frees up the JavaScript thread, allowing DOM content to be displayed faster. The HTML parser also takes fewer breaks, which is said to result in time savings of up to 40 per cent."

New submitter jshurst1 writes "Google has announced QUIC, a stream multiplexing protocol running over a new variation of TLS, as well as UDP. The new protocol offers connectivity with a reduced number of round trips, strong security, and pluggable congestion control. QUIC is in experiment now for Chrome dev and canary users connecting to Google websites."

hypnosec writes "Knoppix 7.2 has been released for public testing — unlike its predecessor, Knoppix 7.1, which was only made available through the annual Linux Magazine CeBIT edition. Based on Debian "Wheezy", Knoppix 7.2 packs quite a few new features, including newer desktop packages from Debian/testing and Debian/unstable Jessie. The latest version uses the Linux 3.9 kernel and xorg 7.7, and comes loaded with LibreOffice 4.0, GIMP 2.8, Chromium 27 (and Firefox/Iceweasel 21), Wine 1.5, and Virtualbox version 4.2.10. It uses LXDE by default. For users who still want to go for KDE or GNOME, version 4.8.4 and 3.4.2 of the respective desktops are available from the Knoppix DVD."

An anonymous reader writes "Last month, Google revealed that it was planning to finish defining its VP9 video codec on June 17 (today), after which it will start using the next-generation compression technology in Chrome and on YouTube. The company is wasting no time: it has already enabled the free video compression standard by default in the latest Chromium build."

An anonymous reader writes "Google today announced it is retiring Chrome Frame, a plug-in that brings Chrome's engine to old IE versions. The company wouldn't share an exact date, but did say it will end support and cease releasing updates sometime in January 2014. Google's reasoning appears to be based on the fact that Chrome Frame was released (initially in September 2009 and then as a stable build in September 2010) at a time when old versions of Internet Explorer, which don't support the latest Web technologies, were still in very high use."

hypnosec writes "Opera has released its first Chromium-based, completely re-engineered browser as a preview for Windows and Mac systems (download). The new browser has been given quite a makeover and comes with a refresh of Opera's 'Speed Dial' bookmarking feature. Users can now not only organize their shortcuts into folders, but also group them into folders automatically by simply dragging one bookmark over another. Opera has also included a faster bookmarking tool dubbed 'Stash,' allowing users to return to the links quickly. The new version has combined its search and address bars, allowing users to make searches directly via Amazon, Bing, Google and Wikipedia."

Via Phoronix comes news that Ubuntu is revisiting replacing Firefox with Chromium as the default browser. Reasons include that Chromium is the basis of Ubuntu Touch and their new web apps platform, and using a single browser for all versions of Ubuntu would simplify maintenance. From the article: "Expressed shortcomings of switching to Google's Chromium open-source web-browser is that data migration from Firefox isn't too obvious, extensions don't migrate between browsers, Chromium isn't supported on all architectures (e.g. PowerPC), the browser doesn't work with the Orca screen reader and doesn't integrate well for accessibility reasons, there is no native PDF plug-in, and Chromium is said to have worse performance under memory pressure. There were also some concerns expressed about differences with WebApps in Chromium. ... It looks like the switch to Chromium will happen in the name of a better user experience for the desktop with Chrome/Chromium now arguably surpassing Firefox in its features and performance while pushing Chromium as the default leads to a more consistent experience across Ubuntu form factors from phones/tablets to the desktop." The Ubuntu community will have their input solicited as the next step. The Ubuntu Developer Summit session has notes and a full video of today's discussion.

AmiMoJo writes "It looks like Mozilla are finally going to remove the much hated blink tag from the Gecko rendering engine that powers Firefox. Work to remove support for the tag, which was always non-standard and is not supported by the most popular HTML layout engines WebKit and Blink (Chrome, Safari, Opera, Android), is progressing and should show up in a future version of the browser." A comment attached to the discussion of this (not completed) move points out the odd possibility that Google's new Blink rendering engine may feature the blink tag via CSS animation, which would be "hilarious/awesome."