Forgot your password?

Comment: Re:straight from the OMFG NO dept (Score 1) 364

by dottrap (#47740587) Attached to: "MythBusters" Drops Kari Byron, Grant Imahara, Tory Belleci

But is the ratings decline reflective of revenue or an overall problem with the show? Over the past 10 years, television viewership has been falling in general, losing out to other forms of entertainment.

However, the irony is that the cost for advertising in television is at an all time premium. This is because there is still no other advertising outlet that can capture such a wide audience at the same time with and also with well understood demographics.

Comment: Re:Registers vs. pointer size (Score 1) 73

by dottrap (#47103281) Attached to: Chrome 35 Launches With New APIs and JavaScript Features

The op complaint was no 64-bit Firefox for Mac. Apple doesn't do x32, so it's not even an option.

Data starvation can be mitigated/manually controlled in 64-bit by understanding your data. High performance code utilizes contiguous blocks of memory and is very aware of data layout, and isn't going to be pointer chasing. So allocating arrays of types that use int32_t instead of int64_t is a trivial example. So in a 64-bit architecture, you still generally win performance-wise.

x32 failed for a lot of reasons.
From the article you cited, here's a quote:
"they just really don't see the [x32] ABI as being worthwhile ... to make maintaining an extra ABI worthwhile."

As the quote highlights, the real crux of the problem is how much of a pain it is to maintain yet another ABI.
The performance differences for x32 didn't justify it over true 64-bit. That means the data starvation due to larger pointer sizes wasn't the dominating factor. So going from i386 to x32 vs. i386 to x64, the latter wins because it gets the speed of more registers, negligible performance impact for pointer size differences, and the plus of large addressable memory if you need it.

To show the pain of another ABI, here is a simplified example: You are using a video editor in GNOME under x32. You suddenly need more than 4GB of addressable memory. That means you needs a x64 version. But then you need a GNOME that is also built as x64, so you have to load up an entirely separate instance of GNOME, all its dependencies, and the video editor. Either you need to shutdown your current environment and reboot another, or you need to load both simultaneously. (This is what happens now when you load 32-bit i386 on modern Mac, hence a large RAM hit, not to mention that every binary also takes double the disk space.)

Comment: Re:meh (Score 1) 73

by dottrap (#47054209) Attached to: Chrome 35 Launches With New APIs and JavaScript Features

how about bloody 64bit on mac.?

Chrome was one of the first popular web browsers to use a separate process per tab. This architecture makes 64-bit less necessary because each tab is expected to use less than 2 GB of RAM.

It's not about addressable memory space.

64-bit usually yields better performance due to more registers and the fact that i386 was a register starved architecture.

But more importantly, everything on modern Mac is now 64-bit. Anything that is 32-bit must load in a 32-bit version of every shared system library that the application touches. At a minimum, Firefox would have to load in the entire 32-bit version of the Cocoa frameworks (because Firefox needs to at least create a native window). If Firefox is the only 32-bit app resident on your system (which is highly likely today), then it's wasting gobs of your system RAM and probably making you swap to disk more.

Comment: A peek inside the IETF corruption: Zeroconf (Score 1) 103

by dottrap (#46745199) Attached to: Why the IETF Isn't Working

Simply stating "Corporatization" is a massive mischaracterization and oversimplification of describing the situation.
Here is a peek in history from 2005 on the IETF mailing list itself and how IETF tried to sabotage the ratification of Zeroconf (Apple's Bonjour is the best known implementation of the Zeroconf protocol). This isn't simply "Corporatization" as both Apple and Microsoft are fighting and some in the the IETF actively trying to undermine it under the guise of simply offering alternatives (that nobody wants or plans to implement and is broken by design).

Stuart Cheshire is the creator of Zeroconf and calls them out directly on the IETF mailing list in 2005.

Comment: Washington Monument Syndrome (Score 0) 185

by dottrap (#46471429) Attached to: Mars Rover Opportunity Faces New Threat: Budget Ax

This is a clear case of Washington Monument Syndrome.

Threaten the most visible/popular projects to get more money.

Congress Makes NASA Finish Useless $350 Million Structure

Government Blatantly Wastes $30 Billion This Year (NASA appears 3 times)

Comment: It isn't. (Score 2) 487

by dottrap (#46393181) Attached to: Android Beats iOS As the Top Tablet OS

From Wikipedia:
"OHA [Open Handset Alliance] members are contractually forbidden from producing devices that are based off incompatible forks of Android."

This has a chilling effect on hiring manufacturers to build your actual device when most of them are already tied to OHA.

This is a perverse definition of "open".

Comment: Bravo, but what's with this "likely" nonsense? (Score 1) 345

by dottrap (#45710173) Attached to: Judge: NSA Phone Program Likely Unconstitutional

What's with this "likely" adjective crap? Did the judge actual use that adjective or did the media add that word? (I did RTFA.) The article quotes are forceful.

So what's with this with "likely" BS? Nobody ever says breaking into somebody's home without permission and stealing stuff is "likely illegal". What's with the double standard?

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (8) I'm on the committee and I *still* don't know what the hell #pragma is for.