Language Selection

English French German Italian Portuguese Spanish

Programming Leftovers

Filed under
Development
  • What’s happening in the Node.js community

    Curious about what’s going on in the Node.js community?

    Node.js 16 will be released in April 2021 and promoted to long-term support in October 2021. We’re also rapidly approaching the end-of-life date for Node.js 10. After April 2021, there will be no further patches or security fixes made available for the Node.js 10 release line. If you haven’t already, you should plan to upgrade to Node.js 12 or Node.js 14 as soon as possible. See the Node.js release schedule in Figure 1.

  • Edge computing optimization with open source technologies

    Optimizing Java code using Quarkus (an open source, Kubernetes-native Java framework) can help reduce runtime memory requirements by an order of magnitude while dropping initial startup times from seconds to milliseconds.

    Low startup times reduce infrastructure usage by making it practical to scale down significantly when an application or process is idle. Longer startup times necessitate an application or process remaining continuously "hot," executing in-memory and using resources even when idle.

  • Build even faster Quarkus applications with fast-jar - Red Hat Developer

    Quarkus is already fast, but what if you could make inner loop development with the supersonic, subatomic Java framework even faster? Quarkus 1.5 introduced fast-jar, a new packaging format that supports faster startup times. Starting in Quarkus 1.12, this great feature became the default packaging format for Quarkus applications. This article introduces you to the fast-jar format and how it works.

  • HPy: a better C API for Python?

    There are other efforts to improve the C API, notably, Victor Stinner's PEP 620 ("Hide implementation details from the C API"), but those have generally been incremental improvements, with the intent of keeping the existing extensions working. In some sense HPy is similar, because it does not seek to replace the existing API, at least anytime soon. But the project does seek to make sweeping changes to the API in pursuit of its goals.

    The current Python C API is closely tied to the CPython implementation of the language, which is part of what makes it hard to adapt the API to other implementations, such as PyPy. The C API effectively embeds the reference-counting garbage collector into the language extensions, which means that alternative garbage-collecting approaches cannot be used (or only used painfully) when trying to run those extensions. It also holds back CPython because it is well-nigh impossible to, for example, remove or alter the global interpreter lock (GIL) without changing the API, thus requiring changes to the extensions.

    So HPy seeks to provide a more streamlined C API that is not intimately tied to CPython, but that can run extensions with the same performance as those that use the existing API. Extensions written to use HPy will be "much faster" on alternatives like PyPy or Python on GraalVM, according to the home page. HPy also provides a way to build "universal binaries" for extensions that will run unmodified on various Pythons, and a "debug mode" that is intended to catch common mistakes made in extensions.

    [...]

    In addition, HPy adds an explicit context parameter (an HPyContext) for each call in order to explicitly manage the local state of the interpreter. It is meant to allow future versions where different threads each have their own interpreter or a process contains multiple interpreters (such as different versions or implementations). It also allows current features like the universal binaries.

    [...]

    The ideas behind HPy seem sound, but it is a sprawling project that will require a great deal of development effort to get far. The existing Python C API has hampered a number of initiatives for Python, while, of course, that same API has contributed greatly to the huge and growing ecosystem around the language. In particular, though, projects aimed at improving the performance of Python tend to run aground on the need to support the API. HPy looks like a project to keep an eye on to see how things might change in that area down the road.

  • dLeyna updates and general project things

    As for all the other things I do. I was trying to write many versions of this blog post and each one sounded like an apology, which sounded wrong. Ever since I changed jobs in 2018 I’m much more involved in coding during my work-time again and that seems to suck my “mental code reservoir” dry, meaning I have very little motivation to spend much time on designing and adding features, limiting most of the work on Rygel, GUPnP and Shotwell to the bare minimum. And I don’t know how and when this might change.

  • Qt for MCUs 1.8 released

    A new feature update of Qt for MCUs is now available. Download version 1.8 to get access to additional MCU platforms, more options to limit the memory footprint, new APIs to create advanced and scalable user interfaces, and a solution to simplify the integration of Qt into existing projects.

    Newcomers can get a free evaluation here, while others can run the Qt Installer to update to the latest version.

    The full list of changes included in version 1.8 can be found in the changelog in the online documentation. Continue reading for more information on the content of this release.

  • GCC 10.3 Compiler Released With AMD Zen 3 Tuning Backported, Nearly 200 Bug Fixes - Phoronix

    GCC 10.3 is out today as the latest stable release of the GNU Compiler Collection, weeks ahead of the GCC 11.1 feature release as the first stable version of GCC 11.

    GCC 10.3 back-ports various fixes to the GCC 10 stable series, which was minted last year. The brief release announcement for the GCC 10.3 compiler notes 178 bug fixes over the GCC 10.2 release from a half-year ago.

  • LLVM 12.0 Delays Drag On With RC5 Now Shipping - Phoronix

    LLVM 12.0 was supposed to ship at the start of March but now more than one month later and some 6,660+ commits to LLVM 13.0 already, LLVM 12.0 has not yet shipped but on Wednesday 12.0.0-rc5 was issued.

    Lingering bugs keep holding back the LLVM 12.0 release. The delay of more than one month is significant in that LLVM traditionally operates on a half-year release cadence and this code for v12.0 was branched all the way back towards the end of January, thus the 6k+ commits already accumulating for LLVM 13.0 this autumn.

  • A swarm in May is worth a load of hay, is it? JetBrains Code With Me collaborative programming tool released • The Register

    JetBrains today pushed out Code With Me, formerly in preview, a plugin to support remote collaborative coding, as well as updates to its Java and Ruby IDEs.

    All the JetBrains IDEs are based on IDEA, a Java IDE, but the range is extensive and includes adaptions for Android (Java and Kotlin), Python, JavaScript, PHP, C#, C/C++, Ruby, and more. Google's Android Studio is based on the free Community Edition of IDEA.

    Code With Me lets two or more developers work in the same IDE using a remote connection. JetBrains competes with Microsoft's free Visual Studio Code, as well as Visual Studio, and the new feature is somewhat similar to Microsoft's Live Share, which supports collaborative coding, debugging and audio calls, with a web client in preparation.

  • IBM Creates a COBOL Compiler For Linux On x86

    IBM has announced a COBOL compiler for Linux on x86. "IBM COBOL for Linux on x86 1.1 brings IBM's COBOL compilation technologies and capabilities to the Linux on x86 environment," said IBM in an announcement, describing it as "the latest addition to the IBM COBOL compiler family, which includes Enterprise COBOL for z/OS and COBOL for AIX."

  • IBM COBOL for Linux on x86 1.1 brings COBOL capabilities to the Linux on x86 environment
  • Short Topix: New Linux Malware Making The Rounds: Despite Age, COBOL Remains Productive, Useful

    Despite getting its start in 1959, the COBOL computer language remains useful and productive nearly 62 years later. Partly based on Cmdr Grace Hopper's FLOW-MATIC language, COBOL (which stands for "common business-oriented language) has found a home on many mainframe computers. But, because of its age, COBOL doesn't attract the developers the way it used to, back in the 60s, 70s, and 80s.

    According to an article on TechRepublic, COBOL proved its value during the COVID-19 pandemic. Originally designed to handle large volumes of transactions and generate reports in the business world, its 220 billion lines of code would likely cost at least between $4 and $8 TRILLION to replace. And replace it with what?

    Most of the COBOL systems exist in the back offices of banks, insurance companies, brokerages, and government offices, continually churning out massive amounts of transactions quickly and efficiently. Many retail giants, such as Walmart, Home Depot, Target and many others, rely on COBOL running on mainframes to process point of sale credit card transactions. Replacing these massive software systems would be risky, as well. After 60 years, COBOL has these tasks handled. Easily.

    The COBOL language is very structured and the machines it runs on are typically fairly easy to maintain. COBOL's usefulness shined through in its use by various government agencies, who still rely on it to process large numbers of unemployment benefits. During the pandemic, the numbers of those seeking unemployment benefits exploded. So, the need for those mainframes that process those unemployment benefits soared right along with the exploding demand for unemployment benefits.
    Many of the programmers trained in COBOL are starting to reach retirement age, so the demand for COBOL programmers is rising. The median income for COBOL programmers is just over $92K per year, and those with 10 years or more of COBOL programming experience can expect wages around $100K per year. Those are not-too-shabby wages for knowing how to work with a 60+ year-old programming language.

  • Run one specific clang-tidy check on your entire codebase

    Recently I did a major refactor on a piece of code that involved thousands of lines of code which were in one way or another related to string handling. All of the code handled char* (C style character pointer arrays) and the concept of const or ownership was literally unknown in that part of the codebase. The refactored code uses std::string's, but due to the legacy nature, a large number of methods returned nullptr's instead of empty strings (like ""). I understand why this was done, but finding all those instances and the fact it only gives a runtime error was a bit of a bummer.

    Luckily clang-tidy is here to save the day. In my IDE, CLion, it gives a warning when you return a nullptr. It however does that only in the file you're currently editing, and since we're talking millions of files, I wasn't going to open them by hand. You can run clang-tidy easily on one file, and it's not hard to run it on an entire codebase as well, using the script run-clang-tidy.py, provided in their packages.

  • Update on git.php.net incident

    The following is a more detailed explanation of what happened and which actions were taken.

    When the first malicious commit was made under Rasmus' name, my initial reaction was to revert the change and revoke commit access for Rasmus' account, on the assumption that this was an individual account compromise. In hindsight, this action didn't really make sense, because there was (at the time) no reason to believe that the push occurred through Rasmus' account in particular. Any account with access to the php-src repository could have performed the push under a false name.

    When the second malicious commit was made under my own name, I reviewed the logs of our gitolite installation, in order to determine which account was actually used to perform the push. However, while all adjacent commits were accounted for, no git-receive-pack entries for the two malicious commits were present, which means that these two commits bypassed the gitolite infrastructure entirely. This was interpreted as likely evidence of a server compromise.

  • PHP project says security hiccup likely due to leak of main database
  • GNU Guix: Outreachy 'guix git log' internship wrap-up

    Magali Lemes joined Guix in December for a three-month internship with Outreachy. Magali implemented a guix git log command to browse the history of packaging changes, with mentoring from Simon Tournier and Gábor Boskovits. In this blog post, Magali and Simon wrap up on what's been accomplished.

More in Tux Machines

digiKam 7.7.0 is released

After three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release. Read more

Dilution and Misuse of the "Linux" Brand

Samsung, Red Hat to Work on Linux Drivers for Future Tech

The metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world. Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility. Read more

today's howtos

  • How to install go1.19beta on Ubuntu 22.04 – NextGenTips

    In this tutorial, we are going to explore how to install go on Ubuntu 22.04 Golang is an open-source programming language that is easy to learn and use. It is built-in concurrency and has a robust standard library. It is reliable, builds fast, and efficient software that scales fast. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel-type systems enable flexible and modular program constructions. Go compiles quickly to machine code and has the convenience of garbage collection and the power of run-time reflection. In this guide, we are going to learn how to install golang 1.19beta on Ubuntu 22.04. Go 1.19beta1 is not yet released. There is so much work in progress with all the documentation.

  • molecule test: failed to connect to bus in systemd container - openQA bites

    Ansible Molecule is a project to help you test your ansible roles. I’m using molecule for automatically testing the ansible roles of geekoops.

  • How To Install MongoDB on AlmaLinux 9 - idroot

    In this tutorial, we will show you how to install MongoDB on AlmaLinux 9. For those of you who didn’t know, MongoDB is a high-performance, highly scalable document-oriented NoSQL database. Unlike in SQL databases where data is stored in rows and columns inside tables, in MongoDB, data is structured in JSON-like format inside records which are referred to as documents. The open-source attribute of MongoDB as a database software makes it an ideal candidate for almost any database-related project. This article assumes you have at least basic knowledge of Linux, know how to use the shell, and most importantly, you host your site on your own VPS. The installation is quite simple and assumes you are running in the root account, if not you may need to add ‘sudo‘ to the commands to get root privileges. I will show you the step-by-step installation of the MongoDB NoSQL database on AlmaLinux 9. You can follow the same instructions for CentOS and Rocky Linux.

  • An introduction (and how-to) to Plugin Loader for the Steam Deck. - Invidious
  • Self-host a Ghost Blog With Traefik

    Ghost is a very popular open-source content management system. Started as an alternative to WordPress and it went on to become an alternative to Substack by focusing on membership and newsletter. The creators of Ghost offer managed Pro hosting but it may not fit everyone's budget. Alternatively, you can self-host it on your own cloud servers. On Linux handbook, we already have a guide on deploying Ghost with Docker in a reverse proxy setup. Instead of Ngnix reverse proxy, you can also use another software called Traefik with Docker. It is a popular open-source cloud-native application proxy, API Gateway, Edge-router, and more. I use Traefik to secure my websites using an SSL certificate obtained from Let's Encrypt. Once deployed, Traefik can automatically manage your certificates and their renewals. In this tutorial, I'll share the necessary steps for deploying a Ghost blog with Docker and Traefik.