Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds

Tech News - Programming

573 Articles
article-image-fyne-1-0-released-as-a-cross-platform-gui-in-go-based-on-material-design
Sugandha Lahoti
25 Mar 2019
2 min read
Save for later

Fyne 1.0 released as a cross-platform GUI in Go based on Material Design

Sugandha Lahoti
25 Mar 2019
2 min read
Last week, Wednesday marked the first major milestone for Fyne, which is a cross-platform GUI written in Go. Fyne 1.0 uses OpenGL to provide cross-platform graphics and the entire toolkit is developed using scalable graphics. The Fyne toolkit communicates with operating system graphics using OpenGL, which is supported on almost all desktop and laptop systems. To do this, it relies on the built-in functionality of Cgo, the C language bridge for Go. For packaging, it uses fyne package command to generate and package all the required metadata for an application to distribute on macOS, Linux, or Windows. By default, it will build an application bundle for the current platform, which can be used in part of a cross-compilation workflow. What’s new in Fyne 1.0? Canvas API (rect, line, circle, text, image) Widget API (box, button, check, entry, form, group, hyperlink, icon, label, progress bar, radio, scroller, tabs, and toolbar) Light and dark themes Pointer, key and shortcut APIs (generic and desktop extension) OpenGL driver for Linux, macOS, and Windows Tools for embedding data and packaging releases Currently, the release only supports desktop applications. For more info, read Fyne’s blog. You may also check out Hands-On GUI Application Development in Go to learn more about Go programming. Introducing Web High-Level Shading Language (WHLSL): A graphics shading language for WebGPU State of Go February 2019 – Golang developments report for this month released Golang just celebrated its ninth anniversary
Read more
  • 0
  • 0
  • 4540

article-image-pypy-7-1-releases-with-utf-8-for-unicode-strings
Natasha Mathur
25 Mar 2019
2 min read
Save for later

PyPy 7.1 releases with UTF-8 for Unicode strings

Natasha Mathur
25 Mar 2019
2 min read
PyPy team released version 7.1 of PyPy, a fast and compliant Python Interpreter, yesterday. PyPy 7.1 explores new features, improvements, and other changes. PyPy 7.1 supports x86 machines on common operating systems (Linux 32/64 bits, Mac OS X 64 bits, Windows 32 bits, OpenBSD, FreeBSD), ARM32,  s390x running Linux, etc. What’s new in PyPy 7.1? PyPy 7.1 comes with two different interpreters, namely, PyPy2.7 (an interpreter that supports the syntax and features of Python 2.7) and PyPy3.6-beta (second official release of PyPy that supports 3.6 features). The latest release finally merges the internal refactoring of unicode representation as UTF-8. Users can remove the conversions from strings to unicode internally, thus leading to a nice speed bump. The UTF-8 changes have been merged to the py3.5 branch (Python3.5.3). The ability to use the buffer protocol with ctype structures and arrays has been improved in PyPy 7.1. The CFFI (C Foreign Function Interface) backend has been updated to version 1.12.2 in PyPy 7.1. Users can use CFFI as opposed to the c-extensions to interact with C and cppyy to interact with C++ code. PyPy team states that they need help from the contributors in case of PyPy and RPython documentation improvements, for tweaking popular modules to run on pypy, and general help with making RPython’s JIT even better. For more information, check out the official PyPy 7.1 release notes. PyPy 7.0 released for Python 2.7, 3.5, and 3.6 alpha Python 3.8 alpha 2 is now available for testing Python steering council election results are out for January 2019
Read more
  • 0
  • 0
  • 1722

article-image-gnu-nano-4-0-text-editor-releases
Natasha Mathur
25 Mar 2019
2 min read
Save for later

GNU Nano 4.0 text editor releases!

Natasha Mathur
25 Mar 2019
2 min read
GNU team released version 4.0 of their GNU Nano, a text editor for Unix-like computing systems that use command line interface, yesterday. GNU Nano 4.0 explores new changes and improvements. GNU Nano 4.0 release has been named as “Thy Rope of Sands”. What’s new in GNU Nano 4.0? The overlong line that used to get automatically hard-wrapped has been fixed in GNU Nano 4.0. Smooth scrolling has become the default in GNU Nano 4.0. No newline character will be added automatically at end of buffer. Option --breaklonglines (-b) can easily turn the automatic hard-wrapping back on. Other pption --jumpyscrolling (-j) provides the chunky, half-screen scrolling, and option --emptyline (-e) leaves the line below the title bar unused. <Alt+Up> and <Alt+Down> can now do a linewise scroll instead of a findnext. Option --guidestripe=<number> is now able to draw a vertical bar at the given column in GNU Nano 4.0. In case a line continues offscreen, it will now end with a highlighted ">" in GNU Nano 4.0. The bindable functions such as 'cutwordleft' and 'cutwordright' have been renamed in GNU Nano 4.0. The paragraph-jumping functions have been moved from Search to Go-to-Line. An option --rebinddelete can compensate for more misbindings. The --disable-wrapping-as-root configure option has been removed. For more details on GNU Nano 4.0, check out the official release notes. GNU Octave 5.1.0 releases with new changes and improvements GNU Health Federation message and authentication server drops MongoDB and adopts PostgreSQL GNU Bison 3.3 released with major bug fixes, yyrhs and yyphrs tables, token constructors and more
Read more
  • 0
  • 0
  • 1667
Visually different images

article-image-llvm-8-0-0-releases
Natasha Mathur
22 Mar 2019
3 min read
Save for later

LLVM 8.0.0 releases!

Natasha Mathur
22 Mar 2019
3 min read
LLVM team released LLVM 8.0, earlier this week. LLVM is a collection of tools that help develop compiler front ends and back ends. LLVM is written in C++ and has been designed for compile-time, link-time, run-time, and "idle-time" optimization of programs that are written in arbitrary programming languages. LLVM 8.0 explores known issues, major improvements and other changes in the subprojects of LLVM. There were certain issues in LLVM 8.0.0 that could not be fixed earlier (before this release). For instance, clang is getting miscompiled by trunk GCC, and “asan-dynamic” is not able to work on FreeBSD. Other than the issues, there is a long list of changes that have been made to LLVM 8.0.0. Non-comprehensive changes to LLVM 8.0.0 llvm-cov tool can export lcov trace files with the help of the -format=lcov option of the export command. The add_llvm_loadable_module CMake macro has been deprecated. The add_llvm_library macro with the MODULE argument can now help provide the same functionality. For MinGW, references to data variables that are to be imported from a dll can be now accessed via a stub. This will further allow the linker to convert it to a dllimport if needed. Support has been added for labels as offsets in .reloc directive. Windows support for libFuzzer (x86_64) has also been added. Other Changes LLVM IR:  The Function attribute named speculative_load_hardening has been introduced. This will indicate that Speculative Load Hardening should be enabled for the function body. JIT APIs: ORC (On Request Compilation) JIT APIs will now support concurrent compilation. The existing (non-concurrent) ORC layer classes, as well as the related APIs, have been deprecated. These have been renamed with a “Legacy” prefix (e.g. LegacyIRCompileLayer). All the deprecated classes will be removed in LLVM 9. AArch64 Target: Support has been added for Speculative Load Hardening. Also, initial support added for the Tiny code model, where code and the statically defined symbols should remain within 1MB. MIPS Target: Support forGlobalISel instruction selection framework has been improved. ORC JIT will now offer support for MIPS and MIPS64 architectures. There’s also newly added support for MIPS N32 AB. PowerPC Target: This has now been switched to non-PIC default in LLVM 8.0.0. Darwin support has also been deprecated. Also, Out-of-Order scheduling has been enabled for P9. SystemZ Target: These include various code-gen improvements related to improved auto-vectorization, inlining, as well as the instruction scheduling. Other than these, changes have also been made to X86 target, WebAssembly Target, Nios2 target, and LLDB. For a complete list of changes, check out the official LLVM 8.0.0 release notes. LLVM 7.0.0 released with improved optimization and new tools for monitoring LLVM will be relicensing under Apache 2.0 start of next year LLVM officially migrating to GitHub from Apache SVN
Read more
  • 0
  • 0
  • 2681

article-image-linux-5-1-will-come-with-intel-graphics-virtual-memory-support-and-more
Amrata Joshi
19 Mar 2019
2 min read
Save for later

Linux 5.1 will come with Intel graphics, virtual memory support, and more

Amrata Joshi
19 Mar 2019
2 min read
The team at Linux has put in a lot of efforts on Linux RC 5.1. Last week, Linus Torvalds, the creator of the Linux kernel, announced that the two-week long merge window for Linux 5.1 is finally coming to an end. The first Release Candidate of Linux kernel 5.1 is finally ready for testing. Let’s have a look at the changes and new features which will be coming in Linux RC 5.1. What’s expected in Linux RC 5.1? Intel graphics With this release, the Intel Fastboot is enabled by default. The Intel graphics driver eliminates unnecessary mode-set operations at boot-time by default. The ones on older Intel graphics can still toggle the feature with the i915.fastboot=1 kernel parameter. Fastboot comes with a clean, flicker-free Linux boot experience. This release comes with Intel HDCP 2.2 support. There is an added support for Coffeelake GVT  for Intel's graphics virtualization tech. Virtual memory support This release comes with Nouveau DRM driver that has heterogeneous memory management hook-ups, which provides shared virtual memory support. This release comes with support for AMDGPU Vega 10/20 BACO and other Vega enhancements. There is a new DRM driver in this release known as the Arm Komeda display driver. Added Support This release comes with Support for the Bitmain SoC as a dual-core A53 combined with a single RISC-V core. This release comes with new Arm support including the Socionext Milbeaut, NXP i.MX8QuadXPlus, and a few Rensas SoCs. New accelerator This release comes with Habana Labs Goya accelerator along with its new driver. A new accelerator subsystem is expected in the Linux kernel. The accelerator is based on AI having open-source, mainline kernel support. Power management This release comes with Icelake PMC core support for dealing with the power management controller registers on the CPUs. To know more about this news in detail, check out Linux Kernel’s mailing list. The Linux Foundation announces the CHIPS Alliance project for deeper open source hardware integration Announcing Linux 5.0! Linux use-after-free vulnerability found in Linux 2.6 through 4.20.11
Read more
  • 0
  • 0
  • 3827

article-image-google-open-sources-sandboxed-api-a-tool-that-helps-in-automating-the-process-of-porting-existing-c-and-c-code
Amrata Joshi
19 Mar 2019
2 min read
Save for later

Google Open-sources Sandboxed API, a tool that helps in automating the process of porting existing C and C++ code

Amrata Joshi
19 Mar 2019
2 min read
Yesterday, the team at Google open-sourced Sandboxed API, a tool that Google has been using internally for its data centers for years. It is a project for sandboxing C and C++ libraries running on Linux systems. Google has made the Sandboxed API available on GitHub. Sandboxed API helps coders to automate the process of porting their existing C and C++ code in order to run on top of Sandbox2, which is Google's custom-made sandbox environment for Linux operating systems. Sandbox2 has also been open-sourced and is included with Sandboxed API GitHub repository. Christian Blichmann & Robert Swiecki, from Google's ISE Sandboxing team, said, "Many popular software containment tools might not sufficiently isolate the rest of the OS, and those which do, might require time-consuming redefinition of security boundaries for each and every project that should be sandboxed." The idea behind introducing sandboxing The idea behind sandboxing is to prevent bugs from spreading from one process to another, or the underlying operating system and the kernel. Many software projects process data that are externally generated and potentially could be untrusted. For instance, the conversion of user-provided picture files into different formats or executing user-generated software code. In case, a software library that parses such data is complex, then there is a high possibility that it might fall victim to certain types of security vulnerabilities such as memory corruption bugs or other problems related to the parsing logic. These vulnerabilities can have a serious impact on security. In order to overcome these challenges, developers prefer software isolation method known as sandboxing. With the help of sandboxing methods, developers make sure that only resources such as files, networking connections, and other operating system resources are accessible to the code involved in parsing user-generated content. The team plans to have an added support more operating systems and plans to bring Sandboxed API to the Unix-like systems like the BSDs (FreeBSD, OpenBSD) and macOS. Google also aims to bring CMake support to the API. To know more about this news in detail, check out Google’s blog post. Google to be the founding member of CDF (Continuous Delivery Foundation) Google announces the stable release of Android Jetpack Navigation #GooglePayoutsForAll: A digital protest against Google’s $135 million execs payout for misconduct
Read more
  • 0
  • 0
  • 2418
Unlock access to the largest independent learning library in Tech for FREE!
Get unlimited access to 7500+ expert-authored eBooks and video courses covering every tech area you can think of.
Renews at $15.99/month. Cancel anytime
article-image-gnome-3-32-released-with-fractional-scaling-improvements-to-desktop-web-and-much-more
Amrata Joshi
14 Mar 2019
3 min read
Save for later

GNOME 3.32 released with fractional scaling, improvements to desktop, web and much more

Amrata Joshi
14 Mar 2019
3 min read
Yesterday, the team at GNOME released the latest version of GNOME 3, GNOME 3.32, a free open-source desktop environment for Unix-like operating systems. This release comes with improvements to desktop, web and much more. What’s new in GNOME 3.32? Fractional Scaling Fractional scaling is available as an experimental option that includes several fractional values with good visual quality on any given monitor. This feature is a major enhancement for the GNOME desktop. It requires manually adding scale-monitor-framebuffer to the settings keyorg.gnome.mutter.experimental-features. Improved data structures in GNOME desktop This release comes with improvements to foundation data structures in the GNOME Desktop for faster and snappier feel to the animations, icons and top shell panel. The search database has been improved which helps in searching faster. Even the on-screen keyboard has been improved, it now supports an emoji chooser. New automation mode in the GNOME Web GNOME Web now comes with a new automation mode which allows the application to be controlled by WebDriver. The reader mode has been enhanced now that features a set of customizable preferences and an improved style. With this release, the touchpad users can now take advantage of more gestures while browsing. For example, swipe left or right to go back or forward through browsing history. New settings for permissions Settings come with a new “Application Permissions” panel that shows resources and permissions for various applications, including installed Flatpak applications. Users can now grant permissions to certain resources when requested by the application. The Sound settings have been enhanced for supporting a vertical layout and an intuitive placement of options. With this release, the night light color temperature can now be adjusted for a warmer or cooler setting. GNOME Boxes GNOME Boxes tries to enable 3D acceleration for virtual machines if both the guest and host support it. This leads to better performance of graphics-intensive guest applications such as games and video editors. Application Management from multiple sources This release can handle apps available from multiple sources, such as Flatpak and distribution repositories. With this release, Flatpak app entries now can list the permissions required on the details page. This will give users a comprehensive understanding of what data the software will need access to. Even browsing application details will get faster now with the new XML parsing library used in this release. To know more about this release, check out the official announcement. GNOME team adds Fractional Scaling support in the upcoming GNOME 3.32 GNOME 3.32 says goodbye to application menus Fedora 29 beta brings Modularity, GNOME 3.30 support and other changes  
Read more
  • 0
  • 0
  • 11610

article-image-sublime-text-3-2-released-with-git-integration-improved-themes-editor-control-and-much-more
Amrata Joshi
14 Mar 2019
3 min read
Save for later

Sublime Text 3.2 released with Git integration, improved themes, editor control and much more!

Amrata Joshi
14 Mar 2019
3 min read
Yesterday, the team behind Sublime Text released Sublime Text 3.2, a text editor that comes with Git integration, improved diff markers, new theme functionality and much more. What’s new in Sublime Text 3.2? GIT integration With this release, the files and folders in the sidebar will now display badges for indicating Git status. In this release, the ignored files and folders are de-emphasized. In Sublime Text 3.2, the Git branch and number of modifications are displayed in the status bar. The commands have now been added to open a repository. Now there are few themes that customize the display of sidebar badges and status bar information. A new setting show_git_status has been added that disables Git integration. Improved editor control This release comes with block_caret setting. The positioning and sizing of gutter icons have now been improved. This release comes with improved IME support for Windows and improved input method (IM) support - fcitx, ibus, etc for Linux. Improved diff markers With this release, diff markers now display added, modified and deleted lines. A new setting called mini_diff now controls incremental diff behavior. With the new Git functionality, diffs can now be calculated against HEAD or the index. Few diff-related commands such as Next Modification, Previous Modification, and Revert Modification have been added. Improved files and folders For Windows, the paths are treated as case-sensitive and the unlock directories are closed. Enhanced themes/UI This release comes with added support for variables and revised JSON format with variables key. Performance has been improved with large numbers of rules in a .sublime-theme. Also, support for macOS native tabs has been added. Window placement and resize performance has been improved. API This release comes with View.set_reference_document() and View.reset_reference_document() for controlling diff generation. Phantoms can now be  drawn correctly in conjunction with draw_centered. Major bug fixes In this release, the Goto Symbol in Project has been fixed. The draw_minimap_border setting is now working. Few users are comparing the performance of Sublime Text with VScode as they think VScode is better. One of the users commented on HackerNews, “I hope Sublime steps up their game, as I think VScode is standing on their shoulders, and competition is good.” Few others think that Sublime is the best editor. Another comment reads, “If all I needed was a great text editor, I would use Sublime. It's everything I want in an editor.” To know more about this news, check out Sublime Text’s blog post. Meet Sublime Merge, a new Git client from the makers of Sublime Text Introducing R-Factor, a refactoring tool for React and Redux Typescript 3.3 is finally released!
Read more
  • 0
  • 0
  • 2651

article-image-microsoft-open-sources-accessibility-insights-for-web-a-chrome-extension-to-help-web-developers-fix-their-accessibility-issues
Sugandha Lahoti
14 Mar 2019
2 min read
Save for later

Microsoft open sources ‘Accessibility Insights for Web’, a chrome extension to help web developers fix their accessibility issues

Sugandha Lahoti
14 Mar 2019
2 min read
On Tuesday, Microsoft open sourced its Accessibility tools, allowing developers to easily find and fix common accessibility issues early in the development cycle. This includes Accessibility Insights for Windows and Accessibility Insights for Web, both built on Deque’s open source axe technology. You can run quick tests, easily create audits that you can export and share with others, and even file issues to GitHub. Accessibility Insights for Web Accessibility Insights for Web is basically a Chrome extension that helps developers find and fix accessibility issues in web apps and sites. The tool comes with a lightweight, two-step process called FastPass that helps developers identify common, high-impact accessibility issues. Fast Pass uses automated checks to check compliance with approximately 50 accessibility requirements. It also makes use of Tab stops to provide clear instructions and a visual helper for identifying accessibility issues related to keyboard access, such as missing tab stops, keyboard traps, and incorrect tab order. The second part of Accessibility Insights is Assessment which helps HTML developers in verifying if a web app or web site is 100% compliant with Web Content Accessibility Guidelines (WCAG) 2.0 Level AA. It also comes with Automated checks and also Manual Testing to provide step-by-step instructions, examples, and how-to-fix guidance for approximately 20 tests. Deque Systems provides GitHub issue filing for Accessibility Insights for Web, and color contrast detection heuristics for Accessibility Insights for Windows. On why Accessibility Insights is open sourced, Microsoft writes in a blog post, “We are driven by the promise of more accessible products for more people.  That’s why we’re releasing Accessibility Insights to the open source and accessibility communities – it’s all of ours now, and together we’ll continue to make it a better tool and build a more accessible future.” You can read more about Accessibility Insights on its website. It’s a win for Web accessibility as courts can now order companies to make their sites WCAG 2.0 compliant W3C and FIDO Alliance declare WebAuthn as the web standard for password-free logins Microsoft open sources the Windows Calculator code on GitHub
Read more
  • 0
  • 0
  • 5057

article-image-google-introduces-season-of-docs-that-will-connect-technical-writers-and-mentors-with-open-source-projects
Amrata Joshi
13 Mar 2019
2 min read
Save for later

Google introduces Season of Docs that will connect technical writers and mentors with open source projects

Amrata Joshi
13 Mar 2019
2 min read
Just two days ago, the team at Google announced Season of Docs, a new program which will connect technical writers with open source projects. Season of Docs will help in bringing technical writers and open source projects together in order to work on open source documentation. https://twitter.com/GoogleOSS/status/1105138318826627072 According to Open Source Survey, documentation is valued in open source communities but it is still difficult to work on it. A person dealing with the documentation needs to know how to structure a documentation site so that people can easily understand the content and only technical writers can do that. Another plus point is that they are aware of the procedures of writing docs that can fit the needs of their audience. Technical writers can help in optimizing a community’s processes for open source contribution and onboarding new contributors. With Season of Docs, technical writers can spend a few months working closely with open source communities. Writes can work with their chosen open source project and also explore the latest technologies. Mentors from open source organizations can share their knowledge based on their communities’ processes and tools. The technical writers and mentors together can build a new doc set and improve the structure of the existing docs. They can also work on tutorials and further improve contribution processes and guides. According to the team, this project will raise awareness about open source, docs, and technical writing. The open source organizations can apply for participating in Season of Docs starting from 2nd to 23rd of April. Google will then publish the list of accepted mentoring organizations, along with their ideas for documentation projects from 30th April. In July, Google will announce the accepted technical writer projects. The technical writers will get a chance to work with mentors on the accepted projects and submit their work between 2nd September and 29th November. Google will then publish the list of successfully completed projects by 10th December. To know more about this news, check out Google’s blog post. Google Cloud Console Incident Resolved! Google confirms it paid $135 million as exit packages to senior execs accused of sexual harassment Researchers input rabbit-duck illusion to Google Cloud Vision API and conclude it shows orientation-bias  
Read more
  • 0
  • 0
  • 3781
article-image-r-core-team-releases-r-3-5-3
Natasha Mathur
13 Mar 2019
2 min read
Save for later

R core team releases R 3.5.3

Natasha Mathur
13 Mar 2019
2 min read
The R Core Team released R 3.5.3, last week. R 3.5.3 explores bug fixes to the functions writeLines, setClassUnion, and stopifnot. R 3.5.3 is a minor release and does not consist of many new changes or improvements. What’s new in R 3.5.3? Detection of flags has been improved for C++ 98/11/14/17. There’s a new macro ‘F_VISIBILITY’ chosen as an alternative for ‘F77_VISIBILITY’. This new macro will now become the preferred form in R 3.6.0. The issue in writeLines (readLines (fnam), fnam) has been fixed. It now works as expected. setClassUnion () no longer sends warnings to its users. It instead uses message() on encountering “non local” subclasses in class members. The failure issue in stopifnot (exprs = T) has been fixed. R team usually use the release names that are in references to Peanuts strips/films. The code-name for this release ( R 3.5.3) has been selected as "Great Truth" by the R team, which left its users with a bit of a mystery. R core team also gave a hint to its users, saying that the clue is in the date of the release i.e. 11th March 2019. The code-name has been debunked, with one user tweeting out the reference in one of the Peanuts strips: https://twitter.com/AdelmoFilho42/status/1105079537749184512 For more information, check out the official R 3.5.3 release notes. Android Studio 3.5 Canary 7 releases! LXD 3.11 releases with configurable snapshot expiry, progress reporting, and more GNU Octave 5.1.0 releases with new changes and improvements
Read more
  • 0
  • 0
  • 1891

article-image-fedora-31-will-now-come-with-mono-5-to-offer-open-source-net-support
Amrata Joshi
12 Mar 2019
2 min read
Save for later

Fedora 31 will now come with Mono 5 to offer open-source .NET support

Amrata Joshi
12 Mar 2019
2 min read
Fedora has always been shipping Mono 4.8, the open source development platform for building cross-platform applications, with each Fedora release. Even after shipping Mono 5.0 in May 2017, the company still continued with Mono 4.8. But it seems the idea will be changing now with the release of Fedora 31. With Fedora 31, the team at Fedora is finally planning to switch to Mono 5.20 which is expected to release later this year. An effort was made in the past few months by the Fedora team to build Mono from source. The build was also done for Debian using msc instead of csc and the reference assemblies were rebuilt from source. In case of Mono, it requires itself to build. The Mono version 4.8 which is included in Fedora currently, is too old to build version 5.20. Currently, the team has been using monolite and a little version of mono compiler, .NET 4.7.1 reference assemblies for first build time. The sources for the required patch files are maintained on Github. The transition from Mono 4 to Mono 5 was on halt because of the changes required in their compiler stack and its dependency upon some binary references. These binaries are available as a source but treated as pre-compiled binaries for simplification and speed. The Fedora developers are now working towards getting Mono 5 into Fedora 31. This will also let the cross-platform applications that are relying upon Microsoft's .NET framework 4.7 and later to now work. Mono 4.8 is also not compatible for PowerPC 64-bit but it is expected that Mono 5 will be. To know more about this news, check out the change proposal. Fedora 29 released with Modularity, Silverblue, and more Swift is now available on Fedora 28 Fedora 29 beta brings Modularity, GNOME 3.30 support and other changes
Read more
  • 0
  • 0
  • 2915

article-image-gcc-9-will-come-with-improved-diagnostics-simpler-c-errors-and-much-more
Amrata Joshi
11 Mar 2019
2 min read
Save for later

GCC 9.1 releases with improved diagnostics, simpler C++ errors and much more

Amrata Joshi
11 Mar 2019
2 min read
Just two months ago, the team behind GCC (GNU Compiler Collection) made certain changes to GCC 9.1. And Last week, the team released GCC 9.1 with improved diagnostics, location and simpler C++ errors.  What’s new in GCC 9.1? Changes to diagnostics The team added a left-hand margin that shows line numbers. GCC 9.1 now has a new look for the diagnostics. The diagnostics can label regions of the source code in order to show relevant information. The diagnostics come with left-hand and right-hand sides of the “+” operator, so GCC highlights them inline. The team has added a JSON output format such that GCC 9.1 now has a machine-readable output format for diagnostics. C++ errors  The compiler usually has to consider several functions while dealing with C++ at a given call site and reject all of them for different reasons. Also, the g++‘s error messages need to be handled and a specific reason needs to be given for rejecting each function. This makes simple cases difficult to read. This release comes with a  special-casing to simplify g++ errors for common cases. Improved C++ syntax in GCC 9.1 The major issue within GCC’s internal representation is that not every node within the syntax tree has a source location. For GCC 9.1, the team has worked to solve this problem so that most of the places in the C++ syntax tree now retain location information for longer. Users can now emit optimization information GCC 9.1 can now automatically vectorize loops and reorganize them to work on multiple iterations at once. Users will now have an option, -fopt-info, that will help in emitting optimization information. Improved runtime library in GCC 9.1 This release comes with improved experimental support for C++17, including <memory_resource>. There will also be a support for opening file streams with wide character paths on Windows. Arm specific This release comes with support for the deprecated Armv2 and Armv3 architectures and their variants have been removed. Support for the Armv5 and Armv5E architectures has also been removed. To know more about this news, check out RedHat’s blog post. DragonFly BSD 5.4.1 released with new system compiler in GCC 8 and more The D language front-end support finally merged into GCC 9 GCC 8.1 Standards released!
Read more
  • 0
  • 0
  • 11872
article-image-junit-5-4-released-with-an-aggregate-artifact-for-reducing-your-maven-and-gradle-files
Bhagyashree R
08 Mar 2019
2 min read
Save for later

JUnit 5.4 released with an aggregate artifact for reducing your Maven and Gradle files

Bhagyashree R
08 Mar 2019
2 min read
Last month, the team behind the JUnit framework announced the release of JUnit 5.4. This release allows ordering extensions and test case execution provides an aggregate artifact for slimming your Maven and Gradle files, and more. Some new features in JUnit 5.4 Ordering test case execution JUnit 5.4 allows you to explicitly define a text execution order. To enable tests ordering, you need to annotate the class with the ‘@TestMethodOrder’ extension and also mention the ordering type of either Alphanumeric, OrderAnnotation, or Random. Alphanumeric orders the test execution based on the method name of the test case. For a custom defined execution, you can use the OrderAnnotation order type. To order test cases pseudo-randomly, you can use the Random order type. Extension ordering With this release, you can not only order test case execution but also order how programmatically register extensions are executed. These extensions are registered with @RegisterExtension. You can use this feature in cases where the setup/teardown behavior of a test is complex and has separate domains. For instance, when you are testing the behavior of how a cache and database are used. Aggregate artifact A large number of dependencies were required when using JUnit 5. With this release, the team has changed this by providing the ‘junit-jupiter’ aggregate artifact. The ‘junit-jupiter’ artifact includes ‘junit-jupiter-api’ and ‘junit-jupiter-params’. This artifact collectively covers most of the dependencies we will need when using JUnit 5. It will also help in reducing the size of Maven and Gradle files of projects using JUnit 5. TempDir In JUnit 5.4, the team has added @TempDir as a native feature of the JUnit framework, which was originally a part of the JUnit-Pioneer third-party library. You can use the @TempDir extension for handling the creation and cleanup of temporary files. TestKit With TestKit, you can perform a meta-analysis on a test suite. It allows you to check the number of executed tests, passed tests, failed tests, skipped tests, as well as a few other behaviors. To read the full list of updates in JUnit 5.4, check out the official announcement. Apache NetBeans IDE 10.0 released with support for JDK 11, JUnit 5 and more! JUnit 5.3 brings console output capture, assertThrow enhancements and parallel test execution Unit testing with Java frameworks: JUnit and TestNG [Tutorial]  
Read more
  • 0
  • 0
  • 3174

article-image-notepad-drops-code-signing-for-its-releases-from-version-7-6-4-onwards
Bhagyashree R
08 Mar 2019
3 min read
Save for later

Notepad++ drops code-signing for its releases from version 7.6.4 onwards

Bhagyashree R
08 Mar 2019
3 min read
On Wednesday, Don Ho, Notepad++ developer announced the release of Notepad++ 7.6.4. He also shared that from this release onwards, users will not see the blue-trusted User Access Control (UAC) popup as Notepad++ has dropped code signing for its releases. UAC is a Windows security feature which helps prevent unauthorized changes to operating systems. Why Notepad++ decided to drop code-signing for its releases? DigiCert, a US-based X.509 SSL certificate authority, donated a three years code signing certificate to Notepad++ in 2016, which has now expired. Now when Don Ho was trying to repurchase a new certificate from Certum, a Certification Authority, he was required to mention a Common Name (CN). The problem here is that as Notepad++ is not a company or organization, Certum did not allow him to use Notepad++ as CN. Additionally, he also feels that these code-signing certificates are too overpriced. He added in the blog post, “Notepad++ has done without a certificate for more than 10 years, I don’t see why I should add the dependency now (and be an accomplice of this overpricing industry). I decide to do without it.” This sparked a discussion on Hacker News, and many users supported the developer’s decision. One of the users commented, “Well I don't care if the developer paid the certificate, and I don't see why someone that develops FOSS should pay money for something that doesn't bring to him any of that money back. At least for open source software certificates should be offered for free, in my opinion.” Don Ho mentioned in the announcement that this decision will not have any effect on Notepad++ security whatsoever, but it will be less flexible from before: As always, every release will come with SHA256 hash of the installed and other packages. The SHA256 hash of all components such as ‘SciLexer.dll’, ‘GUP.exe’, and ‘nppPluginList.dll’ will be checked by Notepad++ Markdown support was planned to land in Notepad++ 7.6.3 version, but the needed file wasn’t deployed correctly by the installer. This bug is now fixed in Notepad++ 7.6.4. Additionally, this release fixes a few vulnerable issues and some crash bugs identified in the European Commission's Free and Open Source Software Auditing Bug Bounty program. To read the original announcement, visit Notepad++’s official website. EU to sponsor bug bounty programs for 14 open source projects from January 2019 Browser based Visualization made easy with the new P5.js 5 Reasons to learn programming
Read more
  • 0
  • 0
  • 2220