To the first point, many people seem unaware that POSIX is an actual set of standards - IEEE 1003.1 in several variations, plus descendants. These standards cover a lot more than just operations on files, and technically "POSIX" only refers to systems that have passed a set of conformance tests covering all of those. Nonetheless, people often use "POSIX" to mean only the section dealing with file operations, and only in a loose sense of things that implement something like the standard without having been tested against it. Many systems, notably including Linux, pretty explicitly do not claim to comply with the actual standard.
A few days ago, Ned Batchelder's post on deleting code made the rounds on HN, even though it was originally written in 2002. Here I want to echo a few of Ned's points, and take a stronger stance than he did: delete code as soon as you know you don't need it any more, no questions asked. I'll also offer some tips from the trenches for how to identify candidate dead code.
This is the first in a series on eating your vegetables in software engineering, on good, healthy practices for a happy and successful codebase. I don't (yet) know how long the series will be, so please stay tuned!
Developers are leaking access tokens for Slack widely on GitHub, in public repositories, support tickets and public gists. They are extremely easy to find due to their structure. It is clear that the knowledge about what these tokens can be used for with malicious intent is not on top of people’s minds…yet. The Detectify team shows the impact, with examples, and explains how this could be prevented.
When Samsung started releasing Edge devices last year, people were pretty excited as to what the dual curved displays can add to the user experience, However, some were pretty disappointed as you couldn’t do that much with them except to see color-coded notifications and other minor things. But with the release of the Samsung Galaxy S7 Edge this year, plus the Android 6.0 Marshmallow update, users were able to get a bit more out of the display. An open-source project now lets you control your music player from the edge display.
The Edge panel created by XDA developer hymxdev will work for Samsung devices that of course have the Edge display, including the Galaxy S6 Edge, S6 Edge Plus, S7 Edge, and even the Galaxy Note 5, if the Edge screen feature is enabled in the phablet. It will let you control your music player without having to open the app itself. All you have to do is install the app and then use the Edge display to Play/Pause, Next track, Previous track, etc. What you can do also depends on the music player you’re using.
The entire essay continues on a similar note. Although the title implies this is a rant about Ubuntu and Debian, he seems to paint the entirety of Linux Land with the same broad brush. And that would be factually wrong.
"Factually wrong" doesn't mean he hasn't pointed out some serious problems. He has. I and many other Linux users see the same problems he identifies. What's "factually wrong" is that these problems are built into the combination of kernel, system software, and applications generally called either "Linux" or "GNU/Linux". And his implication that there's no reasonable way for a user to avoid these problems is also factually wrong.
The bottom line of my objection to his essay is this: Nobody should use software they don't like, especially if there's a reasonable alternative. And by extension, why is Linas still using Debian and Ubuntu and systemd and Firefox and Chrome and Gnome? There are reasonable alternatives to every single one of them.