GTK: At the Heart of GNOME

GTK is at the heart of the GNOME application and software development kit. GTK is used to create graphical user interfaces (GUIs) for desktop environments, applications, and window managers. Since the GTK 4 development process began in 2016, we have about 250 individual contributors, with more than 100 active this year. Thanks to the funding received by the GNOME Foundation in 2020, the GTK development team was able to run hackfests, including one we were lucky enough to have at FOSDEM. This funding also supported Emmanuele Bassi, Core GTK Developer at the GNOME Foundation, working on GTK full-time. For most of 2020, Emmanuele worked on implementing a new accessibility interface for GTK 4, to ensure that more people can use GNOME applications, including those with disabilities. We are building a diverse and sustainable free software computing ecosystem where everyone can be empowered by technology they trust. Since Emmanuele works directly for the Foundation he’s uniquely able to focus on the needs of the community, project, and users to support these goals. GTK is a project with a long history, and throughout that history, it has gone through multiple iterations. A new major release is on the horizon. After four years of development that included a complete overhaul of the internals of the toolkit, GTK 4 promises to be faster through hardware acceleration; more efficient, in terms of performance and power consumption; and more ergonomic, for both application developers, and end users. Over the past four years, the GTK team has continued work on the existing stable versions of GTK and put out multiple releases. Also: GTK Planning More Improvements In 2021 From Better Accessibility To Animation Framework

Platform exclusivity, DRM, and independent authors: A cautionary tale

Imagine, for the sake of argument, that you wrote a book. You've worked on it for years, and you want to share it with the world. You want to reach as many people as possible, but it would be nice to be compensated for your hard work. How many weekends did you spend at home, polishing your manuscript instead of going out with friends? How many sleepless nights have you spent staring at a blank page, looking for inspiration? While researching the best way to publish, you hear horror stories about authors finding their books sold on counterfeit Web sites or distributed gratis without the author's consent. You read stories about authors feeling violated as their hard work is stolen in such a way. As you read about these activities, you also see mentions of companies that claim that they would protect your work against it. Should you publish your book through them, your book would only be available through their application. People could only access it through their store, and they wouldn't even be able to open the file on a device that isn't vetted by the company. The app is very popular, so most people use it anyway, and authors do not have to worry about a lack of interest. Only dealing with one store would also make things easier on your end. You won't have to manage different things. They'll even format your book for you. Sounds easy enough, so you take the deal. Weeks pass, and you make a few sales. It's by no mean a huge success, but you got a few positive reviews, mostly from family and friends. You keep mentioning your project to everyone you know, and find some limited interest. One day, a friend you hadn't talked to in a while asks about your book. They say that they don't like the app your book requires, and they don't want to buy it through the one store you signed an exclusivity deal with. They explain that Digital Restrictions Management (DRM) restricts their freedom to read the book on their device of choice, and won't even let them make backups of the file. They tell you how they once used a similar app, but were locked out of all the books they purchased after moving away from said application. After hearing your friend's story, you decide to give them a DRM-free copy of your book. After all, you wrote it so people would enjoy it first and foremost, and you want your friend to see the fruit of your labor.

Open Hardware: Raspberry Pi, Arduino and RISC-V

• Raspberry Pi 400 kit ships with 7-inch or 13.3-inch touchscreen display

  The Raspberry Pi Foundation has recently launched the Raspberry Pi 4 keyboard computer with impressive performance thanks to a well-designed cooling solution, and I think it’s a great tool for kids (and adults) who may want to carry a Raspberry Pi around. 

• Shutdown button with Raspberry PI and Python - peppe8o

  Because of their low price, mini button switches are useful for many purposes. We have already analyzed how they work (ref. Using mini Switch Button with Raspberry PI and Python) and a funny use case (ref. Reaction Game (v2) with Raspberry PI and Mini Button Switch).

• Arduino Blog » This remote-controlled storytelling apparatus is made up of Arduino-driven toy animatronics

  As an exhibit at the Phaneo Science Center in Wolfsburg, Germany, Niklas Roy and Felix Figus created a remotely-operated storytelling apparatus dubbed “Smart Fairy Tale.” When initiated, a little red ball rolls down the installation’s transparent tubing, triggering different interactions based on the interruption of light sensors along its path. 25 Arduino Nanos are used to control each individual animatronic part of the “story,” making the code manageable and allowing the overall machine to still work if there’s a malfunction in one section.

• Pine64's PINECIL RISC-V soldering iron launched for $25

  We’ve previously mentioned PINECIL RISC-V soldering iron during Pine64’s release of PineCube open-source IP camera development kit, and the good news is the soldering iron is now available for $24.99 on Pine64 store together with optional sets of gross or fine soldering tips compatible with the one used with TS100 model The soldering iron is powered by GigaDevice GD32VF103TB 32-bit RISC-V general-purpose microcontroller and features a small display and two buttons for user interaction, as well as changeable tips.

Linux READFILE System Call Revived Now That It Might Have A User

Earlier this year we mentioned Greg Kroah-Hartman working on a new READFILE system call. The goal of this new syscall is for reading small and medium files more efficiently by having one call to read a file straight into a buffer without having to use the separate open/read/close system calls. It's looking like that system call is back on the table and could be mainlined now that there's a possible user. The READFILE system call is simple for reading lightweight files straight into a buffer without the overhead of multiple system calls that in turn can help performance, especially if reading many files such as on sysfs/debugfs and the like. It had been a number of months without any updates on that syscall and it wasn't mainlined in the cycles since it was proposed earlier this year. But now it looks like it's back on the table.