|
|
|
| | 02/10/10 |  |
|
|
|
prourl writes "The Linux Foundation (LF), the nonprofit organization dedicated to accelerating the growth of Linux, today announced the 2010 'We're Linux' video contest. The contest seeks to find the best user-generated videos that demonstrate what Linux means to those who use it and inspire others to try it." Sadly, the winner will almost certainly be edited in Final Cut Pro on a Mac ;)
|
| | 12/02/09 | |
|
|
|
| | 11/30/09 | |
|
|
|
CNET's Crave has up a detailed interview with Last.fm's Matthew Ogle, the company's head of Web development. Reader CNETNate notes that Last.fm has streamed 275,000 years of audio around the world. From the interview: "We stream all music directly off our servers in London. We have a cluster of streaming nodes including a bunch of powerful machines with solid-state hard drives. We have a process that runs daily which finds the hottest music and pushes those tracks on to the SSDs streamers that sit in front of our regular platter-based streaming machines. That way, if someone is listening to one of our more popular stations, the chances are really good that these songs are coming off our high-speed SSD machines. They're fast because every song is sitting in memory instead of being on a slow, spinning platter." The interview is actually on two pages but pretends it's on three.
|
| | 11/09/09 | |
|
|
|
halfEvilTech writes 'Five years ago today, Mozilla released Firefox 1.0. Ars celebrates the occasion by taking a trip back in time to revisit our classic coverage of the original release.' For fun we dug up the oldest Slashdot Firefox story which was a firebird story proclaiming yet another name change from Feb 04. At least this name change stuck.
|
| | 07/21/09 | |
|
|
|
LinuxScribe tips a piece up at Linux.com with inside details on the design and construction of the Apollo 11 code. There are some analogies to open source development but they are slim. MIT drafted the code — to run on the Apollo Guidance Computer, a device with less grunt than an IBM XT — it had 2K of memory and a 1-MHz clock speed. It was an amazing machine for its time. NASA engineers tested, polished, simulated, and refined the code. "The software was programmed on IBM punch cards. They had 80-columns and were 'assembled' to instruction binary on mainframes... and it took hours. ... During the mission, most of the software code couldn't be changed because it was hard-coded into the hardware, like ROM today... But during pre-launch design simulations, problems that came up in the code could sometimes be finessed by... computer engineers using a small amount of erasable memory that was available for the programs. The software used a low-level assembly language and was controlled using pairs or segments of numbers entered into a square-shaped, numeric-only keyboard called a Display and Keyboard Unit... The two-digit codes stood for 'nouns' or 'verbs,' and were used to enter commands or data, such as spacecraft docking angles or time spans for operations." Reader Smark adds, "The Google Code Blog announced today that the Virtual AGC and AGS project has transcribed the Command Module and Lunar Excursion Module code used during the Apollo 11 moon landing. The code is viewable at the VirtualAGC Google Code Page."
|
More news...
|
Welcome to NeoSystem.
