<?xml version="1.0" encoding="utf-8" ?><rss version="2.0"><channel><title>Bing: Rust Pemrograman</title><link>http://www.bing.com:80/search?q=Rust+Pemrograman</link><description>Search results</description><image><url>http://www.bing.com:80/s/a/rsslogo.gif</url><title>Rust Pemrograman</title><link>http://www.bing.com:80/search?q=Rust+Pemrograman</link></image><copyright>Copyright © 2026 Microsoft. All rights reserved. These XML results may not be used, reproduced or transmitted in any manner or for any purpose other than rendering Bing results within an RSS aggregator for your personal, non-commercial use. Any other use of these results requires express written permission from Microsoft Corporation. By accessing this web page or using these results in any manner whatsoever, you agree to be bound by the foregoing restrictions.</copyright><item><title>A grand vision for Rust | Lobsters</title><link>https://lobste.rs/s/xhoyg7/grand_vision_for_rust</link><description>But in my opinion, Rust has done a great job of folding these technical and academic concepts into simple and intuitive language-level constructs. You don't have to think about monads or applicative functors to get value out of the patterns and concepts they provide.</description><pubDate>Sun, 19 Apr 2026 02:34:00 GMT</pubDate></item><item><title>Announcing Rust 1.85.0 and Rust 2024 | Lobsters</title><link>https://lobste.rs/s/zsngat/announcing_rust_1_85_0_rust_2024</link><description>One thing I've always wondered is why Rust doesn't use major version increments for major editions like this? The only thing I can think of is the residual fear of the Python 2 -&gt; 3 jump. Or do they just not use semver?</description><pubDate>Tue, 31 Mar 2026 09:51:00 GMT</pubDate></item><item><title>Announcing Rust 1.84.0 | Lobsters</title><link>https://lobste.rs/s/mm16it/announcing_rust_1_84_0</link><description>One of the legitimate critiques of Rust (including especially from folks who like Zig, but also more generally) has been that writing safe unsafe Rust has been difficult—unergonomic, difficult to check that you got it right, and generally second-class.</description><pubDate>Mon, 06 Apr 2026 03:11:00 GMT</pubDate></item><item><title>Announcing Rust 1.82.0 | Lobsters</title><link>https://lobste.rs/s/k8qaij/announcing_rust_1_82_0</link><description>Sure, whether Rust is mature, is subjective at the end of the day. Rust hasn't reached my threshold of maturity yet (and I've written a ton of Rust, and seen it grow over the years).</description><pubDate>Mon, 16 Mar 2026 15:53:00 GMT</pubDate></item><item><title>Two Years of Rust | Lobsters</title><link>https://lobste.rs/s/v7lsrv/two_years_rust</link><description>What I'm saying is that Rust exclusively supports the DI approach (more or less) and that the Rust community largely refuses to acknowledge that mocking can be great and actually superior in some cases (perhaps many).</description><pubDate>Tue, 14 Apr 2026 06:14:00 GMT</pubDate></item><item><title>rust - Rust programming | Lobsters</title><link>https://lobste.rs/t/rust</link><description>Stories tagged as rust Rust programming Most often also tagged with performance release plt compilers security linux c web</description><pubDate>Tue, 31 Mar 2026 11:39:00 GMT</pubDate></item><item><title>Rust is Just a Tool | Lobsters</title><link>https://lobste.rs/s/4kticv/rust_is_just_tool</link><description>Rust isn't perfect, but I think it's the currently the best choice for a large subset of software, and I want its adoption to accelerate, so we and our users can have more robust and efficient software.</description><pubDate>Thu, 16 Apr 2026 22:11:00 GMT</pubDate></item><item><title>Prototyping in Rust | Lobsters</title><link>https://lobste.rs/s/atglkw/prototyping_rust</link><description>So today, after spending a bunch of time expanding my test rig to deal with some new stuff in the firmware, I find myself wondering if this prototype would be easier to maintain in rust or if I should have started with Rust as the OP suggests.</description><pubDate>Sat, 28 Mar 2026 12:47:00 GMT</pubDate></item><item><title>Announcing Rust 1.88.0 | Lobsters</title><link>https://lobste.rs/s/llgmmr/announcing_rust_1_88_0</link><description>I have a proc macro in scheme-rs that lets you define Rust functions available to scheme code, and with this change the location of those functions in their source will be automatically available to the user while debugging.</description><pubDate>Tue, 17 Mar 2026 09:39:00 GMT</pubDate></item><item><title>Rust in the kernel is no longer experimental | Lobsters</title><link>https://lobste.rs/s/otc3ak/rust_kernel_is_no_longer_experimental</link><description>My experience having written serious production code in both Rust and C (and I've been doing C for over a decade), is that there's a lot fewer surprises lurking in the Rust stuff, even when I'm diving into codebases I'm unfamiliar with.</description><pubDate>Sat, 18 Apr 2026 11:17:00 GMT</pubDate></item></channel></rss>