SubLevel writes "Since conception in 2004, Paint.NET has been generously been offering the software community the taste of successful freeware, by allowing anyone to download and decipher the entire working of their extremely popular photo editing program. As posted in the Official Paint.NET blog by Rick Brewster, "Backspaceware" as he has so coined has become a tremendous issue. "Paint.NET's license is very generous, and I even release the source code. All free of charge. Unfortunately it gets taken advantage of every once in awhile by scum who are trying to profit from the work of others. I like to call this backspaceware*. They download the source code for something, load it up in to Visual Studio (or whatever), hit the backspace key over the software's name and credits, type in a new name and author, and re-release it. They send it to all the download mirror sites, and don't always do a good job covering up their tracks.""

DeeQ writes with a link to a post on News.com's social networking blog. Author Caroline McCarthy wonders if Google's OpenSocial initiative has missed its moment in the sun. It's been something like six weeks now since the search giant offered up its open-source social media initiative ... but where have been the usual swift victories? Moreover, OpenSocial isn't done yet, and it's not expected until sometime next year. In the meantime Facebook is capitalizing on Google's delay, and other networks are stepping in as well. "Kraus adds that some of the independent platform strategies would be necessary even if OpenSocial were finalized. One of them is LinkedIn's 'InApps,' which also aims to spread LinkedIn's data and influence outside the business-oriented social network through partnerships with other Web sites. 'OpenSocial so far is really about how developers embed their application into a social network,' Kraus explained. 'A good chunk of LinkedIn's APIs is about how LinkedIn extends their social-networking data into other sites.'"

narramissic writes "Google's Android may be getting all the headlines, but the venerable LiPS (Linux Phone Standards Forum), which launched to much fanfare in 2005, is rolling out the specs. The group, comprised of companies including Orange, France Telecom, MontaVista, and Access, announced Monday that it has completed the first release of its mobile Linux specification, adding components including APIs for telephony, messaging, calendar, instant messaging, and presence functions, as well as new user interface components."

jg21 writes "This AJAXWorld Magazine article indicates how far AJAX has come since devs complained here two years ago that it sucked all the time. Eight experts were asked what questions we should now all be asking about where AJAX is headed next. The suggested questions are refreshingly hard-headed, including: 'How are we to fix the web?'; 'When will AJAX development finally be easy?'; and 'Do we really need JavaScript 2.0? Won't it be somewhat irrelevant by the time it becomes commonplace and thus usable?' One of the most interesting questions came from Kevin Hakman, co-founder of TIBCO's General Interface: 'On what timeline will AJAX skills become commoditized like HTML skills became?'"

An anonymous reader writes "I am downright embarrassed by the quality of my code. It is buggy, slow, fragile, and a nightmare to maintain. Do you feel the same way? If so, then what is holding you back from realizing your full potential? More importantly, what if anything are you planning to do about it? I enjoy programming and have from a young age (cut my teeth on BASIC on an Apple IIe). I have worked for companies large and small in a variety of languages and platforms. Sadly the one constant in my career is that I am assigned to projects that drift, seemingly aimlessly, from inception to a point where the client runs out of funding. Have any developers here successfully lobbied their company to stop or cut back on 'cowboy coding' and adopt best practices? Has anyone convinced their superiors that the customer isn't always right and saying no once in awhile is the best course of action?"

Jamie noted that ruby on rails 2.0 is done. In addition to upgrade and installation instructions, the article lists a number of the more interesting new features in the release which appears to be quite extensive.

NewsCloud writes "Last week, Facebook quietly removed sign-in restrictions that previously hid third party applications from the public Web. In other words, Facebook now allows its third party applications to be viewable on the Web by anonymous visitors and indexable by search engines. Web developers can now build an application using Facebook's platform usable by anyone on the Internet — not just Facebook members (e.g. the Lending Library). In doing so, developers can leverage Facebook's login and registration as well its other platform services, which are becoming increasingly substantial. Facebook may be trying to gain advantage as a universal authentication gateway for public Web applications. If successful, it could further hamper efforts to establish OpenID. This will also help the company break out of its earlier AOL-like walled-garden strategy."

chromatic writes "Larry Wall's State of the Onion 11 address is now online. Every year, he describes the state of Perl and its community through metaphor and analogy. This year, Larry explored the history of scripting languages, from their dimly-lit beginnings to their glorious future. Along the way, he also describes several of the design principles invoked in the design of Perl 6. 'When I was a RSTS programmer on a PDP-11, I certainly treated BASIC as a scripting language, at least in terms of rapid prototyping and process control. I'm sure it warped my brain forever. Perl's statement modifiers are straight out of BASIC/PLUS. It even had some cute sigils on the ends of its variables to distinguish string and integer from floating point. But you could do extreme programming. In fact, I had a college buddy I did pair programming with. We took a compiler writing class together and studied all that fancy stuff from the dragon book.'"

Lucas123 writes "Computer World is running a piece on Crowdsourcing. That's a catchy term for the practice of taking a job traditionally performed by employees or a contracted company and outsourcing it to an undefined, large group of people in the form of an open call on the Web. Article author Mary Brandel views it as a viable way to develop cheap but innovative software. Sites like TopCoder and their coding competitions are becoming more popular with big name companies like Constellation Energy because programmers who take on the job are global, offering many different perspectives on any one job. 'The creativity and innovation of how people are rationalizing these designs and building components enables us to interject a perspective and approach that normally we wouldn't have access to,' Constellation's director of IT said." Is there any potential here, or is this just a buzzword bad idea?

An anonymous reader writes "In an effort to keep up with changes from Apple at a faster speed, the iPhone Dev Team is considering open sourcing AnySIM, the free unlocking solution for the iPhone. In a chat with Gizmodo, iPhone Dev Team member Sam said that this move could 'open a lot of possibilities for the future,' mainly in terms of the speed of the updates and avoiding sloppy and possibly dangerous binary patches. They are now looking for community input to get the project started."

Bogtha writes "Long-time users of Perl for their public websites, and having successfully used Ruby on Rails for internal websites, the BBC have fused the two by creating a 'Perl on Rails' that has the advantages of rapid development that Rails brings, while performing well enough to be used for the Beeb's high-traffic public websites. This is already powering one of their websites, and is set to be used in the controversial iPlayer project as well."

The time-honored tradition of code scavanging has long been a way for new programmers to "break in" to a new language or task that they may not want to build from the ground up. The re-use of old code, cleaned up and tweaked to a new purpose can help developers learn many useful skills and accomplish tasks quickly, especially for small tasks that aren't of vital importance. One blogger wondered if this process could be formalized and tools could be built to help foster and enable code scavanging on a mass level. Is this a viable option, or are there just too many things to consider?

jg21 writes "Via the Web 2.0 Journal, a worthy link to Yahoo! Architect and JSON inventor Douglas Crockford's latest ideas to fix HTML. He's categorically not a fan of HTML 5, which is still just an Editor's Draft and not endorsed by W3C yet. Crock puts forward ten ideas that in his view would provide extensibility without complexity, adding that the simplification of HTML he is proposing would reduce the cost of training of web developers and incorporates the best practices of AJAX development. From the article: 'The problems with HTML will not be solved by making it bigger and more complicated. I think instead we should generalize what it does well, while excising features that are problematic. HTML can be made into a general application delivery format without disrupting its original role as a document format.'"

greenrom writes "I work for a small company as a software developer. While investigating a bug in one of our products, I found source code on a website that was nearly identical to code used in our product. Even the comments were the same. It's obvious that a developer at our company found some useful code on the web and copied it. The original author didn't attach any particular license to the code. It's just 200 lines of code the author posted in a forum. Is it legitimate to use source code that's publicly available but doesn't fall under any particular license? If not, what's the best way to deal with this kind of situation? Since I'm now the only person working on this code, there's no practical way to report the situation confidentially. I'm new to the company, and the developer who copied the code is the project lead. Reporting him to management doesn't seem like a good career move. I could rewrite the copied code without reporting him, but since the product is very close to release it would be difficult to make a significant change without providing some justification."

phobonetik writes "Building on three successful years of engaging University students with over one hundred open source projects, the Google Summer of Code program is being complemented with the Google Highly Open Participation Contest, launched today. Running initially as a pilot involving 10 open source projects, the contest is open to any student enrolled in highschool education. Students choose from a list of several hundred predetermined tasks that improve the open source project, and get paid small sums for their successful completion. At the end of the contest (4th Feb 2008), each of the ten open source projects nominate their best contributor, who wins a grand prize." I wish there would have been something like this when I was in high school... I wonder how great my BBS door games would have been if there was a chance of getting cash and trips.

LarsWestergren writes "Many Mac users have been upset that Apple has not made Java 6 available on the platform. Landon Fuller posts that there is a developer preview release available of Java JDK6 on Mac OSX, Tiger and Leopard. It is based on the BSD port of Sun's Java 6 and is made available under the Java Research License. Charles Nutter posts about impressive JRuby performance gains using Java 6 on his Mac."

Jamie found a fun story about a 90s Zelda Game Boy ROM that shipped with the source code- not so much on purpose, but more because the linker padded out the last meg of ROM with random memory contents, which happened to include game source code.

mcwop writes "Early this morning Maryland passed legislation to apply a new 6% sales tax to 'custom computer programming' and other computer- and hardware-related services. Computer industry groups lobbied hard against the measure to no avail. Purchasers of IT services may find that in-house IT and buying out-of-state become attractive options, as well as cutting money out of other projects."

narramissic writes "There may be trouble brewing between Google and Sun. Google has written its own virtual machine for Android, 'most likely as a way to get around licensing issues with Sun.' If Google used any of Sun's intellectual property to build Dalvik, Sun could sue Google for patent infringement. But here's where it gets interesting - Sun is a vocal advocate for open source and it would 'hardly appease the open source community to sue Google over an open source software stack.'"

petrus.burdigala writes "I work for a mid-sized commercial software company (~20 Mloc) and we are frequently challenged by our supervisors to get fixes around the clock. Overall, we manage to get a 'bullet-proof' patch in about 4-5 weeks (from coding->QA->Build/Packaging->shipment), which I consider not so bad. But the other day, we got an urgent request from our support team to come up with a decent fix in 48 hours. I think they're a tiny bit unrealistic. So I wanted to get feedback from my peers: are we doing that bad? It takes months for other software vendors to issue zero-day exploit fixes, are our customers being unreasonable?"