potkor

There's supposed to be native Optimus support in the latest drivers. Ubuntu is aiming to support it for 13.10 (and backport to LTS), see https://wiki.ubuntu.com/X/HybridGraphics

Let's hope it works out. There are still some showstopper bugs like suspend not working and touchpad locking up.

Bumblebee was always a stopgap and a kludge - and a lot of credit is due for the enterprising bumblebee hackers.

That's single threaded compositing on its own thread.

Nvidia software has always been much better than AMD. AMD on Linux is a complet disaster. So if you work on GPU it's natural to go Nvidia.

What Krugman said here applies to the EU too (infact he's basing it on IMF research using global data):

http://krugman.blogs.nytimes.com/2010/08/12/the-price- stability-trap/

"in the modern world, rapid deflation doesn’t happen, and in fact slight positive inflation often persists in the face of an obviously depressed economy"

Triple Town. It's great though it's freemium (150 turns/day limit).

Most people's "true public IP address" is just as pseudonymous though.

It was not well known (before this came out last month) that putting an unlocked Android phone in the freezer lets you pull off a practical cold boot attack for the flash crypto keys.

Here's previous discussion: http://news.ycombinator.com/item?id=5231454

Maybe stop the whole thing about "let's pretend common nth level domain signifies something about web page relatioships"? It's just baseless.

Generally you start with Python and 1) get the code correct (hardest part) and then 2) port the performance critical parts to C/C++. So even they ended up with 0% in Python, it wouldn't "look bad". You got the benefit in part 1.

(And as others have said, 17% of LOC in Python might still mean majority of the functionality in Python).

You have it the wrong way around. People who cordon themselves off and only leave HTTP working aren't on the Internet.

They don't want non-web apps to work. Those networks deliberately rule out networked games, uTP, VoIP, IPsec, WebRTC, etc.

If you want to worry about people teetering on the edge of the Internet, you should worry about people behind NAT and its prevalence to the point of people confusing NAT boxes and routers...

(Re your last sentence, it's not a UDP replacement, see other comments.)

So like others have pointed out, this is not aiming to replace UDP any more than HTTP is aiming to replace TCP. So it's more like a feature rich TCP replacement, a transport protocol that happens to sit on top of UDP (which is what you have to do unless you want to write a OS driver).

As for impact, depends entirely what applications they plan to deploy it on. WebSockets, peer-to-peer WebRTC and media streaming could benefit from real-time friendly properties (fixing head-of-line blocking and enabling selectively unreliable packets). Hard to see anything significant for traditional web content delivery.

There are many things that you might want from a post-TCP transport protocol. Look at some of the SCTP features for a taste. It has stream multiplexing over the single connection, multipath and dynamic address changes, datagram mode, per-message reliable/unreliable option, to name a few.

SCTP seems to have bombed partly because they were "doing it right", ie getting their own IP protocol number and trying to get it deployed inside OS IP stacks instead of of sitting at application level on top of UDP.

The FEC feature in QUIC sounds a little unorthodox unless it's for multicasting or some control plane function, since at this protocol layer it's considered prudent to be sensitive to congestion when coping with packet loss...

People go completely irrational about avoiding writes to SSD's, I've seen researchers at an EE dept spending evenings tuning their Windows installations and going as far as stuffing frequently used stuff onto a RAM disk.

I guess the early off brand SSD's randomly eating your data didn't help the popular perception (even though that wasn't because of flash wear). But still...

This paper from 2011 compares autovectorization in GCC against two proprietary compilers, from Intel and IBM: http://polaris.cs.uiuc.edu/~garzaran/doc/pact11.pdf

GCC got a 23% speedup vs 15% for XLC and 28% for ICC. GCC did well considering the proprietary compilers' narrow focus and corporate resources.

BTW, Fortran compilers for the 1980's supers did autovectorization pretty well. Funny that we've made it so hard today.

> It will probably take another 30 years before you can actually think like a human and perform optimizations like this.

ITYM "It will probably take another 30 years before I use a language that tells you what the required semantics of the code are, meanwhile I'll use my requirements interpretation privileges to relax the semantics in a few places"

They've been able to port various Windows-centric products to other platforms before (to Mac and Solaris at least). Exchange, Office, Internet Explorer etc.

I agree they won't make a huge profit from it directly but I bet it's a good counter-argument to "let's standardise on OpenOffice since otherwise we are subject to MS vendor lock-in". A couple of big government or corporate deals should cover the costs.

Fortunately that kind of wiretapping is a crime in most of the civilized world, finance sector employer or not.

If you read the linked Washington Times article, the "monitoring centers" sound like separatete bells-and-whistles products that are not the same as the mandated LI mechanisms.

Lots of other vendors market these government espionage tools to autocratic regimes too. Eg Bluecoat, Cisco etc.

At any rate it feels bad that we have to appeal to these human rights abusing autocracies, it's not any better to have these mechanisms built into the western networks.

Does this also apply to end-users of Ruby apps that are just an apt-get away? I don't really want to learn all that stuff (and remember to redo it on all installs) just to use some tool that happens to be written in Ruby.

In practice Itanium only competed with the existing 64-bit architectures from the Unix vendors. Many of whom got suckered into dropping their own stuff and moving onto Itanium, and got wiped out because of the very late & underperforming Itanium chips (frequently called "Itanic")...

Intel chips have supported it pretty soon after AMD, since the latter-day Pentium 4s (from 2004 on).

32-bit Windows (with the 2GB limit) couldn't run the 64-bit Firefox in any case, so in the context of this discussion the 32-bit build is always getting 4GB of address space.

Yes, its triumph over the Java Desktop has been impressive.

Desktop hardware has been 64-bit since the 2003 Athlon 64, 2004 Pentium 4 and 2003 PowerPC G5. Servers 10 years+ earlier(X). I guess 9+ years on the desktop is "not too long" if your beard is long enough :)

X) http://en.wikipedia.org/wiki/64-bit#64-bit_processor_timelin...

Latest spin from the .fi copyright mafia is "this demonstrates how we need legislation enabling softer measures for enforcement", cue 3 strikes etc badness.

When they last revised the criminal law wrt copyright. It's actually a triply evil twist. First (1) new law says that only for the criminal form can you get jail time, and you need to be making a profit to turn it from a minor offense to a crime. Then (2) they the added in the last paragraph of the relevant section that if a computer network is involved and there's "significant damage" to the rightholder, it's also the criminal form. And then (3) the courts made it the sentencing practice that it's "significant damage" even in cases like this.

link (finnish):http://www.finlex.fi/fi/laki/ajantasa/1889/18890039001#e-53 chapter 49 last paragraph

Interesting that there are still shrink-wrapped software packages that cost a lot. In fact you could buy a dedicated computer to run just that for some of the prices and it wouldn't make a big difference in cost.

Wonder what other apps like this are left that have a wide audience, excluding "enterprise" stuff? I guess Microsoft Office is one.

Not mentioned in this article, but the Android compatiblity might be a big thing.

Mostly everything except Flash and proprietary games.

You have to wade pretty far until this gets to the main user-visible advantage (global routability) and doesn't make a very compelling case of why you'd want it.

People have been lulled into this state of apathy about crippled IPv4+NAT connectivity (or don't know any better). The problem is that the network effect/chilling effect wrt app deployment/development isn't something that a user instantly sees, and the other, more immediate benefits are currently only significant for pretty advanced users (who are already aware of how NAT makes their lives hard).

Cortex-A15 and Apple A6 are the high-end now. Cortex-A9's are so small and (relatively) cheap that they throw 4 of them on $20 tablet SoCs even for applications that don't really benefit from many cores.