Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×

Comment General-purpose OS for a camera (Score 1) 179

A decade ago, there was a small series of digital cameras that ran a somewhat-open OS: Slashdot covered DigitaOS before. Yes, some people ran games on their cameras; I was one. But more importantly, new applications could be developed. Long before EXIF and geotagging, there was a guy with a GPS hooked to the serial port (yes, back when cameras used RS232) of a camera, and a Digita program to save the coordinates where each shot was taken. There are countless new ideas waiting to happen, when an open OS is paired with serious optics. I can't wait.

Comment Hackerspace connections (Score 5, Interesting) 239

I got my current job because another guy at the local hackerspace saw me working on stuff and figured I'd be a good fit at the place he worked. No big deal, makes sense, okay. But the sheer number of times this has happened, still astonishes me. With a membership of about 70 people, I can count 9 who've gotten jobs through connections made at the hackerspace. That's noteworthy.

Comment No chance of ruining the species... (Score 1, Flamebait) 1034

...recent Western culture has shown that a higher percentage of men have become fathers in the past few generations than before that.

As more and more males become adjusted to the instant high of popular culture, we'll just return to the times when a tinier percentage of men were having all the babies.

Marriage is already on a decline, in some races good husbands are hard to find so women have more biracial babies, and the powerful men won't stop spreading their seed.

Does it matter to me if the weak male class doesn't have kids? Hell no -- and they make good employees, too. Maybe better ones.

Comment Size of build != Size of executable (Score 2) 753

This is basic stuff to anyone who actually maintains a build, but Slashdot hasn't been a forum mostly populated by engineers for a number of years, now.

This appears to be due to link-time optimization blowing up the resident memory size of the linker, taking it past 3GB (which is already a non-standard hack the 32 bit build has had to do). Firefox is large, yes, but this has nothing to do with the final binary - which appears to be about 100MB total including all libraries in the Aurora builds.

I used to routinely run out of 32 bit address space compiling executables for a 64MB embedded ARM platform. This was due to symbol bloat, not executable size (which was 8MB). I also ran out of space compiling for a DSP with 288KB of RAM and 1MB flash, but that was mostly piss poor tools (Tasking). In fact, doesn't Chrome and even the Android sources already require building on a 64 bit host?

Firefox

Firefox Too Big To Link On 32-bit Windows 753

An anonymous reader writes "Firefox has gotten so large that it cannot be compiled with PGO on a 32-bit linker anymore, due to the virtual memory limitation of 3 GB. This problem had happened last year with 2 GB, which was worked around by adding a/3GB switch to the Windows build servers. Now the problem is back, and things aren't quite that simple anymore." This only affects the inbound branch, but from the looks of it new code is no longer being accepted until they can trim things from the build to make it work again. The long term solution is to build the 32-bit binaries on a 64-bit system.

Comment You're just repeating the "Theora sucks" meme (Score 1) 108

I don't have to explain:

Theora really can't even compete with MPEG-1 on either video quality at a given bitrate, or performance. It was very specifically designeed for extremely low quality, extremely low resolution, extremely low bitrate streaming video, over a decade ago...

This isn't true. There's plenty of results out there which say Theora is, while not the best, a good codec. To quote Wikipedia: More recently however, Xiph developers have compared the 1.1 Theora encoder to YouTube's H.264 and H.263+ encoders, in response to concerns raised in 2009 about Theora's inferior performance by Chris DiBona, a Google employee. They found the results from Theora to be nearly the same as YouTube's H.264 output, and much better than the H.263+ output.

There are plenty of people proclaiming that because it doesn't come out top, it's useless. Theora is far from useless: the results in any scenario that H.264 (even main profile) would be used, are still usable if you select Theora instead. They just aren't as pretty, because it's just not designed to the same constraints as H.264.

Becoming the HDTV standard would be an unrealistic goal. You attribute Theora not becoming the dominant standard due to Xiph's mishandling of the codec. The more obvious reason is politics: the MPEG group exists specifically to create audio/video standards which can be licensed. Broadcasters and content providers generally only use MPEG standards, and they just love licensing.

I'm interested to know what your theory is that Xiph could drive HDTV standards and have handled this better than a small company could?

Facebook

Facebook Releases JIT PHP Compiler 244

angry tapir writes, quoting a Techworld article: "In its continuing endeavor to serve its 800 million users as quickly as possible, Facebook is once again revamping the way it handles its PHP-based Web pages. Facebook has posted ... its HipHop Virtual Machine (HHVM), which the company's engineers call a just-in-time PHP compiler. According to Facebook, this PHP execution engine is 60 percent faster than its current PHP interpreter and uses 90 percent less memory." Facebook has a weblog post with a more technical description.
Businesses

The Rise and Fall of Kodak 352

H_Fisher writes "Michael Hiltzik of the L.A. Times writes with a frank look at the decisions and changes that have led to Kodak's decline from top U.S. photography company to a company whose product is almost irrelevant. He writes: '[Kodak] executives couldn't foresee a future in which film had no role in image capture at all, nor come to grips with the lower profit margins or faster competitive pace of high-tech industries.' He also notes that Kodak's story comes as a cautionary tale to giants like Google and Facebook."
Television

TV Isn't Broken, So Why Fix It? 839

PolygamousRanchKid sends this quote from a contentious article at CNN that questions the need for further development of TVs and the entire TV-viewing experience. "The technology industry is absolutely bent on reinventing television. ... But nobody seems to be able to answer the big question: what exactly is so broken about TV anyway? The tech industry is filled with engineers and geeks. They naturally want to optimize the TV experience, to make it as efficient and elegant as possible, requiring the fewest number of steps to complete a particular task while offering the greatest number of amazing new features. But normal people don't think about TV that way. TV is passive. The last thing we want to do is work at it. ... As long as there's something on — anything — that is reasonably engaging, we're cool. Most of us are even OK spending a few minutes just shuffling through channels at random." So, what do you think is broken about TV right now? Is there a point at which it'd be better for us to stand back and say "We've done what we can with this. Let's work on something else"?

Slashdot Top Deals

Beware of Programmers who carry screwdrivers. -- Leonard Brandwein

Working...