Had a really good laugh with @hannah just now trying our hands at the clearly way superior & production ready act of #VibeCoding with #Codestral.
We told it to build a calculator in #Rust. After telling it to use an AST it looked promising, even adhering to order of operation (already better than MS Calc!).
Then we told it to add support for braces and it utterly and completely shat itself. Like, Mexican diet explosive diarrhea-style. 
Is there a way to write queries and transforms over #Rust codebases to refactor.
Like, all uses of a given datatype removed...
select expressions from crate where footype is used
update crate where footype is used set use to null
Finished my day job, so I can come back to fixing my personal projects. And this time, I have a "funny" story! :3
Just fixed a segfault in my Rust sysinfo crate on FreeBSD. So, apparently, in some FreeBSD types, a pointer isn't actually a pointer but a kernel pointer. So to get access to the data, you need to use kvm_read function... And it might return types that also have kernel pointers and so on.
Lost a few hours trying to understand why my non-null pointers were out of my memory to discover by reading FreeBSD source code what was going on (because if there is documentation about this, didn't find it).
Anyway, I think this whole API is awful. FreeBSD making breaking changes in structs layout between each version is also a nightmare. Of all platforms I wrote Rust bindings for, this is the worst by far.
PR is here: https://github.com/GuillaumeGomez/sysinfo/pull/1499
Binance is hiring Smart Contract Security Engineer
#golang #python #rust #solidity #blockchain #defi #web3 #securityengineer
Remote; Singapore
Full-time
Binance
Job details https://jobsfordevelopers.com/jobs/smart-contract-security-engineer-at-binance-apr-17-2024-c6fd42?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring
Wrote a blog post about memory leaking in #Rust and why it is not always a bad idea.
Rust is memory safe... but that doesn't mean there a no pitfalls!
Here are a bunch of things you should look out for in production code:
From my most recent blog post, I was inspired to make a PR to the syn crate to add docs for syn::Error::combine for how to store "maybe errors" and how to iterate over errors once combined (helpful for unit testing). #rust
i would like to announce that i am rewriting my game in #rust !
this will greatly increase the productivity:
i will no longer be able to improve my makefile, or have to test my code to be sure itll work, cargo will do it for me!
and dont worry about the downsides, i dont use linked lists, you can always buy a larger hard drive, and the cpu overhead is minimal!
as for all 0 users who cant use a non-c compiler for any reason, theyre unimportant and holding us back
@liaizon no name yet, directory on my projects folder is called "activitypub", Python module is un-creatively called "leoactivitypub".
All it can do is follow people (send signed Follow actions) and validate incoming post signatures.
I wanted to do it in #Rust but ended up in #Python to get something working quickly. The whole thing is a mess right now :(
Official Clippy (Rust's official linter) update announcement! #rust #rustlang #programming
As a Clippy team member, I'm very pleased to announce our latest and greatest feature to date: We are adding GLaDOS to Clippy!
Rust developers upgrade to newer versions of Rust _vastly_ faster than Python developers do.
As of yesterday:
11% of downloads on PyPI were for Python versions 3.12 or newer, released in October 2023.
97% of package downloads on crates.io were for Rust 1.75 or later, released in December 2023.
From my experience, there's a rational reason for this difference: major Python vresion upgrades usually aren't _hard_, but they do require some tweaking. So there's always lag. Meanwhile, Rust upgrades are a non-event, with no changes to user code needed. And insofar as Rust wants to introduce breaking changes, the edition mechanism means it's opt-in rather than being forced on you when you upgrade.
UPDATE: As someone implied in their replies, this is somewhat misleading insofar as it includes lots of open source projects that are testing in CI against old Python versions. Even so, if open source project CI dominated download numbers, I would expect something like 40% of downloads to be for Python 3.12 or later, since most projects are likely supporting 3.9-3.13 at the moment.
Data sources:
- https://pypistats.org/packages/__all__
- https://lib.rs/stats#rustc
Your Rust is rusty? No problem, one can make a distro without:
https://discourse.ubuntu.com/t/58314
Liberty to the segfaults!
Introducing Ariel OS - an embedded library OS for small MCUs
#Scala developers - the best remote-only company is looking for you! :) Disclaimer: you *do* need to communicate in Polish.
We're also looking for senior #Java, #Rust and #TypeScript devs. So if you're into type-checked languages, SoftwareMill is the place for you :)
pnathan 
Revertron 
