Linux Kernel Keepers Mull In-Tree Support for Rust – InApps is an article under the topic Software Development Many of you are most interested in today !! Today, let’s InApps.net learn Linux Kernel Keepers Mull In-Tree Support for Rust – InApps in today’s post !
Read more about Linux Kernel Keepers Mull In-Tree Support for Rust – InApps at Wikipedia
You can find content about Linux Kernel Keepers Mull In-Tree Support for Rust – InApps from the Wikipedia website
While this is not the first time the topic of Rust in the Linux kernel has surfaced, the internet this week is awash in twitterings and rumblings that the time has finally come. It all started with a thread on the Linux Kernel mailing list where software developer Nick Desaulniers, who works on compiling the Linux Kernel with Clang (and LLVM) proposed the idea of running a session on support for Rust “in tree” at an upcoming Linux Plumbers Conference. While the idea has been floated before, what has everyone, according to an article at Hackaday, asking if 2020 will be the year of Rust in the Linux kernel is the fact that Linux creator Linus Torvalds responded seemingly in favor of the idea.
“The interesting part is [Linus Torvalds]’s response on the LKML thread, which leaves everyone hoping for a hearty signature Rust rant akin to his C++ one disappointed,” they write. “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.”
Sounds like you’re dragging your feet a little, 4-5 days seems like sufficient time.
— Joseph Lyons (@MyDeathMachine) July 12, 2020
An article over at The Register takes a deeper dive into the topic, noting that Microsoft recently cited Rust as the “the best alternative to C and C++ currently available” — a topic we’ve surely touched on before — with memory safety being the primary benefit of Rust over the others.
For further support of the topic, another blog post crossed the feeds this week, this one exclaiming that Rust is surprisingly good as a server language. While it is not, in any way, directly addressing the topic of Rust and Linux, the author’s conclusion adds a little thought to the overall idea of Rust as a systems language:
Would I recommend someone write their next server in Rust? No. The ecosystem is not quite there yet, and most servers are still going to be I/O bound, so the speed gains probably aren’t going to matter that much,” they write. “BUT, once the ecosystem matures, honestly I think Rust is a great language to write servers in. You get the speed, and the safety, and honestly you don’t pay the same price you normally do fighting (or at least thinking of) the borrow checker.
it’s nonbinary visibility day and my pronouns are /dev/null
— Ian Coldwater (@IanColdwater) July 14, 2020
This Week in Programming
- If The Idea Of Helping Design Rust Appeals To You…Then you might want to head on over to the Rust blog again this week to read all about the path to membership of the language’s lang team, the team behind designing and implementing new language features. The post offers a list of expectations for a potential team member — such as leading project groups or participating in RFC discussions — and highlights a “path to membership” with steps such as being involved in individual project groups and resolving technical disputes “in a productive way.” While this is one focus of the blog post, the Rust team writes that it is all in an effort to address a different issue. “In short, the idea is that we are trying to ‘intercept’ the RFC process earlier by introducing a “pre-step” called a Major Change Proposal (MCP),” they write. “The idea is that if you have an idea you’d like to pursue, you can file an MCP issue and describe the high-level details. If the idea catches the eye of somebody within the team, we will create a project group to pursue the idea, with that member serving as the lang team liaison and you (or others) serving as the group lead.” Essentially, the effort here is to recruit more people to staff this process and make language development smoother — and they want your help.
- Android & Kotlin for the Noobs: It’s been a while now since Kotlin left behind its underdog status and became the officially backed language for Android development, and now Google has launched some courses for prospective developers to learn Android and Kotlin with no programming experience. Following their 2016 release of their Android Basics curriculum, Google is now launching Android Basics in Kotlin, “a new online course for people without programming experience to learn how to build Android apps.” The course offers step-by-step instructions on how to use Android Studio to build apps, as well as how to run them on an Android device (or virtual device), along with hands-on practice to learn the fundamentals. The course is completely free, and the first unit is immediately available with more to follow.
- PHP Support on Windows Officially Ends: InfoWorld brings us the story of the end of the line for PHP on Windows, citing a message that says Microsoft will not be producing an official build of PHP 8 for Windows. According to the story, Microsoft has been delivering Windows releases as binaries and source code on windows.php.net for IIS and other Windows Web servers, but that will be coming to an end. Nonetheless, they write, “PHP for Windows will not disappear. It’s very clear that there’s more than enough demand for someone to continue building and distributing a Windows version of PHP beyond PHP 7.” Rather, it’s just that “Microsoft won’t directly contribute resources and servers for the builds, but more than likely, it will donate licenses and servers to the PHP project.”
C++: An absolute powerhouse
Python: Simple but beautiful and powerful
Java: Enterprise language
— Raf Rasenberg (@rafrasenberg) July 16, 2020
- Archiving In the Arctic: Less on the practical end of things and more on the “huh, that’s cool” spectrum, GitHub offers us a view into the journey of the world’s open source code to the Arctic. The mission of the GitHub Archive Program along with the GitHub Arctic Code Vault, they write, is “to preserve open source software for future generations by storing your code in an archive built to last a thousand years” and this week sees the arrival of 21 terabytes of open source code repositories written on 186 reels of piqlFilm (digital photosensitive archival film) to the arctic. Oh, and if you happened to get code included in the archive, you’ll get a nifty new badge on GitHub!
— Guy Barrette (@GuyBarrette) July 14, 2020
Feature image by Vince Veras on Unsplash.
At this time, InApps does not allow comments directly on this website. We invite all readers who wish to discuss a story to visit us on Twitter or Facebook. We also welcome your news tips and feedback via email: [email protected].
Let’s create the next big thing together!
Coming together is a beginning. Keeping together is progress. Working together is success.