zaphoyd

I use an rMBP full time at work as well with no trouble using an Apple thunderbolt display, a 27 inch dell display (via mini displayport), and a fourth 1200p display via HDMI. I'd definitely suggest going for displayport if possible over the finicky DL-DVI adaptors.

fair enough

G++ still doesn't support all of the C++11 standard library so that is not entirely true. (Clang's standard library implementation, libc++, is C++11 feature complete as well)

A single current generation Thunderbolt port runs two separate 10Gbit channels. Each channel is a mux of PCI-E data and a DisplayPort 1.1a stream. Two displays (each up to DisplayPort 1.1a's 8.64Gb maximum bandwidth) can be driven on one chain, one off of each channel. This can either be two Thunderbolt displays or one Thunderbolt display and one pass through raw DisplayPort display at the end.

Some restrictions apply due to the need for one Thunderbolt controller chip per display to do the DisplayPort demuxing. A Thunderbolt monitor will typically have one Thunderbolt chip and will use its DisplayPort output itself. A DisplayPort display can't be daisy chained directly after a Thunderbolt display (but can after a non-display Thunderbolt peripheral) for this reason.

It sounds like (according to the OP article) that the 2013 Thunderbolt chips (Redwood Ridge) will allow DisplayPort 1.2 pass through only. In this configuration the port could either be run as a Thunderbolt chain (with the above limitations to 2xDP 1.1) or as a DisplayPort 1.2 port. In 1.2 mode Thunderbolt peripherals couldn't be used, but DisplayPort 1.2 features (in particular 4k support and MST) could be used. Presumably the 2014 20Gbit channel Thunderbolt could allow 2xDP 1.2 as that tops out at 17.28Gbit.

Edit: yes, this means that devices sharing the chain with two Thunderbolt displays will have constrained incoming bandwidth. Probably even more so as the only Thunderbolt displays in existence also sport USB, speakers, a webcam, FW800, and Gigabit Ethernet, which together could easily eat up the remaining bandwidth on the TB channel. This may also be part of the reason why Apple hasn't released an updated Thunderbolt display with USB3, 2x10Gbit doesn't go very far with a pair of 27 inch displays hogging most of it.

A MacBook air with 1 current generation thunderbolt port can drive two 2560x1440 thunderbolt displays via daisy chaining.

I've purposely kept my iPad on 5.x because iOS 5 maps is the only iPad maps application that works well with public transit routing. iOS 6 maps doesn't do public transit at all, Google Maps and all the good third party transit routing apps are iPhone only.

Also a bunch of the new iOS 6 features (like Passbook, photo panorama, certain geofences, and the updated phone app) are not available at all on iPads. Siri (maybe?) and IPv6 over LTE are the only iOS 6 features I feel I am missing on the iPad so I am in no huge hurry to upgrade.

In my case: I'm reading this on the bus in a loud environment where I pay through the nose for mobile data.

This is getting too complicated. :( Does anyone have a good link for which iPhone/iPad models work on each technology (HSPA+/LTE) in each tmobile market?

Simtower definitely seemed to simulate individuals and had a population cap of 15-20k. Its path finding was drastically simpler though.

Every floor (110 floors max) was essentially a single zone that could be crossed instantaneously so each person needed a path only from floor A to floor B. There were strict limits as well about how many transfers were allowed per path and how many total stairs, escalates, and elevators were build able.

Sim City 4 allowed many millions of "people" on networks of significant complexity. The SimTower simulation was simple, satisfying, and relatively bug free. It also wasn't complex enough to continue to be satisfying for 10+ years the way SC4 has been.

Seconding this. The 2012 "update" was no more than a slight rearranging of CPU and RAM within that same generation of parts. The thing still uses all 2010 era parts (radeon 5xxx graphics, westmere xeons, 3gbit SATA, PCI-E 2, no thunderbolt). It has been "due" for an update since sandy bridge xeons were released in early 2012.

looks like 4GB

I would guess that scale in this context refers to the extent to which the calving happens rather than a specific scale named calving.

See http://dev.w3.org/csswg/mediaqueries4/#luminosity

Has anyone here come across any particularly good books or other resources on functional style programming in C++? Especially ones that have been updated for C++11s new functional features.

One area where IPv6 will have "fewer hops" is in cases where carrier grade NAT is being used in mobile networks. With IPv4 and CGN all traffic must be routed from cell sites to central offices with CGN hardware. With IPv6 traffic can be routed directly from cell sites to its destination without having to first travel to a central aggregation point with special hardware.

I am also a fan of "X in pure CSS" in moderation, particularly the ones that model things that I've needed to do to implement certain simple embellishments in ways where using images makes the site harder to change/maintain/retina-fy. For example, speech bubbles, arrows, engraved text, rounded objects, some types of icons, etc.

Does anyone know how CARP on FreeBSD compares to keepalived on Linux?

Do you have a source for PHP 5.5 dropping straight MySQL support? I'd like to read more.

This. I've been looking for a good email solution for personal+freelance work with decent privacy, security, and reliability. I don't need 24/7 support. I am absolutely willing to pay for it. But pricing per mailbox with Google apps adds up really quickly even with just 4-5 boxes. I'd like to be able to make separate mailboxes for my partner and to separate several different classes of email (personal, business, limited access, catch all, etc) for security purposes. These things don't need extra support or space, I can't stomach an extra $50/year for what amounts to aliases with passwords.

Has anyone found a good solution for this? I could host it myself but that is a lot of hassle, free email accounts have ads and rarely let you use your own domain. The best I've found so far is email through a shared hosting provider, but it has limitations of its own (no IPv6, no 2 factor auth, self signed TLS certificates, etc). The cost is similar to a Google Apps account but without the linear price increase per mailbox.

For smaller deployments (they have a 50 domain limit on the free accounts), Hurricane Electric DNS has been great. The business case is straightforward and they have top notch IPv6 support.

This uses SNI (which as mentioned in the parent lacks support in certain popular old clients, most notably Windows XP)

HTTP and HTTPS are served on different ports so using a single IP for both typically isn't an issue. The issue here is that HTTP allows you to host multiple sites from one IP address, whereas HTTPS can only deliver a single certificate per IP address. This requires 1 IP per SSLed hostname. SNI lets you send multiple certificates on one IP, but client support isn't good enough yet. Multi-name certificates work better but can be more expensive.

The article suggests that the two machines could be running different operating systems and be placed on different networks/locations to reduce the chances of a single attack compromising both systems.

a /64 gives you a single subnet with effectively infinite size. A shorter prefix would allow you to have multiple subnets for isolating things like gaming devices, guest networks, VPNs, etc. For IPv4 the ability to do this was basically a pipe dream, for IPv6 the addresses are there, we just need to coordinate how ISPs hand them out and how consumer routers manage them.

In short, one /64 is sufficient for duplicating an IPv4 like situation. A /60 or /56 gives us more room to innovate in new types of home networks.

Not only are they making large infrastructure investments, a many of their customers (including myself) can get IPv6 service from all three of those companies today and have been able to for some time.

Assuming you arent CPU or memory limited, the bottleneck was originally largely due to gigabit Ethernet's support of unswitched hubs and as such uses CSMA to detect collisions. In order for this to work there is a minimum transmit timeslot to ensure that collisions can be detected at the full round trip delay of a ~100m network.

Effectively a 1Gbit Ethernet node must transmit at least 512 bytes during its timeslot. If it has that much to send then it all goes out at 1gbit. If it only has a few bytes to send (a tcp ack for example) then it must idle for a bit to make sure there wasn't a collision.

In theory gigabit Ethernet should perform at 1gbit for sustained transfers but much worse for workloads with more sporadic sets of smaller packets. In practice, especially on core switches and routers, modern techniques like frame bursting (sending multiple small packets going to the same destination back to back) even things out more.

10gbit Ethernet and above get rid of the carrier sense collision detection support all together and require the entire network to be point to point with switches. It has no minimum timeslots or packet lengths.

I had this issue as well with the web streaming versions and plenty of free disk space. I ended up just pulling them up in iTunes which downloaded the whole thing and then it played fine. Something to do with the adaptive HTTP streaming I would guess.

comcast assigns a /64 if you plug in a router that supports DHCPv6. You get a /128 if you plug your macbook air straight into the modem. =)

Amusingly even if the Comcast LAN prefix is static most operating systems by default will cycle your address anyways. In IPv6 a dynamic address is now a Feature!

Whether or not the Comcast LAN prefix changes is a good question though. I've seen no evidence that they plan to deliberately change them. My Comcast IPv4 address stays static pretty much until I reset my modem and even then it often grabs the same v4 address again.

I did a bit of really basic testing earlier today and no amount of modem resetting seems to cycle the IPv6 prefix I am getting delegated.

In the end though, dynamic DNS does a very good job of dealing with the occasionally changing prefix and IPv6 gets rid of the need to do port forwarding so maintaining dns records with public addresses to machines on your home network is actually possible now. I am happy to report that (with the proper firewalls in place) it is downright awesome to have IPv6 at home and at work and on your phone. I can't wait to see what sort of new home cloud tech this will enable.

Android phones on Verizon's LTE network get a global IPv6 address by default. Their firewall prevents unsolicited incoming traffic though. Not sure about AT&T LTE.