We’re excited to announce that Warp now supports the latest OpenAI Codex models, unlocking the coding performance improvements that these models deliver over the core GPT models.
Why now?
Support for Codex has been a frequently requested feature since the Codex models were first released (see Warp issue #7490). Until recently, however, integrating Codex into Warp resulted in a meaningfully degraded experience.
Early Codex models were heavily optimized for the Codex CLI harness. When used insi...
An anonymous reader quotes a report from Ars Technica: On Monday, the US Department of the Interior announced that it was pausing the leases on all five offshore wind sites currently under construction in the US. The move comes despite the fact that these projects already have installed significant hardware in the water and on land; one of them is nearly complete. In what appears to be an attempt to avoid legal scrutiny, the Interior is blaming the decisions on a classified report from the Department of Defense.
The second Trump administration announced its animosity toward offshore wind power literally on day one, issuing an executive order on inauguration day that called for a temporary halt to issuing permits for new projects pending a re-evaluation. Earlier this month, however, a judge vacated that executive order, noting that the government has shown no indication that it was even attempting to start the re-evaluation it said was needed. But a number of projects have gone through the entire permitting process, and construction has started. Before today, the administration had attempted to stop these in an erratic, halting manner. Empire Wind, an 800 MW farm being built off New York, was stopped by the Department of the Interior, which alleged that it had been rushed through permitting. That hold was lifted following lobbying and negotiations by New York and the project developer Orsted, and the Department of the Interior never revealed why it changed its mind. When the Interior Department blocked a second Orsted project, Revolution Wind offshore of southern New England, the company took the government to court and won a ruling that let it continue construction.
Today's announcement targets those and three other projects. Interior says it is pausing the permits for all five, which are the only projects currently under construction. It claims that offshore wind creates "national security risks" that were revealed in a recent analysis performed by the Department of Defense, which apparently neglected to identify these issues during the evaluations it did while the projects were first permitted. What are these risks? The Interior Department is being extremely coy. It notes that offshore wind turbines can interfere with radar sensing, but that's been known for a while. In announcing the decision, Interior Secretary Doug Burgum also noted "the rapid evolution of the relevant adversary technologies." But the announcement says that the Defense Department analysis is classified, meaning nobody is likely to know what the actual reason is -- presuming one exists. The classification will also make it far more challenging to contest this decision in court.
CNNThe New YorkerThe New York TimesKQEDScientific AmericanArs TechnicaBBC NewsNPRIEEE Spectrum
In 2025, a global conversation emerged about memory, power and who controls the historical record. As governments deleted web pages, platforms broke links, and public data quietly (and not so quietly) disappeared, journalists around the world turned to the Internet Archive and the Wayback Machine to understand what was being lost, what could still be saved, and why preservation matters more than ever. From investigations in The New Yorker and The New York Times to video features from the BBC and CNN, these stories capture how the fight to preserve the web became one of the defining information battles of the year.
Thank you to everyone who joined Advent of Code 2025 in Rust! It was inspiring to see many Rustaceans solving algorithmic puzzles, and celebrating the holiday coding season with the community.
Before the Advent began, Vitaly Bragilevsky published a blog post on how to use AI in Advent of Code challenge responsibly and effectively. This year’s AoC featured 12 puzzles, and from December 1–12, we celebrated by posting daily RustRover features in our RustRover Advent Calendar – a small gift for the community and a way to highlight tools that make your Rust experience even better.
And the winners are…
We invited you to take on the AoC puzzles using Rust, join our leaderboards, and compete for top scores and random prizes. Now, it’s time to congratulate our 10 winners who stood out among all participants.
Let’s give a big round of applause to the top five Rust developers who dominated the combined leaderboards with impressive results out of 71 participants:
Duro – 2017 (for the second year in a row, as in 2024!)
JohnX4321 – 1996
MaRcR11 – 1961
Giacomo Stevanato – 1910
Agnibha Chakraborty – 1885
Additionally, here are five participants were randomly selected as prize winners:
bragrseg – 576
ViincentLim – 1585
N. Adhikary – 813
Gunter Schmidt – 435
Saurav Kumar – 676
We reached out to the winners who had social media contact information listed on their GitHub profiles. If you didn’t include contact details, please reach out to rustrover-support@jetbrains.com, and we’ll be happy to send you your prize. Congratulations to all our winners and to everyone who took part!
Keep learning and building in Rust
The Advent of Code puzzles are available year-round, so get ready for the next AoC by exploring resources to strengthen your Rust skills:
A huge thank-you to Eric Wastl and the Advent of Code team for creating such an inspiring tradition. Let’s keep learning, building, and having fun with Rust and see you next year for another round of AoC!
Log in
