SternisheFan writes "Google has expanded its legal agreement with developers working on Android applications to specifically prohibit them from taking any action that could lead to a fragmentation of the operating system. The prohibition was added to the terms and conditions for Google's Android SDK (software development kit), which developers must accept before using the software to build Android apps. The previous version of the terms of service, published in April 2009, didn't address the issue, but the new terms published on Tuesday include this new paragraph: 'You agree that you will not take any actions that may cause or result in the fragmentation of Android, including but not limited to distributing, participating in the creation of, or promoting in any way a software development kit derived from the SDK.' Google did not respond to several requests for comment. The issue of Android fragmentation has been gaining increased attention, but it's happened largely as a result of actions taken by Google and Android handset makers, not developers. It's a problem because it means that Android applications may not run properly across all Android devices. 'It continues to be a problem, both on smartphones and tablets,' said Avi Greengart, research director at Consumer Devices. 'Google has talked about multiple initiatives for dealing with it, but none of them have successfully addressed it.'"
Sign up for the Slashdot Daily Newsletter! DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. ×
Nerval's Lobster writes "When Steven Sinofsky stepped down as head of Microsoft's Windows division earlier this week, multiple publications cited friction with other executives as the primary reason behind the departure. Whether or not that's the case—neither Sinofsky nor Microsoft has offered an official explanation, aside from the usual platitudes—someone with connections to Microsoft is claiming that Sinofsky's departure stemmed from a failed attempt to bring additional parts of the company under his control. 'Steven had apparently lost recent battles to bring both Windows Phone and the Developer Division under his control,' Hal Berenson, president of consulting group True Mountain Group and a former Microsoft executive, wrote in a Nov. 13 blog posting. 'I suspect that he saw those [losses] both as a roadblock to where he wanted to take Windows over the next few years, and a clear indication that his political power within Microsoft had peaked.' The departure, he added, was the 'outgrowth of conflict.' Berenson's claim was enough to draw Sinofsky himself into the discussion. In the comments section below the posting, Sinofsky left a short note suggesting that rumors of a multi-product takeover were, frankly, malarkey."
sfcrazy writes "A very serious argument erupted on the Linux kernel mailing list when Andy Grover, a Red Hat SCSI target engineer, requested that Nicholas A. Bellinger, the Linux SCSI target maintainer, provide proof of non-infringement of the GPL. Nick is developer at Rising Tide Systems, a Red Hat competitor, and a maker of advanced SCSI storage systems. Nick's company recently produced a groundbreaking technology involving advanced SCSI commands which will give Rising Tide Systems a lead in producing SCSI storage systems. Now, RTS is blocking Red Hat from getting access to that code as it's proprietary. What's uncertain is whether RTS' code is covered by GPL or not — if it is then Red Hat has all the rights to get access to it and it's a serious GPL violation."
Artefacto writes "The Ksplice team has made available a git repository with the changes Red Hat made to the kernel broken down. They are calling this project RedPatch. This comes in response to a policy change Red Hat had implemented in early 2011, with the goal of undercutting Oracle and other vendors' strategy of poaching Red Hat's customers. The Ksplice team says they've been working on these individual patches since then. They claim to be now making it public because they 'feel everyone in the Linux community can benefit from the work.' 'For Ksplice, we build individual updates for each change and rely on source patches that are broken-out, not a giant tarball. Otherwise, we wouldn't be able to take the right patches to create individual updates for each fix, and to skip over the noise — like a change that speeds up bootup — which is unnecessary for an already-running system.'"
First time accepted submitter jemenake writes "A friend of mine teaches electronic media (Photoshop, Premiere, etc.) at a local high-school. Right now, they're doing Photoshop, and each chapter in the book starts with an 'end result' file which shows what they're going to construct in that chapter, and then, given the basic graphical assets (background textures, photos, etc.), the students need to duplicate the same look in the final-result file. The problem, of course, is that some students just grab the final-result file and rename it and turn it in. Some are a little less brazen and they rename a few layers, maybe alter the colors on a few images, etc. So, it becomes time-consuming for her to open each file alongside the final-result file to see if it's 'too perfect.'" How to look for images closer than they should be to the original? Read on for more details.
CWmike writes with this excerpt from Computerworld: "Steven Sinofsky, the executive in charge of Microsoft's Windows 8 operating system and the driving force behind the new OS, is leaving the company effective immediately, Microsoft announced late Monday. Sinofsky was also the public face for Windows 8 and its new Metro interface, posting constant updates in a Windows 8 blog that charted its development. His last post, fittingly, was entitled 'Updating Windows 8 for General Availability.' The OS was officially launched at the end of last month. According to the All Things D blog, there was growing tension between Sinofsky and other members of the Microsoft executive team, who didn't see him as enough of a team player. But Microsoft's official position is that the decision was a mutual one. Sinofsky had only good things to say about his former employer." Also at SlashCloud.
ctrahey writes "Many of us disregard the impact of our titles on various aspects of our lives, both professional and otherwise. Perhaps it's appropriate to ask two questions about the difference between a couple titles familiar to the Slashdot community: Developer vs Software Engineer. What are the factors to consider in the appropriate use of the titles? And (more interesting to me), what influence might the use of these titles have on the written code? Have you observed a difference in attitudes, priorities, or outlooks in talent as a corollary to their titles?"
First time accepted submitter Hatfield56 writes "I've been in IT since the mid-1980s, mainly working for financial institutions. After 16 years at a company, as a programmer (Java, C#, PL/SQL, some Unix scripting) and technical lead, my job was outsourced. That was in 2009 when the job market was basically dead. After many false starts, here I am 3 years later wondering what to do. I'm sure if I were 40 I'd be working already but over 60 you might as well be dead. SO, I'm wondering about A+. Does anyone think that this will make me more employable? Or should I being a greeter at Walmart?"
jfruh writes "Among the winners of last night's election: marijuana users. Voters in both Washington and Colorado approved referenda that legalized marijuana for recreational use, though the drug remains illegal under federal law. There's been a long-standing debate among programmers as to whether recreational drugs, including pot and hallucinagens like LSD, can actually help programmers code. Don't forget, there was a substantial overlap between the wave of computer professionals who came of age in the '60s and that era's counterculture." (There's even a good book on that topic.)
From the H reporting on LinuxCon Europe comes news that several Linux kernel developers have been laid off by AMD as part of its workforce reduction. From the article: "OSRC staff primarily worked to develop the Linux support for AMD's server processors, but they also wrote code and extensions for related desktop and notebook CPUs – for example, they looked after the code to support CPU frequency scaling for the PowerNow and Turbo Core technologies. While working on the kernel's IOMMU and KVM support, one of AMD's former employees contributed to the development of the "IOMMU groups" feature that was integrated into Linux 3.6; this feature provides the basis for a new Linux 3.6 technology that allows a host's PCIe devices to be passed through to virtual machines and can also be used with Intel CPUs." Looks like the group was doing interesting research on hypervisors, lockless data structures, and multi-core synchronization primitives among other things. The Open Source Radeon driver developers are not affected by this at least.
dstates writes "Want a good job in IT? Detroit of all places may be the place to be. GM is bringing IT development back in house to speed innovation. Among other initiatives, a self driving Cadillac is planned by mid decade. Ford is also actively developing driver assist technology and is betting big on voice recognition. Ann Arbor has thousands of smart cars wirelessly connected on the road. Think about all those aging baby boomers with houses in the burbs and no desire to move as their vision and reflexes decline. The smart car is a huge market. Seriously, Detroit and SE Michigan have good jobs, great universities, cheap housing and easy access to great sports and outdoors activities."
jbernardo writes "Nokia has put in deep freeze its free developer program, the launchpad. Now, in the Developer Programs page, one can only see a pitch for a paid 'Nokia Premium Developer Program,' and below, in the Nokia Developer Pro and Developer Launchpad box, there is a text merely stating that Nokia are not currently accepting new applications for Nokia Developer Launchpad and Nokia Developer Pro programs. With most (if not all) Launchpad memberships already expired, seems like Nokia no longer is interested in the developer community, which once was one of the mainstays of its domination of the smartphone market. Of course, that domination was destroyed by Elop and its 'burning platforms' memo, together with the failed bet on Windows Phone 7, so maybe giving up on developers would also be expectable."
Esther Schindler writes "Why is it that young developers imagine that older programmers can't program in a modern environment? Too many of us of a 'certain age' are facing an IT work environment that is hostile to older workers. Lately, Steven Vaughan-Nichols has been been noticing that the old meme about how grandpa can't understand iPhones, Linux, or the cloud is showing up more often even as it's becoming increasingly irrelevant. The truth is: Many older developers are every bit as good as young programmers, and he cites plenty of example of still-relevant geeks to prove it. And he writes, 'Sadly, while that should have put an end to the idea that long hours are a fact of IT life, this remnant of our factory-line past lingers both in high tech and in other industries. But what really matters is who's productive and who's not.'"