Sometimes I wish that rustc had a database of small breaking changes that affect only a handful of crates, so that we could on the fly patch them going forward. Things like "we now correctly check for lifetimes in assoc types" can technically be a breaking change that affects a handful of crates, but I want to ensure that building a project from today in 15 years doesn't require a compiler tool chain from today.
I guess this is the windows backwards compatibility approach. #rust#rustlang
"#Rust development is going too fast (because they are stabilizing features I don't care about) and going too slow (because they are not stabilizing features I care about!"
There are only so many #RustLang contributors, hours in a day, days in a year to get to everything now, and some features are reliant on other, less flashy work that needs to happen before they can be even attempted.
But people are putting in a lot of work, the codebase changes so quickly that it is hard to keep up.
Hit an edge case in the #Rust compiler that appears to be quadratic at best and potentially exponential. Trivial to make happen with real-world code. Investigating...
I have some bittersweet news -- I decided to leave Deno. Going to be joining a really cool company, continuing to work in Rust.
Deno was a great place to work, full of really smart folks. I got to work on some great projects: rewriting the HTTP server to nearly 2x throughput, some major refactoring of the event loop and timers to make them an order of magnitude faster, working on rebuilding the V8 -> Rust interface to make it as fast as humanly possible...
... while also improving the developer experience with better errors.
Too many fun projects to count!
I still think #Deno is the best choice for server-side JS and #typescript, robust command-line tools and many other places. It's so much better than everything else.
Looking forward to announcing the new role in the near future and continuing to work in the high-performance #Rust arena. 🚀
(1/2) I recently posted a few posts about Rust 🦀 and my intention to leverage it for data science applications. Multiple people asked if Rust is a substitute for R or Python, and the short answer (in my opinion) is no. I see Rust as a complementary or supporting language that could make languages like R and Python faster.
Polaris 🐻❄️ is one example of a Python 🐍 application that uses Rust on the backend. 🧵👇🏼
https://nexte.st/ is awesome. The expression language to filter for tests or simply display a list of available test made is "must-have" for me. #rustlang#rust
I wonder if anyone has ever written an embedded #RDBMS in which there is no run-time #SQL interpreter, and all SQL queries are translated into machine code at compile time.
Kinda like #Rust sqlx, except queries are fully compiled at compile time, not just checked for correct syntax and types.
I'm guessing this would be extremely specific to one #programming language, and outright impossible in most programming languages.
Is this AI generated, or someone thinks middleware aimed for game development is the same as a game engine?
Regardless, can someone help me in finding some kind of #opensource middleware similar to #raylib, #sdl, #sfml, and #glfw? I can't find anything else, especially thanks to #seo and/or people not understanding the difference between engine and middleware. All I need is a fixed buffer audio stream (worst case scenario, I'll use my own that I started writing for my own middleware I can't finish due to lack of time), input handling, and creating an OpenGL window. I don't have enough time to tinker with my own middleware and/or directly hooking into the OS (thanks to SEO, a lot of the search results are also garbage for stuff like rawinput).
"Note that any lifetime bounds, including 'static, apply only to references and types containing references. They do nothing when applied to self-contained types. This means that String is not 'static, but rather it isn't affected by any lifetime bound."
✅ Implemented various challenging Achievements
✅ Implemented game menu
✅ Implemented game over screen
✅ Beautiful new planetary/lunar textures by Björn Jónsson, https://bjj.mmedia.is/data/planetary_maps.html
> Unfortunately, most people seem to have taken the wrong lesson from Rust. They see all of this business with lifetimes and ownership as a dirty mess that Rust has had to adopt because it wanted to avoid garbage collection. But this is completely backwards! Rust adopted rules around shared mutable state and this enabled it to avoid garbage collection. These rules are a good idea regardless.
Yes, so much this! I'm using #Rust not because I'm building low-level resource constrained systems (far from it) but because it allows for local reasoning about state. Paired with the ML inspired syntax that makes pattern matching easy this leads to far more reliable programs.
This is also why I like #Clojure so much. Clojure's refs / atoms /agents allow for scoping mutability in an otherwise purely functional system. Scratch for the same itch. But Rust's compile time checking avoids pushing issues into the runtime, increasing reliability and hugely reduces time needed for debugging. The trade off here is no interactive / live development.
also, now with #gpt4o, latency is going to be critical if you’re doing streaming audio/video, so #python may start looking less appealing. what’s the new #LLM language? #rust? #go? #cpp? #fortran?
i predict that there’s always going to be strong advantages to using #python for #ai, but with streaming audio & video of #gpt4o, there’s not enough latency slack for python.
i think a framework will emerge, similar to pyspark, where you can write python code that gets compiled into a steaming plan, and executed as highly optimized low level #rust code with the possibility of python UDFs. i figure it’s still a couple of years from being really usable rn
I've been moving between neovim, helix (can't get over the slightly different mental model compared to vim), vscode, rustrover... Curious what others use.