Comment Since we are always recipients of the code... (Score 1) 633
GPL protects the freedom of the many (the *recipients*),
since almost all *producers* are recipients of code for any used libs.
Submission + - Is JCP neccessary for the open-source JDK 7? (jroller.com)
sperxios10 writes: "When Jean-Marie Dautelle asked about Java Committee Process and How to make it better?,
Stephen Colebourne asked back: Is the JCP broken?.
Stephen based some of his assumptions on the controversy surrounding Java 7's modularization efforts and miss-communications of Sun with OSGi group. He initially suggested 5 remedies, such as "... a guarantee 20%, or maybe 25%, of seats to individuals", but eventually concluded:
Stephen based some of his assumptions on the controversy surrounding Java 7's modularization efforts and miss-communications of Sun with OSGi group. He initially suggested 5 remedies, such as "... a guarantee 20%, or maybe 25%, of seats to individuals", but eventually concluded:
The real solution would be to redefine Java as a core kernel, and an OSGi module system, with a central repository of modules that could be downloaded on demand. Vendors could then group together ad hoc to build new modules for everything from date-time to JSF. The market would then decide the winners. Thus the JCP would simply be the guardian of the language syntax and core libraries, an actually manageable task!
Does this proposal make any sense to you?"
Submission + - Futures market for gaming can help the industry
An anonymous reader writes: A futures market for gaming has opened to predict the success of console hardware and games software. For gamers, this plays like fantasy football for video games in which you compete with friends or the world in your picks for a portfolio of game stocks.
For the video game industry, the simExchange can be much more. 1UP says: "Futures markets are (natch) eerily prescient when it comes to divining the future, and there isn't a company out there who wouldn't give its eye teeth for the chance to score an accurate assessment of their game or console in the public eye. simExchange isn't a tool for you and me so much as it is a tool for companies who seek to gauge public opinion before making their marketing or production decisions. Because futures markets can fluctuate as quickly as word-of-mouth, a piece of news — such as the release of a new demo, or the admission of a launch date pushback — can drastically effect how a game will perform when it hits the salesroom floor. simExchange offers companies the opportunity to watch their game's 'stock price' rise or fall in 'real-time' in the minds of gamers everywhere (and adjust accordingly) each time they do something right or wrong."
For the video game industry, the simExchange can be much more. 1UP says: "Futures markets are (natch) eerily prescient when it comes to divining the future, and there isn't a company out there who wouldn't give its eye teeth for the chance to score an accurate assessment of their game or console in the public eye. simExchange isn't a tool for you and me so much as it is a tool for companies who seek to gauge public opinion before making their marketing or production decisions. Because futures markets can fluctuate as quickly as word-of-mouth, a piece of news — such as the release of a new demo, or the admission of a launch date pushback — can drastically effect how a game will perform when it hits the salesroom floor. simExchange offers companies the opportunity to watch their game's 'stock price' rise or fall in 'real-time' in the minds of gamers everywhere (and adjust accordingly) each time they do something right or wrong."
Submission + - Get Closure with JavaScript Memory Leaks
An anonymous reader writes: Internet Explorer and Mozilla Firefox are the two Web browsers most commonly associated with memory leaks in JavaScript. The culprit in both browsers is the component object model used to manage DOM objects. This article explains how circular references can lead to memory leaks in JavaScript, particularly when combined with closures. You'll see several common memory leak patterns involving circular references and some easy ways to work around them.
