An anonymous reader writes "Texas Instruments' most recent, ARM-based series of graphing calculators, the TI-Nspire line, has long resisted users' efforts to run their own software. (Unlike other TI calculator models, which can be programmed either in BASIC, C, or assembly language, the Nspire only supports an extremely limited form of BASIC.) A bug in the Nspire's OS was recently discovered, however, which can be exploited to execute arbitrary machine code. Now the first version of a tool called Ndless has been released, enabling users, for the first time, to write and run their own C and assembly programs on the device. This opens up exciting new possibilities for these devices, which are extremely powerful compared to TI's other calculator offerings, but (thanks to the built-in software's limitations) have hitherto been largely ignored by the calculator programming community."

distantbody writes "The flight sim project FlightGear has reached version 2.0. From the website: 'Highlights of this new version include: Dramatic new 3D clouds, dramatic lighting conditions, improved support for custom scenery, and many many new and detailed aircraft models.' Full list of improvements here. And of course the screenshots. The release coincides with the release of SimGear v2, the 'set of open-source libraries designed to be used as building blocks for quickly assembling 3d simulations, games, and visualization applications' on which FlightGear is based."

Several sources are reporting on a new metric that computer scientists are going after with respect to recommender systems — recommendation diversity. "In a paper that will be released by PNAS, a group of scientists are pushing the limits of recommendation systems, creating new algorithms that will make more tangential recommendations to users, which can help expand their interests, which will increase the longevity and utility of the recommendation system itself. Accuracy has long been the most prized measurement in recommending content, like movies, links, or music. However, computer scientists note that this type of system can narrow the field of interest for each user the more it is used. Improved accuracy can result in a strong filtering based on a user's interests, until the system can only recommend a small subset of all the content it has to offer."

Trailrunner7 writes "SQL injection has become perhaps the most widely used technique for compromising Web applications, thanks to both its relative simplicity and high success rate. It's not often that outsiders get a look at the way these attacks work, but a well-known researcher is providing just that. Rafal Los showed a skeptical group of executives just how quickly he could compromise one of their sites using SQL injection, and in the process found that the site had already been hacked and was serving the Zeus Trojan to visitors." Los's original blog post has more and better illustrations, too.

darthcamaro writes "Remember Mozilla Ubiquity? It was an effort to bring natural language commands to the Firefox browser. Now after almost two years of development and a half million downloads, the project is no longer being actively developed. Project founder Aza Raskin is now working on other projects, including Mozilla Jetpack, so Ubiquity is on the back burner. '"There is huge demand for being able to connect the Web with language — to not have to move from one site to another to complete your daily tasks," Raskin said. "And there is huge demand for anyone to be able to write small snippets of code that lets them command the Web the way they want. Ubiquity gave everyday developers a voice with how the browser and the Web works."'"

snydeq writes "Fatal Exception's Neil McAllister writes about the no-win scenario facing today's independent programmers: 'In a knowledge economy, programmers rank among our most valuable workers, yet the current legal and regulatory climate makes a career as an independent software developer virtually a dead-end prospect.' Section 1706 of the 1986 Tax Reform Act, the hurdles and costs of obtaining health care for one's own family, a hostile legal climate in search of accountability for any defects in code — these harsh realities make it 'easy to see why software developers would give up on entrepreneurship. For many, the risks simply don't match the potential rewards. Better to keep their heads down, not rock the boat, and hope they can hang onto their jobs until retirement.' Great news for big software vendors, which will be 'ensured an endless supply of programmers desperate for the safe haven of a steady paycheck, predictable taxation, health benefits, and a shield from civil prosecution when their code turns up buggy. But where will the next Microsoft come from? A field that discourages self-reliance sends the message that the status quo is the highest goal.'"

angry tapir writes "PayPal will open an applications store this year where developers can offer their wares, the latest step in the company's multi-pronged strategy to deepen its relationship with external programmers. Developers have a big opportunity to offer applications for merchants and consumers that PayPal doesn't have the interest or resources to build itself, according to a PayPal official."

jjrff writes "Phoronix has a little piece about the future (or lack thereof) of OpenSolaris. It appears based on the current support lifecycle, OpenSolaris may be going away. There is a fun thread (read: mild flameage) on a ZFS list about it."

MyNoSQL has up an interview with Ryan King on how Twitter is transitioning to the Cassandra database. Here's some detailed background on Cassandra, which aims to "bring together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model." Before settling on Cassandra, the Twitter team looked into: "...HBase, Voldemort, MongoDB, MemcacheDB, Redis, Cassandra, HyperTable, and probably some others I'm forgetting. ... We're currently moving our largest (and most painful to maintain) table — the statuses table, which contains all tweets and retweets. ... Some side notes here about importing. We were originally trying to use the BinaryMemtable interface, but we actually found it to be too fast — it would saturate the backplane of our network. We've switched back to using the Thrift interface for bulk loading (and we still have to throttle it). The whole process takes about a week now. With infinite network bandwidth we could do it in about 7 hours on our current cluster." Relatedly, an anonymous reader notes that the upcoming NoSQL Live conference, which will take place in Boston March 11th, has announced their lineup of speakers and panelists including Ryan King and folks from LinkedIn, StumbleUpon, and Rackspace.

thatpythonguy writes "Learning Python is a well-written book by an experienced Python trainer that has served the Python community well since the first edition was published in 1999. Now, at its fourth edition, this book by Mark Lutz arguably continues to be Python's bible." Read on for the rest of Ahmed's review.

Esther Schindler writes "It's easy for techies to enumerate the reasons that Internet Explorer 6 should die. Although the percentage of users who use IE6 has dropped to about 12%, many web developers are forced to make sure their websites work with the ancient browser (which presents additional problems, such as keeping their companies from upgrading to newer versions of Windows). But rather than indulge in an emotional rant, in 'Why You Can't Pry IE6 Out Of Their Cold Dead Hands,' I set about to find out why the companies that remain standardized on IE6 haven't upgraded (never mind to what). In short: user and business-owner ignorance and/or disinterest in new technology; being stuck with a critical business app that relies on IE6; finding a budget to update internal IE6 apps that will work the same as they used to; and keeping users away from newer Web 2.0 sites."

Niris writes "I'm currently taking a course called Advanced Java Programming, which is using the text book Absolute Java, 4th edition, by Walter Savitch. As I work at night as a security guard in the middle of nowhere, I've had enough time to read through the entire course part of the book, finish all eleven chapter quizzes, and do all of the assignments within a month, so all that's left is a group assignment that won't be ready until late April. I'm trying to figure out what else to read that's Java related aside from the usual 'This is how to create a tree. This is recursion. This is how to implement an interface and make an anonymous object,' and wanted to see what Slashdotters have to suggest. So far I'm looking at reading Beginning Algorithms, by Simon Harris and James Ross."

Dotnaught writes "Photoshop co-creator Russell Brown asked Ansca Mobile to re-create Photoshop 1.0, originally introduced in 1990, for the iPhone. The resulting app, created in three days using the Corona SDK, was distributed to 50 attendees of an event celebrating Photoshop's 20th anniversary. Programmer Evan Kirchhoff in a blog post explains that Ansca took the project on to prove its claims about how Corona makes iPhone development faster."

Kelson writes "Have you noticed that there haven't been many updates to Gears in a while? That's because Google has decided to focus instead on similar capabilities in the emerging HTML5 standard: local storage, database, workers and location cover similar functionality, but natively in the web browser. Of course, since Gears and HTML APIs aren't exactly the same, it's not a simple drop-in replacement, so they'll continue supporting the current version of Gears in Firefox and Internet Explorer. I guess this means the long-anticipated Gears support for 64-bit Firefox on Linux and Opera are moot."

BeardedChimp writes "I, like many others here, have learned to program by myself. Starting at a young age and learning through fiddling I have taught myself C++, Java, python, PHP, etc., but what I want to know is what I haven't learned that is important when taught in a traditional computer science curriculum. I have a degree in physics, so I'm not averse to math. What books, websites, or resources would you recommend to fill in the gaps?"

Hugh Pickens writes "The Register reports that experts from some 30 organizations worldwide have compiled 2010's list of the 25 most dangerous programming errors along with a novel way to prevent them: by drafting contracts that hold developers responsible when bugs creep into applications. The 25 flaws are the cause of almost every major cyber attack in recent history, including the ones that recently struck Google and 33 other large companies, as well as breaches suffered by military systems and millions of small business and home users. The top 25 entries are prioritized using inputs from over 20 different organizations, who evaluated each weakness based on prevalence and importance. Interestingly enough the classic buffer overflow ranked 3rd in the list while Cross-site Scripting and SQL Injection are considered the 1-2 punch of security weaknesses in 2010. Security experts say business customers have the means to foster safer products by demanding that vendors follow common-sense safety measures such as verifying that all team members successfully clear a background investigation and be trained in secure programming techniques. 'As a customer, you have the power to influence vendors to provide more secure products by letting them know that security is important to you,' the introduction to the list states and includes a draft contract with the terms customers should request to enable buyers of custom software to make code writers responsible for checking the code and for fixing security flaws before software is delivered."

Ian Lamont writes "InfoWorld has an interesting analysis of the reasons behind the relative dearth of programmers over the age of 40. While some people may assume that the recession has provided a handy cover for age discrimination, a closer look suggests that it's the nature of IT itself to push its elderly workers out, in what the article describes as a 'Logan's Run'-like marketplace. A bunch of factors are listed as reasons, including management's misunderstanding of the ways in which developers work: 'Any developer can tell you that not all C or PHP or Java programmers are created equal; some are vastly more productive or creative. However, unless or until there is a way to explicitly demonstrate the productivity differential between a good programmer and a mediocre one, inexperienced or nontechnical hiring managers tend to look at resumes with an eye for youth, under the "more bang for the buck" theory. Cheaper young 'uns will work longer hours and produce more code. The very concept of viewing experience as an asset for raising productivity is a non-factor — much to the detriment of the developer workplace.'"

An anonymous reader writes "A couple of times in my career, I've inherited a fairly large (30-40 thousand lines) collection of code. The original authors knew it because they wrote it; I didn't, and I don't. I spend a huge amount of time finding the right place to make a change, far more than I do changing anything. How would you learn such a big hunk of code? And how discouraged should I be that I can't seem to 'get' this code as well as the original developers?"

Precision writes to inform us about the Swiss firm Myriad, which claims a 3x boost in Android app performance and longer battery life with a new virtual machine. Myriad says that its technology is 100% compatible with existing Android apps. "The tool is a replacement for the Dalvik virtual machine, which ships as part of the Android platform, and retains full compatibility with existing software. Dalvik Turbo also supports a range of processors including those based on ARM, Intel Atom, and MIPS Architectures."

itwbennett writes "It can take a fairly stable team of programmers as long as six months to get to a point where they're estimating programming time fairly close to actuals, says Suvro Upadhyaya, a Senior Software Engineer at Oracle. Accurately estimating programming time is a process of defining limitations, he says. The programmers' experience, domain knowledge, and speed vs. quality all come into play, and it is highly dependent upon the culture of the team/organization. Upadhyaya uses Scrum to estimate programming time. How do you do it?"