Will 2020 Be The Year Of Rust In The Linux Kernel?

July 15, 2020 by Sven Gregori 55 Comments

One problem with modern programming languages is the reach their overly enthusiastic early adopters have nowadays thanks to the internet. As a result, everyone else’s first encounter with them are oftentimes some crude, fanboyish endeavors to rewrite every single established software project in that shiny new language — just because — which may leave an off-putting taste behind. However, Rust certainly seems to have outgrown this state by now, and with its rising popularity within the general developer population, it’s safe to say it will stick around. Will it fully replace C one day? Probably not, but there’s a big chance for coexistence, and [Nick Desaulniers] got the ball rolling for that within the Linux kernel.

Now, before you storm off pledging your allegiance to C by finding a new operating system: nothing is happening yet. [Nick] simply tested the waters for a possible future of Rust within the Linux kernel code base, which is something he’s planning to bring up for discussion in this year’s Linux Plumbers Conference — the annual kernel developer gathering. The interesting part is [Linus Torvalds]’s respone on the LKML thread, which leaves everyone hoping for a hearty signature Rust rant akin to his C++ one disappointed. Instead, his main concern is that a soft and optional introduction of the support in the build system would leave possible bugs hidden, and therefore should be automatically enabled if a Rust compiler is present — essentially implying that he seems otherwise on board.

We’ll see what comes of it, but with Rust language team lead [Josh Triplett] stating that enhancements benefiting and advancing a kernel integration are certainly imaginable for Rust itself, we might see interesting collaborations coming up in the near future. If you don’t want to wait for that and use Rust already today in a user-land driver, check out this 35c3 talk. And if that doesn’t go far enough for you, here’s a whole (non-Linux) kernel written in Rust.

Don’t Wait, You Need To See Comet NEOWISE Right Now

July 14, 2020 by Tom Nardi 74 Comments

By now you’ve heard of NEOWISE, the most spectacular comet to visit our little corner of the galaxy since Hale-Bopp passed through over 20 years ago. But we’re willing to bet you haven’t actually seen it with your own eyes. That’s because up until now, the only way to view this interstellar traveler was to wake up in the pre-dawn hours; an especially difficult requirement considering a large chunk of the population has gotten used to sleeping-in over the last few months.

But things are about to change as NEOWISE begins a new phase of its trip through our celestial neck of the woods. Having come to within 44.5 million km (27.7 million miles) of the sun on July 3rd, the comet is now making its way back out of our solar system. Thanks to the complex dance of the heavens, that means that observers in the Northern Hemisphere will now be able to see NEOWISE in the evening sky just above the horizon.

NEOWISE is on a kind of “up and over” trajectory compared to the orbital paths of the planets. Get a better feel for it with JPL’s interactive solar dynamics tool.

While NEOWISE might be beating a hasty retreat from Sol right now, the comet it actually getting closer to us in the process. On July 22nd it will reach perigee, that is, the point in its orbit closest to Earth. On that evening the comet will be approximately 103 million km (64 million miles) away. Not exactly a stone’s throw, but pretty close in astronomical terms. The comet will appear to be getting higher in the sky as it approaches Earth, and should be visible with the naked eye between 10 and 20 degrees above the northern horizon.

Most estimates say that NEOWISE should remain visible until at least the middle of August, though it will be dimming rapidly. After that, you’re going to have to wait awhile for a repeat showing. Given the orbit of this particular comet, it won’t come around our way again for approximately 6,800 years, give or take a few lifetimes.

NASA will be hosting a NEOWISE live stream tomorrow afternoon where researchers will answer questions about this once in a lifetime celestial event, though we think you’ll get a lot more out of it if you just go outside and look up.

The Segway Is Dead, Long Live The Segway

June 30, 2020 by Tom Nardi 87 Comments

Before it was officially unveiled in December 2001, the hype surrounding the Segway Human Transporter was incredible. But it wasn’t because people were excited to get their hands on the product, they just wanted to know what the thing was. Cryptic claims from inventor Dean Kamen that “Ginger” would revolutionize transportation and urban planning lead to wild speculation. When somebody says their new creation will make existing automobiles look like horse-drawn carriages in comparison, it’s hard not to get excited.

There were some pretty outlandish theories. Some believed that Kamen, a brilliant engineer and inventor by all accounts, had stumbled upon some kind of anti-gravity technology. The kids thought they would be zipping around on their own Back to the Future hover boards by Christmas, while Mom and Dad were wondering what the down payment on a floating minivan might be. Others thought the big secret was the discovery of teleportation, and that we were only a few years out from being able to “beam” ourselves around like Captain Kirk.

Even in hindsight, you really can’t blame them. Kamen had the sort of swagger and media presence that we today associate with Elon Musk. There was a general feeling that this charismatic maverick was about to do what the “Big Guys” couldn’t. Or even more tantalizing, what they wouldn’t do. After all, a technology which made the automobile obsolete would change the world. The very idea threatened a number of very big players, not least of which the incredibly powerful petroleum industry.

Of course, we all know what Dean Kamen actually showed off to the world that fateful day nearly 20 years ago. The two-wheeled scooter was admittedly an impressive piece of hardware, but it was hardly a threat to Detroit automakers. Even the horses were largely unconcerned, as you could buy an actual pony for less than what the Segway cost.

Now, with the announcement that Segway will stop production on their eponymous personal transporter in July, we can confidently say that history will look back on it as one of the most over-hyped pieces of technology ever created. But that’s not to say Kamen’s unique vehicle didn’t have an impact. Continue reading “The Segway Is Dead, Long Live The Segway” →

Does PHP Have A Future, Or Are Twenty Five Years Enough?

June 29, 2020 by Ben James 54 Comments

In June, 1995, Rasmus Lerdorf made an announcement on a Usenet group. You can still read it.

Today, twenty five years on, PHP is about as ubiquitous as it could possibly have become. I’d be willing to bet that for the majority of readers of this article, their first forays into web programming involved PHP.

Announcing the Personal Home Page Tools (PHP Tools) version 1.0.

These tools are a set of small tight cgi binaries written in C.

But no matter what rich history and wide userbase PHP holds, that’s no justification for its use in a landscape that is rapidly evolving. Whilst PHP will inevitably be around for years to come in existing applications, does it have a future in new sites?

Continue reading “Does PHP Have A Future, Or Are Twenty Five Years Enough?” →

What’s The Deal With Snap Packages?

June 24, 2020 by Tom Nardi 151 Comments

Who would have thought that software packaging software would cause such a hubbub? But such is the case with snap. Developed by Canonical as a faster and easier way to get the latest versions of software installed on Ubuntu systems, the software has ended up starting a fiery debate in the larger Linux community. For the more casual user, snap is just a way to get the software they want as quickly as possible. But for users concerned with the ideology of free and open source software, it’s seen a dangerous step towards the types of proprietary “walled gardens” that may have drove them to Linux in the first place.

Perhaps the most vocal opponent of snap, and certainly the one that’s got the most media attention, is Linux Mint. In a June 1st post on the distribution’s official blog, Mint founder Clement Lefebvre made it very clear that the Ubuntu spin-off does not approve of the new package format and wouldn’t include it on base installs. Further, he announced that Mint 20 would actively block users from installing the snap framework through the package manager. It can still be installed manually, but this move is seen as a way to prevent it from being added to the system without the user’s explicit consent.

The short version of Clement’s complaint is that the snap packager installs from a proprietary Canonical-specific source. If you want to distribute snaps, you have to set up an account with Canonical and host it there. While the underlying software is still open source, the snap packager breaks with long tradition of having the distribution of the software also being open and free. This undoubtedly makes the install simple for naive users, and easier to maintain for Canonical maintainers, but it also takes away freedom of choice and diversity of package sources.

Continue reading “What’s The Deal With Snap Packages?” →

Ask Hackaday: Are 80 Characters Per Line Still Reasonable In 2020?

June 18, 2020 by Sven Gregori 186 Comments

Software developers won’t ever run out of subjects to argue and fight about. Some of them can be fundamental to a project — like choice of language or the programming paradigm to begin with. Others seem more of a personal preference at first, but can end up equally fundamental on a bigger scale — like which character to choose for indentation, where to place the curly braces, or how to handle line breaks. Latest when there’s more than one developer collaborating, it’s time to find a common agreement in form of a coding style guide, which might of course require a bit of compromise.

Regardless of taste, the worst decision is having no decision, and even if you don’t agree with a specific detail, it’s usually best to make peace with it for the benefit of uniformly formatted code. In a professional environment, a style guide was ideally worked out collaboratively inside or between teams, and input and opinions of everyone involved were taken into consideration — and if your company doesn’t have one to begin with, the best step to take is probably one towards the exit.

The situation can get a bit more complex in open source projects though, depending on the structure and size of a project. If no official style guide exists, the graceful thing to do is to simply adopt the code base’s current style when contributing to it. But larger projects that are accustomed to a multitude of random contributors will typically have one defined, which was either worked out by the core developers, or declared by its benevolent dictator for life.

In case of the Linux kernel, that’s of course [Linus Torvalds], who has recently shaken up the community with a mailing list response declaring an overly common, often even unwritten rule of code formatting as essentially obsolete: the 80-character line limitation. Considering the notoriety of his rants and crudeness, his response, which was initiated by a line break change in the submitted patch, seems downright diplomatic this time.

[Linus]’ reasoning against a continuing enforcement of 80-char line limits is primarly the fact that screens are simply big enough today to comfortably fit longer lines, even with multiple terminals (or windows) next to each other. As he puts it, the only reason to stick to the limitation is using an actual VT100, which won’t serve much use in kernel development anyway.

Allowing longer lines on the other hand would encourage the use of more verbose variable names and whitespace, which in turn would actually increase readability. Of course, all to a certain extent, and [Linus] obviously doesn’t call for abolishing line breaks altogether. But he has a point; does it really make sense to stick to a decades old, nowadays rather arbitrary-seeming limitation in 2020?

Continue reading “Ask Hackaday: Are 80 Characters Per Line Still Reasonable In 2020?” →

Justice For The Gatwick Two: The Final Chapter In The British Drone Panic Saga

June 17, 2020 by Jenny List 27 Comments

At the end of 2018, a spate of drone sightings caused the temporary closure of London Gatwick Airport, and set in train a chain of events that were simultaneously baffling and comedic as the authorities struggled to keep up with both events and the ever widening gap in their knowledge of the subject.

One of the more inept actions of the Sussex Police was to respond by arresting the first local drone enthusiast they could find on Facebook, locking up a local couple for 36 hours and creating a media frenzy by announcing the apprehension of the villains before shamefacedly releasing them without charge.

In a final twist to the sorry saga, the couple have sued the force for wrongful arrest and false imprisonment, for which the cops have had to make a £200,000 ($250,117) payout including legal fees.

We reported extensively on the events surrounding the case 18 months ago, and then on a follow-up event at London Heathrow airport. The mass media at the time were full of the official line that drone hobbyists must be at fault, but then as now we were more interested in seeing some hard evidence. As we said then: Show us the drone.

So how has the new drone law progressed, since it was decided that Something Must Be Done? Enthusiasts have continued as before, and the multirotor community is as technically creative as ever. We were fortunate enough to host the Lets Drone Out podcast at MK Makerspace back in those halcyon days before the pandemic and see the state of the art in sub-250g craft, and with those and commercial offerings such as the DJI Mavic Mini all requiring no registration there is increasingly little need for an enthusiast to purchase a larger machine. The boost to the British drone industry we were promised has instead been a boost for the Chinese industry as we predicted, and of course we’re still waiting for the public inquiry into the whole mess. Something tells us Hell will freeze over first.

If you’d like the whole backstory in a convenient and entertaining video format, can we direct you to this talk at CCCamp 2019.

Thanks [Stuart Rogers] for the tip.

Keystone Kops header image: Mack Sennett Studios [Public domain].