sfcrazy writes "Ubuntu developer Oliver Grawert does not prefer to do online banking with Linux Mint. In the official mailing list of the distribution, Ubuntu developers stated that the popular Ubuntu derivative is a vulnerable system and people shouldn't go for online banking on it. One of the Ubuntu developers, Oliver Grawert, originally pointed out that it is not necessary that security updates from Ubuntu get down to Linux Mint users since changes from X.Org, the kernel, Firefox, the boot-loader, and other core components are blocked from being automatically upgraded." Clement Lefebvre, the Linux Mint project founder, has since made a statement and confirmed that Oliver Grawert seems "more opinionated than knowledgeable" adding "the press blew what he said out of proportion."

jones_supa writes "When GCC 4.9 is released in 2014 it will be coming in hot on new features with a large assortment of improvements and new functionality for the open-source compiler. Phoronix provides a recap of some of the really great features of this next major compiler release from the Free Software Foundation. For a quick list: OpenMP 4.0, Intel Cilk Plus multi-threading support, Intel Bay Trail and Silvermont support, NDS32 port, Undefined Behavior Sanitizer, Address Sanitizer, ADA and Fortran updates, improved C11 / C++11 / C++14, better x86 intrinsics, refined diagnostics output. Bubbling under are still: Bulldozer 4 / Excavator support, OpenACC, JIT compiler, disabling Java by default."

jones_supa writes "One of the most important measuring sticks for the success of any software is how long a user keeps it installed after first trying it. Intel has an article about some of the most common reasons users abandon software. Quoting: 'Apps that don’t offer anything helpful or unique tend to be the ones that are uninstalled the most frequently. People cycle through apps incredibly quickly to find the one that best fits their needs. ... A lot of apps have a naturally limited lifecycle; i.e., apps that are centered around a movie release or an app that tracks a pregnancy, or an app that celebrates a holiday. In addition, apps with limited functionality, for example, “lite” games that only go so far, are uninstalled once the user has mastered all the levels.' Some of the common factors they list include: lengthy forms, asking for ratings, collecting unnecessary data, user unfriendliness, unnecessary notifications and, of course, bugs. Additionally, if people have paid even a small price for the app, they are more committed to keep it installed. So, what makes you uninstall a piece of software?"

theodp writes "'Why do programmers start counting at zero?' wondered Mike Hoye, questioning the conventional programming wisdom. Code.org will soon introduce the practice to a hoped-for audience of 10 million schoolchildren as part of Computer Science Education Week's Hour of Code. In a tutorial created by engineers from Microsoft, Google, Twitter and Facebook that's intended to introduce programming to kids as young as six years old, an otherwise breezy lesson featuring look-ma-no-typing Blockly and characters out of Angry Birds and Plants vs. Zombies, a Mark Zuckerberg video introducing the concept of Repeat Loops includes an out-of-place JavaScript example that shows kids it's as easy as 0-1-2-3 to generate 4 lines of lyrics from Happy Birthday to You by using zero-based numbering with a For-loop and ternary If statement. Accompanying videos by Bill Gates on If Statements and basketball star Chris Bosh on Repeat Until Blocks show the Code.org tutorial is still a work-in-progress. That's no big deal, since CSEdWeek has pushed back the delivery date for final Hour of Code tutorials from its prior little-time-for-testing due date to Dec. 9th, the first day of a five-day period during which teachers are expected to deliver the lessons to 10 million students."

Nerval's Lobster writes "Stephen Wolfram, the chief designer of the Mathematica software platform and the Wolfram Alpha 'computation knowledge engine,' has another massive project in the works—although he's remaining somewhat vague about details for the time being. In simplest terms, the project is a new programming language—which he's dubbing the 'Wolfram Language'—which will allow developers and software engineers to program a wide variety of complex functions in a streamlined fashion, for pretty much every single type of hardware from PCs and smartphones all the way up to datacenters and embedded systems. The Language will leverage automation to cut out much of the nitpicking complexity that dominates current programming. 'The Wolfram Language does things automatically whenever you want it to,' he wrote in a recent blog posting. 'Whether it's selecting an optimal algorithm for something. Or picking the most aesthetic layout. Or parallelizing a computation efficiently. Or figuring out the semantic meaning of a piece of data. Or, for that matter, predicting what you might want to do next. Or understanding input you've given in natural language.' In other words, he's proposing a general-purpose programming language with a mind-boggling amount of functions built right in. At this year's SXSW, Wolfram alluded to his decades of work coming together in 'a very nice way,' and this is clearly what he meant. And while it's tempting to dismiss anyone who makes sweeping statements about radically changing the existing paradigm, he does have a record of launching very big projects (Wolfram Alpha contains more than 10 trillion pieces of data cultivated from primary sources, along with tens of thousands of algorithms and equations) that function reliably. At many points over the past few years, he's also expressed a belief that simple equations and programming can converge to create and support enormously complicated systems. Combine all those factors together, and it's clear that Wolfram's pronouncements—no matter how grandiose—can't simply be dismissed. But it remains to be seen how much of an impact he actually has on programming as an art and science."

Last week, we mentioned that the GIMP project had elected to leave SourceForge as its host, citing SourceForge's advertising policies. SourceForge (which shares a parent company with Slashdot) has released a statement about those policies, addressing in particular both ads that are confusing in themselves and their revenue-sharing system called DevShare, based on the provision of third-party software along with users' downloads. Among other things, the SF team is appealing to users to help them find and block misleading ads, and has this to say about the additional downloads: "The DevShare program has been designed to be fully transparent. The installation flow has no deceptive steps, all offers are fully disclosed, and the clear option to completely decline the offer is always available. All uninstallation procedures are exhaustively documented, and all third party offers go through a comprehensive compliance process to make sure they are virus and malware free."

stoolpigeon writes "Yesterday marked the release of Dart SDK 1.0, a cross-browser, open source toolkit for structured web applications. The Dart SDK 1.0 includes everything you need to write structured web applications: a simple yet powerful programming language, robust tools, and comprehensive core libraries. The language has been somewhat controversial, but Google continues to move it forward." Reader slack_justyb adds some more detail: "The new release brings a much tighter dart2js compiler reducing overall JavaScript output up to 40%; Dartium — a version of Google Chrome that has the DartVM in addition to the JavaScript VM as native to the browser; PUB, a package manager for Dart add-ons; and several favorite 3rd party plug-ins that now come out-of-box, in addition to a lot of work for Dart server-side tools that can work to automate server side tasks and help in the construction of web pages. However Dart has many critics not only from the IE and Apple camps, as one would guess, but from the Firefox and Opera camps as well. In addition to the low adoption of Dart from third parties there are some asking where does Dart go from here? Especially considering that Google is one of the strongest pushers for EcmaScript 6."

rjmarvin writes "Microsoft today announced a web-based development environment for app creation to complement Visual Studio 2013, called Visual Studio Online. Microsoft Senior V.P. S. Somasegar says the new web-based IDE is designed for quick tasks related to building Windows Azure websites and services. Microsoft will be releasing the Visual Studio Online Application Insights service in a limited preview to show developers how to deploy and perform in conjunction with Visual Studio 2013's new features."

First time accepted submitter Gavin King writes with news that the Ceylon language hit 1.0 "Ceylon 1.0 is a modern, modular, statically typed programming language for the Java and JavaScript virtual machines. The language features, an emphasis upon readability and a strong bias toward omission or elimination of potentially-harmful constructs; an extremely powerful type system combining subtype and parametric polymorphism with declaration-site variance, including first-class union and intersection types, and using principal types for local type inference and flow-dependent typing; a unique treatment of function and tuple types, enabling powerful abstractions; first-class constructs for defining modules and dependencies between modules; a very flexible syntax including comprehensions and support for expressing tree-like structures; and fully-reified generic types, on both the JVM and JavaScript virtual machines, and a unique typesafe metamodel. More information may be found in the feature list and quick introduction." If you think Ceylon is cool, you might find Ur/Web interesting too.

gbooch writes "The Computer History Museum in Mountain View, California, is not just a museum of hardware, but also of software. The Museum has made public such gems as the source code for MacPaint, Photoshop, and APL, and now code from the Apple II. As their site reports: 'With thanks to Paul Laughton, in collaboration with Dr. Bruce Damer, founder and curator of the Digibarn Computer Museum, and with the permission of Apple Inc., we are pleased to make available the 1978 source code of Apple II DOS for non-commercial use. This material is Copyright © 1978 Apple Inc., and may not be reproduced without permission from Apple.'"

Lemeowski writes "Time has been good to Linux and the kernel community, with the level of participation and volume of activity reaching unprecedented levels. But as core Linux kernel developers grow older, there's a very real concern about ensuring younger generations are getting involved. In this post, Open Access supporter Luis Ibanez shares some exciting stats about recent releases of the Linux kernel, but also warns that 'Maintaining the vitality of this large community does not happen spontaneously. On the contrary, it requires dedication and attention by community members on how to bring new contributors on board, and how to train them and integrate them alongside the well-established developers.'"

An anonymous reader writes "As a new developer at a young-ish software company, I've been told my communication skills need some work. I'm not painfully introverted or socially inept, but I get lost in my work and only contact people if I need something from them or they ask me a question. Traditional advice isn't relevant to casual, less hierarchical companies — I don't have to hold my tongue when someone is wrong or worry about formalities. But I do need to connect with people professionally, since my team members and managers decide my perf and advancement. How do you keep colleagues abreast of your work without having exponentially many needless conversations?"

jeditobe writes with a link to a talk (video recorded, with transcript) about a project we've been posting about for years: ambitious Windows-replacement ReactOS: "In this talk, Alex Ionescu, lead kernel developer for the ReactOS project since 2004 (and recently returning after a long hiatus) will talk about the project's current state, having just passed revision 60000 in the SVN repository. Alex will also cover some of the project's goals, the development and testing methodology being such a massive undertaking (an open source project to reimplement all of Windows from scratch!), partnership with other open source projects (MinGW, Wine, Haiku, etc...). Alex will talk both about the infrastructure side about running such a massive OS project (but without Linux's corporate resources), as well as the day-to-day development challenges of a highly distributed team and the lack of Win32 internals knowledge that makes it hard to recruit. Finally, Alex will do a few demos of the OS, try out a few games and applications, Internet access, etc, and of course, show off a few blue screens of death."

rsmiller510 writes "It would seem on its face that simply asking your users what they need in an app would be the easiest way to build one, but it turns out it's not quite that simple. People often don't know what they want or need or they can't articulate it in a way that's useful to you. They may say I want Google or Dropbox for the enterprise, but they don't get that developers can be so much more creative than that. And the best way to understand those users' needs is to watch what they do, then use your own skills to build apps to make their working lives better or easier."

An anonymous reader writes "Oracle acquired GlassFish when it acquired Sun Microsystems, and now — like OpenSolaris and OpenOffice — the company has announced it will no longer support a commercial version of the product. Mike Milinkovich, executive director of the Eclipse Foundation. said in an interview the decision wasn't exactly a surprise: "The only company that was putting any real investment in GlassFish was Oracle," Milinkovich said. "Nobody else was really stepping up to the plate to help. If you never contributed anything to it, you can't complain when something like this happens." An update to the open source version is still planned for 2014." GlassFish is an open source application server.

Nerval's Lobster writes "A government official who helped oversee the bug-riddled Healthcare.gov Website has resigned his post. Tony Trenkle, Chief Information Officer (CIO) for Medicare and Medicaid Services, which oversees Healthcare.gov, will reportedly join the private sector after he departs on November 15. A spokesperson for the Medicare agency refused to say whether he had been forced out, telling reporters: 'Tony made a decision that he was going to move to the private sector and that is what our COO announced yesterday.' Because of his supervisory role, Trenkle is considered a significant player in the Website's development; The New York Times indicated that he was one of two federal officials who signed an internal memo suggesting that security protocols for the Website weren't in place as recently as late September, a few days before Healthcare.gov's launch.Following Trenkle's resignation, Health and Human Services secretary Kathleen Sebelius admitted to the Senate Finance Committee that Healthcare.gov would require hundreds of fixes. 'We're not where we need to be,' she said. 'It's a pretty aggressive schedule to get to the entire punch list by the end of November.' Sebelius added that she was ultimately accountable for what she termed the 'excruciatingly awful' rollout. Healthcare.gov has experienced massive problems since its Oct. 1 debut. In addition to repeated crashes and slow performance, the Website's software often prevents people from setting up accounts. President Obama has expressed intense frustration with the situation, but insists the Affordable Care Act (ACA) backing the Website remains strong. 'The essence of the law, the health insurance that's available to people is working just fine,' he told reporters in October. 'The problem has been that the website that's supposed to make it easy to apply for insurance hasn't been working.' While the federal government won't release 'official' enrollment numbers until the end of November, it's clear that the Website's backers are losing the battle of public perception."

rjmarvin writes "The Academy for Software Engineering, right off of Manhattan's Union Square, is in its second year of educating students for a future in computer science and software engineering. No entrance exams, no admission standards, just an opportunity for any student interested in software to take specialized classes like robotics and programming, go on trips to companies like Google and Facebook, and spend summers interning at Morgan Stanley and JPMorgan Chase before heading to college and into the workforce, powering the next wave of innovation as members of the tech workforce in New York's burgeoning 'Silicon Alley.'"

mikejuk writes "Bribe.io announces itself as: 'A super easy way to bribe developers to fix bugs and add features in the software you're using.' Recognizing the fact that a lot of open source projects are maintained by developers working alone and in their spare time, the idea is to encourage other developers to by specifying a monetary value to a bug report or feature enhancement. Once an initial 'Bribe' has been posted others can 'chip in' and add to the financial incentive."

Nerval's Lobster writes "Benchmarking is a tricky business: a valid benchmarking tries to remove all extraneous variables in order to get an accurate measurement, a process that's often problematic: sometimes it's nearly impossible to remove all outside influences, and often the process of taking the measurement can skew the results. In deciding to compare three compilers (the Intel C++ compiler, the GNU C++ compiler (g++), and the LLVM clang compiler), developer and editor Jeff Cogswell takes a number of 'real world' factors into account, such as how each compiler deals with templates, and comes to certain conclusions. 'It's interesting that the code built with the g++ compiler performed the best in most cases, although the clang compiler proved to be the fastest in terms of compilation time,' he writes. 'But I wasn't able to test much regarding the parallel processing with clang, since its Cilk Plus extension aren't quite ready, and the Threading Building Blocks team hasn't ported it yet.' Follow his work and see if you agree, and suggest where he can go from here."

rtoz writes "For handling the future unreliable chips, a research group at MIT's Computer Science and Artificial Intelligence Laboratory has developed a new programming framework that enables software developers to specify when errors may be tolerable. The system then calculates the probability that the software will perform as it's intended. As transistors get smaller, they also become less reliable. This reliability won't be a major issue in some cases. For example, if few pixels in each frame of a high-definition video are improperly decoded, viewers probably won't notice — but relaxing the requirement of perfect decoding could yield gains in speed or energy efficiency."