Open Source IDE Eclipse Photon released

Mr. Thabang Mashologu, Marketing Head at Eclipse Foundation has announced the release of Eclipse Photon. It is the 13th annual release popular open source IDE (Integrated Development Environment).

The main highlights of Eclipse Photon include built-in support for Java 10 and Java 8 EE applications. It also features an improved dark theme with better background, text and popup message colors.

Citing from the official release announcement,

The thirteenth annual simultaneous release of Eclipse projects is a huge accomplishment made possible by the tireless efforts of many committers, projects, and Foundation staff. There are 85 projects in the Eclipse Photon simultaneous release, consisting of over 73 million lines of code, with contributions by 620 developers, 246 of whom are Eclipse committers. Congratulations and thank you to everyone who contributed to this milestone achievement!

Here are some of the highlights of the Eclipse IDE, Photon Edition:

• Full Eclipse IDE user experience for building, debugging, running and packaging Rust applications.
• Expanded C# editing and debug capabilities, including syntax coloring, autocomplete suggestions, code diagnostics, and code navigation tools.
• Support for building Java™ 10 and Java EE™ 8 based applications out of the box.
• Dark theme improvements in text colors, background color, popup dialogs, mark occurrences, and more.

You can read the Eclipse Photon release announcement in the official website. The team has also published a complete list of changes incorporated in Eclipse Photon release.

5 Best Memory Debuggers for Linux Development

The Computer World portal has published an article listing 5 memory debuggers that can be used while coding linux. This article lists 5 popular, free and open source memory debuggers such as Dmalloc, Electric Fence, Mcheck, Mwatch and Mtrace.

As a programmer, I'm aware that I tend to make mistakes -- and why not? Even programmers are human. Some errors are detected during code compilation, while others get caught during software testing. However, a category of error exists that usually does not get detected at either of these stages and that may cause the software to behave unexpectedly -- or worse, terminate prematurely. 

If you haven't already guessed it, I am talking about memory-related errors. Manually debugging these errors can be not only time-consuming but difficult to find and correct. Also, it's worth mentioning that these errors are surprisingly common, especially in software written in programming languages like C and C++, which were designed for use with manual memory management.

Read complete article in Computer World Portal.