Sammlung von Newsfeeds
Hasselblad has announced the Stellar II, an enthusiast compact which the company says has been 'conceived and crafted exclusively for aficionados, collectors, and connoisseurs'. Like other recent Hasselblads, the Stellar II is a rebadged Sony camera - which in this case is the RX100 II. Available grip finishes include olive, walnut, padouk, and carbon fiber. You can pick one up for yourself at a price of $2395/€1650.
The Nikon D750 is a full-frame DSLR that mates features from the D810 with a 24MP sensor, providing a faster frame-rate than any non-pro full-frame Nikon DSLR since the D700. Its comprehensive still and video photography specifications are aimed directly at enthusiasts and full-frame upgraders. We've made a significant update to our D750 first impressions review including a shooting experience and studio scene analysis. Read more
Page-load times in the ten-second range are still common on modern mobile networks, and that’s a fraction of how long it takes in countries with older, more limited networks. Why so slow? It’s mostly our fault: our sites are too heavy, and they’re often assembled and delivered in ways that don’t take advantage of how browsers work. According to HTTP Archive, the average website weighs 1.7 megabytes. (It’s probably heftier now, so you may want to look it up.) To make matters worse, most of the sites surveyed on HTTP Archive aren’t even responsive, but focus on one specific use case: the classic desktop computer with a large screen.
That’s awful news for responsive (and, ahem, responsible) designers who aim to support many types of devices with a single codebase, rather than focusing on one type. Truth be told, much of the flak responsive design has taken relates to the ballooning file sizes of responsive sites in the wild, like Oakley’s admittedly gorgeous Airbrake MX site, which originally launched with a whopping 80-megabyte file size (though it was later heavily optimized to be much more responsible), or the media-rich Disney homepage, which serves a 5-megabyte responsive site to any device.
Why are some responsive sites so big? Attempting to support every browser and device with a single codebase certainly can have an additive effect on file size—if we don’t take measures to prevent it. Responsive design’s very nature involves delivering code that’s ready to respond to conditions that may or may not occur, and delivering code only when and where it’s needed poses some tricky obstacles given our current tool set.Fear not!
Responsible responsive designs are achievable even for the most complex and content-heavy sites, but they don’t happen on their own. Delivering fast responsive sites requires a deliberate focus on our delivery systems, because how we serve and apply our assets has an enormous impact on perceived and actual page-loading performance. In fact, how we deliver code matters more than how much our code weighs.
Delivering responsibly is hard, so this chapter will take a deep, practical dive into optimizing responsive assets for eventual delivery over the network. First, though, we’ll tour the anatomy of the loading and enhancement process to see how client-side code is requested, loaded, and rendered, and where performance and usability bottlenecks tend to happen.
Ready? Let’s take a quick look at the page-loading process.A walk down the critical path
Understanding how browsers request and load page assets goes a long way in helping us to make responsible decisions about how we deliver code and speed up load times for our users. If you were to record the events that take place from the moment a page is requested to the moment that page is usable, you would have what’s known in the web performance community as the critical path. It’s our job as web developers to shorten that path as much as we can.A simplified anatomy of a request
To kick off our tour de HTTP, let’s start with the foundation of everything that happens on the web: the exchange of data between a browser and a web server. Between the time when our user hits go and their site begins to load, an initial request pings back and forth from their browser to a local Domain Name Service (which translates the URL into an IP address used to find the host), or DNS, to the host server (fig 3.1).Fig 3.1: The foundation of a web connection.
That’s the basic rundown for devices accessing the web over Wi-Fi (or an old-fashioned Ethernet cable). A device connected to a mobile network takes an extra step: the browser first sends the request to a local cell tower, which forwards the request to the DNS to start the browser-server loop. Even on a popular connection speed like 3G, that radio connection takes ages in computer terms. As a result, establishing a mobile connection to a remote server can lag behind Wi-Fi by two whole seconds or more (fig 3.2).Fig 3.2: Mobile? First to the cell tower! Which takes two seconds on average over 3G.
Two seconds may not seem like a long time, but consider that users can spot—and are bothered by—performance delays as short as 300 milliseconds. That crucial two-second delay means the mobile web is inherently slower than its Wi-Fi counterpart.
Thankfully, modern LTE and 4G connections alleviate this pain dramatically, and they’re slowly growing in popularity throughout the world. We can’t rely on a connection to be fast, though, so it’s best to assume it won’t be. In either case, once a connection to the server is established, the requests for files can flow without tower connection delays.Requests, requests, requests!
The complexities of HTML parsing (and its variations across browsers) could fill a book. Lest it be ours, I will be brief: the important thing is getting a grasp on the fundamental order of operations when a browser parses and renders HTML.
- CSS, for example, works best when all styles relevant to the initial page layout are loaded and parsed before an HTML document is rendered visually on a screen.
Despite its name, blocking rendering for CSS does help the user interface load consistently. If you load a page before its CSS is available, you’ll see an unstyled default page; when the CSS finishes loading and the browser applies it, the page content will reflow into the newly styled layout. This two-step process is called a flash of unstyled content, or FOUC, and it can be extremely jarring to users. So blocking page rendering until the CSS is ready is certainly desirable as long as the CSS loads in a short period of time—which isn’t always an easy goal to meet.
In the next chapter, we’ll cover ways to load scripts that avoid this default blocking behavior and improve perceived performance as a result.
Samsung 18-55mm III lens review: A decent entry-point to the NX mount, but will it satisfy enthusiasts?
Panasonic has announced that its DMC-CM1 'compact camera with smartphone technology' will be sold in the UK. Originally the company had marked out France and Germany as the only countries to get the device, but citing 'high demand' it has included a limited number of UK stores to stock it. Read more
On Sunday, November 30, web designers and developers across the globe will celebrate Blue Beanie Day 2014, wearing a blue beanie to show their support for web standards. Join in!
“What’s Blue Beanie Day,” you may ask? Well, it’s possible you’ve seen it in years past: a host of avatars on Twitter and Facebook, with selfies galore, each sporting a little blue toque. Here’s the thing: each is a tribute to the hat that launched a thousand sites: the blue beanie worn by A List Apart’s own Jeffrey Zeldman in that infamous selfie, and that eventually emblazoned the cover of Zeldman’s Designing With Web Standards.
But this isn’t a plug for a book, or for the man wearing the rather fetching hat: rather, sporting a blue chapeau is a reminder that web standards—standards like semantic markup, neatly separated styles, and DOM scripting—are responsible for much of the work we do today. In the pre-WaSP, pre-DWWS world, we were forced to build to the idiosycrasies of each broken desktop browser—could you imagine anything like responsive web design without web standards? It’s true: we face a lot of challenges as the web moves beyond the desktop. But as wild and woolly as this multi-device version of the web is, it’d be significantly more challenging without the solid web standards support we enjoy today.
So if web standards have made your life a little easier—and I know I couldn’t do my job without ’em—then upload a shot of yourself wearing a blue beanie, hat, or cap to any of these fine social media locations:
- The Blue Beanie Day Tumblr
- The International Blue Beanie Day 2014 pool on Flickr
- Using the #bbd14 hashtag on Instagram
And there’s no need to wait until November 30: if you’ve got a beanie-enabled shot of yourself, then post away!
Der ADC-Wettbewerb 2015 kommt mit einigen Neuerungen wie dem Bereich „Out of any Box“. Teilnahmeschluss für Arbeiten und Kampagnen aus 2014 ist am 22. Januar.
Der Startschuss zum 51. ADC-Wettbewerb ist gefallen. Zu den Wettbewerbsbereichen Printmedien, Audiovisuelle Medien, Digitale Medien, Dialogmarketing/Promotion/Media, Branded Content/PR, Räumliche Inszenierung, Design, Editorial, Craft und Ganzheitliche Kommunikation kommt „Out of any Box“ hinzu. „Out of any Box“ Innerhalb dieser (Nicht-) Kategorie können Arbeiten eingereicht werden, die eine neue Dimension haben, die in keinen vorgefertigten „Kommunikationscontainer“ passen. „Wir möchten Arbeiten sehen…weiterlesen…
DPReview members are a talented group and we've been highlighting their photography in a series of readers' showcases. Recently we asked the Portrait & People Photography forum to share their favorite shots. They responded with excellent work both in and out of the studio, and we've picked a few of our favorites to share. See gallery
Flickr Wall Art now allows users to order prints from more than 50 million photographs, the service has announced. This follows Wall Art's arrival in October, and moves to include all applicable freely-licensed Creative Commons images, licensed artists images, and a curated selection of content from NASA. Read more
In this article, nature photographer Erez Marom shares the story of his panoramic shot 'Clouds over Skagsanden', taken earlier this year in the Lofoten Islands in Arctic Norway. His article covers everything from preparing to shoot at the location, to the shoot itself through to final post-processing of the resulting image. Click through to read Erez Marom's article 'Behind the Shot: Clouds over Skagsanden'
The Nexus 6 is Google's showcase phone for Android 5.0 'Lollipop' and the first Nexus device made by Motorola. It comes with a dual-LED ring flash, a 13MP sensor with a fast F2.0 aperture, optical image stabilization and 4K video recording. DxOMark Mobile put the Nexus 6 through its image quality tests and has just published the results. Read more