An anonymous reader writes "An article at Ars recaps a discussion from Stack Exchange about a software engineer who had the misfortune to inherit 200k lines of 'spaghetti code' cobbled together over the course of 10-20 years. A lengthy and detailed response walks through how best to proceed at development triage in the face of limited time and developer-power. From the article: 'Rigidity is (often) good. This is a controversial opinion, as rigidity is often seen as a force working against you. It's true for some phases of some projects. But once you see it as a structural support, a framework that takes away the guesswork, it greatly reduces the amount of wasted time and effort. Make it work for you, not against you. Rigidity = Process / Procedure. Software development needs good processes and procedures for exactly the same reasons that chemical plants or factories have manuals, procedures, drills, and emergency guidelines: preventing bad outcomes, increasing predictability, maximizing productivity... Rigidity comes in moderation, though!'"
angry tapir writes "SAP has agreed to pay Oracle US$306 million in connection with the corporate-theft case that Oracle filed against it and a former SAP subsidiary in 2007, according to a filing made Thursday in the U.S. District Court for the Northern District of California. The long-running legal dispute centers on illegal downloads of Oracle software and support materials by SAP subsidiary TomorrowNow, which offered lower-cost support services for Oracle software. SAP admitted liability for actions taken by TomorrowNow workers, and a jury awarded Oracle US$1.3 billion in damages in November 2010." The $1.3 billion fine was overturned shortly after, causing more months of litigation.
alstor writes "Yesterday an update to Knight Capital Group's algorithmic trading software caused massive volume buys and sells, resulting in large price swings on the New York Stock Exchange. As a result, the NYSE canceled some of the trades, but today the loss to Knight has been calculated at $440 million. Ignoring adjustments for inflation, this makes the cost of this glitch almost as much as the $475 million charge Intel took for the Pentium FDIV Bug, which might warrant adding this bug to the list of worst bugs. In light of this loss and the May 6, 2010 Flash Crash, perhaps investors will demand changes from firms using algorithmic trading, since the SEC is apparently too antiquated to do anything about it (PDF)."
angry tapir writes "A California court has ordered Oracle to continue porting its software to the Intel Itanium chips used by Hewlett-Packard in a number of its servers. Last year, Oracle, which competes with HP in the hardware market but shares many customers with the vendor, announced it would cease supporting Itanium. HP filed suit in June 2011, maintaining that Oracle was contractually bound to continue supporting Itanium."
An anonymous reader tips news that Google has sent out a letter to app developers explaining policy changes for any new apps published on the Google Play store. In-app purchases must now use Google Play's payment system unless it's for goods or services used outside the app itself. They've added language to dissuade developers from making their apps look like other apps, or like they come from other developers. But more significantly, Google has explained in detail what qualifies as spam: repetitive content, misleading product descriptions, gaming the rating system, affiliate traffic apps, or apps that send communications without user consent. Also, advertisements within apps must now follow the same rules as the app itself, and they can't be intrusive: Ads can't install things like shortcuts or icons without consent, they must notify the user of settings changes, they can't simulate notifications, and they can't request personal information to grant full app function.
CowboyRobot writes "Intuit launched QuickBooks in 1992, and it has grown into the best-selling retail software for small-business accounting worldwide. QuickBooks is available on multiple platforms with different feature sets (Pro, Premier, Enterprise), in specialized editions (accounting, contracting, etc.), is available on CD or via subscription, and is offered in localized versions for the U.S., Canada, and the U.K. How they manage so many builds is a case-study for large scale programming. 'The Windows version is about 80,000 source files, 10+ million lines of C++ code plus a little C# for the .NET parts. Plus help files, tax tables, files defining local accounting rules, tax and other government reporting forms, upgrade offers — a lot of files. Every customer gets the full version. Specific feature sets are turned on and off with the license key.' And the lessons are not just technical. 'One surprising lesson is that small teams work, even for very large codebases — especially, Burt says, in sustaining an entrepreneurial, creative culture.'"
Croakyvoice writes "A few years ago the Homebrew community went from one console to another releasing some excellent software, from the Days of the Dreamcast the first breakthrough homebrew console, to the PSP which gave us the first handheld Nintendo 64, GBA and PSX emulators on a handheld. The last few years we have seen Microsoft, Nintendo, Sony and Apple all bring out means to thwart homebrew development. The app store on both Android and iOS have taken many homebrew devs over to try and break the market. The major consoles have so many firmware updates that the days of Homebrew seem to be numbered, is there a way back for the Homebrew Community?"
Nerval's Lobster writes "For any software developers with an urge to play around with demographic or socio-economic data: the U.S. Census Bureau has launched an API for Web and mobile apps that can slice that statistical information in all sorts of nifty ways. The API draws data from two sets: the 2010 Census (statistics include population, age, sex, and race) and the 2006-2010 American Community Survey (offers information on education, income, occupation, commuting, and more). In theory, developers could use those datasets to analyze housing prices for a particular neighborhood, or gain insights into a city's employment cycles. The APIs include no information that could identify an individual."
An anonymous reader writes "Romero is willing to give Ouya the benefit of the doubt, but he sees it filling a niche for neither gamers nor developers. 'I think it's cool that they're making a platform, but it's not really the answer that's coming from Apple about the next generation of consoles. Developers really want to invoke the spirit of the Apple II, Android isn't the operating system with which to do it,' Romero said. 'There are two platforms: [iOS] makes money [and] is still very programmable, like the Apple II, and then the other is Android, which is a piracy platform, and you're not doing anything new with it.'"
McGruber writes "The Federal Times has the stunning (but not surprising) news that a new audit found six Defense Department modernization projects to be a combined $8 billion — or 110 percent — over budget. The projects are also suffering from years-long schedule delays. In 1998, work began on the Army's Logistics Modernization Program (LMP). In April 2010, the General Accounting Office issued a report titled 'Actions Needed to Improve Implementation of the Army Logistics Modernization Program' about the status of LMP. LMP is now scheduled to be fully deployed in September 2016, 12 years later than originally scheduled, and 18 years after development first began! (Development of the oft-maligned Duke Nukem Forever only took 15 years.)"
New submitter zixxt writes "GTK+ Developer Benjamin Otte talks about the stagnation and decline of the Gnome Project. He describes how core developers are leaving GNOME development, how GNOME is understaffed, why GNOME is a Red Hat project and why GNOME is losing market and mind share. Is the Gnome project on its deathbed? Quoting: 'I first noticed this in 2005 when Jeff Waugh gave his 10×10 talk. Back then, the GNOME project had essentially achieved what it set out to do: a working Free desktop environment. Since then, nobody has managed to set new goals for the project. In fact, these days GNOME describes itself as a “community that makes great software”, which is as nondescript as you can get for software development. The biggest problem with having no goals is that you can’t measure yourself. Nobody can say if GNOME 3 is better or worse than GNOME 2. There is no recognized metric anywhere. This also leads to frustration in lots of places.'"
geek writes "According to Marco Arment, the creator of Instapaper, Apple may be in trouble with developers. According to Arment, the new sandboxing guidelines from Apple are pushing developers away in droves. 'I've lost all confidence that the apps I buy in the App Store today will still be there next month or next year. The advantages of buying from the App Store are mostly gone now. My confidence in the App Store, as a customer, has evaporated. Next time I buy an app that’s available both in and out of the Store, I’ll probably choose to buy it directly from the vendor. And nearly everyone who’s been burned by sandboxing exclusions — not just the affected apps’ developers, but all of their customers — will make the same choice with their future purchases. To most of these customers, the App Store is no longer a reliable place to buy software.' Arment also comments on the 'our way or the highway' attitude Apple often takes in these situations and how it may be backfiring this time around."
As part of a KDE-wide effort to prepare for Qt 5/QtQuick2, and a push to improve the window manager, KWin now sports QML decoration support. Currently, the C++ API for decorators is "...not very Qt like and requires a strong understanding of how the window decoration in KWin works ... [and] seems to be too difficult to be used." This complexity increases maintenance burden: "In 4.9 we ship four window decorations: the Aurorae theme engine, Oxygen, Plastik, b2 and Laptop. Together they are 10 kSLOC of C++ code and 1 kSLOC QML code (Aurorae). Before Aurorae got ported to QML the size of the decorations was 13 kSLOC. Overall that is about 10 per cent of the KWin source base, which is rather large." Basing his work on the QML version of the Aurorae engine, Martin Gräßlin set out to port Plastik to QML (the C++ version has already bitrotted, and was slated for removal): "After one and a half days of work I’m proud to say that writing decorations in QML is possible. ... In the current state the decoration consists of 370 lines of QML code and I expect to need an additional 100 lines to finish the buttons (they are already functional, that is the close button closes the window) and add some of the configuration options. The same API in C++ consists of 1500 lines of code. So we do not only get fewer lines of code but also a more readable and easier to maintain codebase. For something like a window decoration a declarative approach is much better suited than the imperative C++ way of painting elements."
CowboyNeal writes "Last week, Oracle announced that they were making Oracle Linux available free of charge, and also provided a script that makes switching to Oracle Linux nearly painless for existing CentOS users. What makes Oracle Linux unique, and why would anyone want to use it? Read on to find out, as I delve into what Oracle Linux has to offer."