Readit NewsObligatory mention of that iconic low-angle shot of The Mother floating gracefully across the plains. One of the best of all time.
(doesn't mean it's not an improvement on C++)
Novig is rebuilding sports betting from first principles as a prediction market exchange. Legacy sportsbooks are extractive middlemen with misaligned incentives, dark patterns, and predatory mechanics. We're creating the alternative: a transparent exchange where users trade against each other at fair odds.
We're building core infrastructure around order routing, risk management, data pipelines, low-latency networking, and market integrity at scale. We write Rust extensively. We believe correctness, performance, and expressive code are necessities rather than luxuries. Ideal candidates care deeply about infrastructure, security, and performance. It certainly won't hurt to also care about prediction markets, traditional markets, or well-designed distributed systems.
Tech stack: Rust, Node, PostgreSQL, Kafka, Linux, distributed systems.
jobs@novig.co | https://job-boards.greenhouse.io/novig/jobs/4588745006
``` const MyComponent = () => jsx!(<div></div>) ```
rather than a .tsx file.
That or wasm to be usable so I can just write my web apps in Rust
I too, eventually gave up on React <> WASM <> Rust but I was able to port all my existing React over into Leptos in a few hours.
I look forward to what tomorrow brings.
* Start from 0 if you are indexing. I.e. you are identifying an item or its position.
* Start from 1 if you are counting. I.e. you are saying how many items there are.
It doesn't matter what it is. I don't know why you think pages in a book are somehow different to memory addresses.
Start from 0 if you are counting boundaries (fenceposts, memory addresses)
Start from 1 if you are counting spaces (pages in a book, ordinals)
Floors are a case where both make intuitive sense, which is maybe how we ended up with European vs American floor numbering.
It will automatically implement the most general, relaxed version (FnMut I think?) and only restrict itself further to FnOnce and Fn based on what you do inside the closure.
So, it can be tricky to know what's going on, and making a code change can change the contract of the closure and therefore where and how it can be used.
(I invite rust experts to correct me if any of the above is mistaken - I always forget the order of precedence for FnOnce/Fn/FnMut and which implies which)
FnOnce
FnMut
Fn