🏡
  • ↔
  • →
  1. About KeePassXC’s Code Quality Control – KeePassXC
  2. How to build a remarkable command palette
  3. Leaderboard - compar:IA, the AI chatbot arena
  4. Who needs Graphviz when you can build it yourself? | SpiderMonkey JavaScript/WebAssembly Engine
  5. Automerge

generated: November 24, 2025 at 09:11:09

  1. November 24, 2025
    1. 🔗 r/reverseengineering /r/ReverseEngineering's Weekly Questions Thread rss

      To reduce the amount of noise from questions, we have disabled self-posts in favor of a unified questions thread every week. Feel free to ask any question about reverse engineering here. If your question is about how to use a specific tool, or is specific to some particular target, you will have better luck on the Reverse Engineering StackExchange. See also /r/AskReverseEngineering.

      submitted by /u/AutoModerator
      [link] [comments]

    2. 🔗 HexRaysSA/plugin-repository commits sync repo: -1 plugin, -2 releases rss 
      sync repo: -1 plugin, -2 releases

## Removed plugins
- fwhunt-ida
    3. 🔗 langchain-ai/deepagents deepagents-cli==0.0.10 release

      Changes since deepagents-cli==0.0.9

      release(deepagents, cli) (#477)
      Harrison/fix diffing (#478)
      truncate glob (#473)
      fix(cli): 2nd argument must be called runtime (not _runtime) (#472)
      add file upload and download apis (#381)
      chore(cli): other lints (#464)
      feat: add option to disable splash on startup (#446)
      chore(cli): pull out interrupt on config (#463)
      Harrison/add gemini support (#456)
      chore(cli): remove internal file that's not needed (#462)
      chore(cli): apply auto-fixes for linting (#461)
      chore(cli): quick linting fixes (#460)
      chore(cli): remove hard-coded paths (#458)
      cli: inherit env variables for cli (#459)
      fix(deepagents-cli): fix linting (broke CI) (#457)
      feat(cli): add project-level skills support (#439)
      fix: localize key bindings and update tips for macOS compatibility (#451)
      chore: cleanup markdownlint errors in README.md (#447)
      fix cli rendering (#445)
      add auto accept option to CLI (#421)
      Remove unnecessary dependencies from deepagents module (#429)
      fix: use request.override instead of direct attribute overrides (#431)
      add missing type annotations (#425)
      chore(deepagent-cli): remove double diff display (WIP) (#387)
      Add skills and dual-scope memory to deepagents CLI (#315)
      use thread id rather than hardcoding to main (#423)

    4. 🔗 langchain-ai/deepagents deepagents==0.2.8 release

      Changes since deepagents==0.2.7

      release(deepagents, cli) (#477)
      return strings in tools (#474)
      truncate glob (#473)
      fix(deepagents): fix type for file info (#471)
      add file upload and download apis (#381)
      fix(deepagents-cli): fix linting (broke CI) (#457)
      fix(middleware): prevent silent corruption from Windows absolute paths (Issue #427) (#454)
      Remove unnecessary dependencies from deepagents module (#429)
      fix: use request.override instead of direct attribute overrides (#431)
      Update README.md (#422)

    5. 🔗 obra/superpowers v3.5.0 release

      Release v3.5.0: OpenCode Support

    6. 🔗 jcrist/msgspec Version 0.20.0 release
      • Support Python 3.14, including freethreaded mode (#852, #877).
      • Expose the StructMeta metaclass (#890, #927, #928, #940, #945).
      • Add msgspec.inspect.is_struct and msgspec.inspect.is_struct_type functions for checking whether an object is a msgspec.Struct-like instance or class (#950).
      • Support Windows arm64 builds (#943).
      • Enable ThinLTO on macOS aarch64 builds (#937).
      • Fix leaks of re.Pattern objects when using pattern constraints of msgspec.Meta (#899).
      • Fixed memoryview support for msgspec.msgpack (#836).
      • Fix crash when typing.TypedDict contains incorrect metadata (#853, #947).
      • Add setuptools-scm as a build dependency instead of vendoring versioneer (#905).
      • Remove support for legacy packaging builds (#907).
      • Improved the developer experience by adding the just command runner and Dev Container support (#918).
    7. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, -1 plugin, +2 releases, -1 release rss 
      sync repo: +1 plugin, -1 plugin, +2 releases, -1 release

## New plugins
- [fwhunt-ida](https://github.com/binarly-io/fwhunt-ida) (1.0.2, 1.0.1)

## Removed plugins
- gepetto
  2. November 23, 2025
    1. 🔗 livestorejs/livestore "v0.4.0-dev.18" release

      "Release 0.4.0-dev.18 including Chrome Extension"

    2. 🔗 r/wiesbaden Monatlicher Pen-and-Paper-Rollenspieltreff in Wiesbaden Schierstein rss

      Einmal im Monat bieten wir in der Phantasos Arena in Wiesbaden-Schierstein einen Rollenspiel-Treff an. Einsteiger und Profis sind herzlich willkommen, sowohl als Spieler als auch als Spielleiter, wir freuen uns immer über neue Gesichter in der Runde und neue Systeme. Der nächste Treff findet am 8.12. statt, und es wird weihnachtlich.

      Um besser planen zu können, bitten wir um eine Anmeldung via Discord: https://discord.gg/c82e3fYKyr

      Ort: Schossbergstraße 11, hinteres Bürogebäude, Wiesbaden Datum: 1x/Monat, nächstes mal am 8.12., 18.30 Uhr Systeme: Wechselnd, im Dezember zB Candela Obscura und ein W24-Abenteuer am Nordpol

      Hinweise: Der Betreiber der Location bittet um 5€ Nutzungsbeitrag pro Person für Miete, Strom etc; wer sich das nicht leisten kann, ist trotzdem willkommen. Die Location ist nicht barrierefrei.

      submitted by /u/Bitter-Secretary6006
      [link] [comments]

    3. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +1 release rss 
      sync repo: +1 plugin, +1 release

## New plugins
- [gepetto](https://github.com/JusticeRage/Gepetto) (1.5.0)
    4. 🔗 r/wiesbaden Black-/ Death-Metall Band gründen? rss

      Hat wer Lust? Gerne Richtung BoltThrower, Obituary etc... Musikalisch stumpf, wenig Virtuosität, böse gucken und so. Mental auch klassisch britisch, also links-grün hardcore-humanistisch mit kollektivistischem Ansatz. Gender egal, Hauptsache Proberaum. Bin alt, männlich und verbittert; spiele aber ganz o.k. Gitarre. Cheerio & Ta-da.

      submitted by /u/Last-Wolverine-1774
      [link] [comments]

    5. 🔗 r/wiesbaden Bauingenieur Julius Berger rss

      submitted by /u/NoBad9507
      [link] [comments]

    6. 🔗 r/wiesbaden Steam trains around Frankfurt in the coming weeks, incl. one from Wiesbaden rss

      submitted by /u/SenatorAslak
      [link] [comments]

    7. 🔗 HexRaysSA/plugin-repository commits sync repo: -1 plugin, -1 release rss 
      sync repo: -1 plugin, -1 release

## Removed plugins
- ida-terminal-plugin
    8. 🔗 Register Spill Joy & Curiosity #63 rss

      This was the second time in four months that I happened to be in San Francisco when a new model was released by a major provider. "Gemini 3 just dropped" was overheard in the coffee shop.

      Very busy but fantastic week.

      • We switched Amp to Gemini 3 Pro. I know that for some people Gemini 3 feels off, but I honestly think it's the best model I've used as an agent so far. It's fantastic.

      • I'm still holding my breath and I'm pessimistic, but hallelujah! if this actually happens in a way that's noticeable: Europe is scaling back its landmark privacy and AI laws.

      • What I found the most surprising about Every's Vibe Check on Gemini 3 is that they're saying it's "not yet a writing champ". Maybe I can't judge it on that, I very rarely use LLMs to generate more than a single sentence of prose, but I thought Gemini 3's descriptions of bugs, its summaries of what it did, its investigations -- I thought those were well-written and surprisingly well-formatted too. I actually said out loud: "if I would see a PR description written like that , I'd try to hire the person who wrote it."

      • Paul Dix, CTO of InfluxDB: "I believe the next year will show that the role of the traditional software engineer is dead. If you got into this career because you love writing lines of code, I have some bad news for you: it's over. The machines will be writing most of the code from here on out. Although there is some artisanal stuff that will remain in the realm of hand written code, it will be deeply in the minority of what gets produced."

      • "Older programs were all about what you need: you can do this, that, whatever you want, just let me know. You were in control, you were giving orders, and programs obeyed. But recently (a decade, more or less), this relationship has subtly changed. Newer programs (which are called apps now, yes, I know) started to want things from you."

      • Are You Playing to Play, or Playing to Win? Read it two days ago and already think that these definitions of scrub and maestro will stick with me. "One time I played a scrub who was pretty good at many aspects of Street Fighter, but he cried cheap as I beat him with 'no skill moves' while he performed many difficult dragon punches. He cried cheap when I threw him 5 times in a row asking, 'is that all you know how to do? throw?' I told him, 'Play to win, not to do 'difficult moves.'' He would never reach the next level of play without shedding those extra rules in his head". Can't help but think of programming and typing code by hand.

      • "#! was a great hack to make scripts look and feel like real executable binaries.", from: #! magic, details about the shebang/hash-bang mechanism on various Unix flavours.

      • "A friend of mine tells Claude to always address him as 'Mr Tinkleberry', he says he can tell when Claude is not paying attention to the instructions on CLAUDE.md when Claude stops calling him 'Mr Tinkleberry' consistently"

      • This is from all the way back in April and you actually notice that when reading, I'd say, which is interesting in itself, but the whole piece is great and contains a lot of gems: Will the Humanities Survive Artificial Intelligence?

      • "I've started a company in this space about 2 years ago. We are doing fine. What we've learned so far is that a lot of these techniques are simply optimisations to tackle some deficiency in LLMs that is a problem "today". These are not going to be problems tomorrow because the technology will shift. As it happened many time in the span of the last 2 years. So yah, cool, caching all of that... but give it a couple of months and a better technique will come out - or more capable models. [...] What I've learned from this is that often times it is better to do absolutely nothing."

      • Joan Didion, On Self-Respect: "In brief, people with self-respect exhibit a certain toughness, a kind of moral nerve; they display what was once called character, a quality which, although approved in the abstract, sometimes loses ground to other, more instantly negotiable virtues. The measure of its slipping prestige is that one tends to think of it only in connection with homely children and with United States senators who have been defeated, preferably in the primary, for re-election. Nonetheless, character--the willingness to accept responsibility for one's own life--is the source from which self-respect springs."

      If your travel also maps to model releases, you should subscribe:

    9. 🔗 r/LocalLLaMA Physical documentation for LLMs in Shenzhen bookstore selling guides for DeepSeek, Doubao, Kimi, and ChatGPT. rss

      Physical documentation for LLMs in Shenzhen bookstore selling guides for DeepSeek, Doubao, Kimi, and ChatGPT. | submitted by /u/abdouhlili
      [link] [comments]
      ---|---

    10. 🔗 r/reverseengineering Luau VM Bytecode Injection via Manual Mapping rss

      submitted by /u/pmd02931
      [link] [comments]

  3. November 22, 2025
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2025-11-22 rss

      IDA Plugin Updates on 2025-11-22

      New Releases:

      Activity:

    2. 🔗 Simon Willison Olmo 3 is a fully open LLM rss

      Olmo is the LLM series from Ai2 - the Allen institute for AI. Unlike most open weight models these are notable for including the full training data, training process and checkpoints along with those releases.

      The new Olmo 3 claims to be "the best fully open 32B-scale thinking model" and has a strong focus on interpretability:

      At its center is Olmo 3-Think (32B), the best fully open 32B-scale thinking model that for the first time lets you inspect intermediate reasoning traces and trace those behaviors back to the data and training decisions that produced them.

      They've released four 7B models - Olmo 3-Base, Olmo 3-Instruct, Olmo 3-Think and Olmo 3-RL Zero, plus 32B variants of the 3-Think and 3-Base models.

      Having full access to the training data is really useful. Here's how they describe that:

      Olmo 3 is pretrained on Dolma 3, a new ~9.3-trillion-token corpus drawn from web pages, science PDFs processed with olmOCR, codebases, math problems and solutions, and encyclopedic text. From this pool, we construct Dolma 3 Mix, a 5.9-trillion-token (~6T) pretraining mix with a higher proportion of coding and mathematical data than earlier Dolma releases, plus much stronger decontamination via extensive deduplication, quality filtering, and careful control over data mixing. We follow established web standards in collecting training data and don't collect from sites that explicitly disallow it, including paywalled content.

      They also highlight that they are training on fewer tokens than their competition:

      [...] it's the strongest fully open thinking model we're aware of, narrowing the gap to the best open-weight models of similar scale – such as Qwen 3 32B – while training on roughly 6x fewer tokens.

      If you're continuing to hold out hope for a model trained entirely on licensed data this one sadly won't fit the bill - a lot of that data still comes from a crawl of the web.

      I tried out the 32B Think model and the 7B Instruct model using LM Studio. The 7B model is a 4.16GB download, the 32B one is 18.14GB.

      The 32B model is absolutely an over-thinker! I asked it to "Generate an SVG of a pelican riding a bicycle" and it thought for 14 minutes 43 seconds, outputting 8,437 tokens total most of which was this epic thinking trace.

      I don't usually quote the full SVG in these write-ups, but in this case it's short enough that I think it's worth sharing. The SVG comments give a great impression of what it was trying to do - it has a Bicycle, Bike frame, Pelican, Left and Right wings and even "Feet on pedals".

      <svg width="200" height="200" viewBox="0 0 100 100">
  <!-- Bicycle -->
  <circle cx="30" cy="60" r="15" stroke="black" fill="none"/>
  <circle cx="70" cy="60" r="15" stroke="black" fill="none"/>

  <!-- Bike frame -->
  <rect x="35" y="25" width="30" height="10" fill="saddlebrown"/>
  <line x1="35" y1="40" x2="30" y2="60" stroke="black" stroke-width="3"/>
  <line x1="65" y1="40" x2="70" y2="60" stroke="black" stroke-width="3"/>

  <!-- Pelican -->
  <ellipse cx="55" cy="65" rx="20" ry="15" fill="white"/>
  <polygon points="52 50,57 35,62 50" fill="black"/> <!-- Head/beak -->
  <circle cx="55" cy="45" r="2" fill="white"/>
  <circle cx="60" cy="45" r="2" fill="white"/>

  <polygon points="45 60,50 70,55 60" fill="lightgrey"/> <!-- Left wing -->
  <polygon points="65 60,70 70,55 60" fill="lightgrey"/> <!-- Right wing -->

  <!-- Feet on pedals -->
  <polygon points="25 75,30 85,35 75" fill="black"/>
  <polygon points="75 75,70 85,65 75" fill="black"/>
</svg>

      Rendered it looks like this:

      Two circles, each with a triangle sticking out from the bottom. They have bars leading up to a brown box. Overlapping them is a black triangle with white circles for eyes and two grey triangles that are probably meant to be wings. It is not recognizable as a pelican or a bicycle.

      I tested OLMo 2 32B 4bit back in March and got something that, while pleasingly abstract, didn't come close to resembling a pelican or a bicycle:

      Blue and black wiggly lines looking more like a circuit diagram than a pelican riding a bicycle

      To be fair 32B models generally don't do great with this. Here's Qwen 3 32B's attempt (I ran that just now using OpenRouter):

      The bicycle is two black circles joined by two lines, with a weird rectangular saddle perched on top The pelican is a blue oval, a white circles with a yellow triangle in it and a weird eye shaped oval overlapping the blue one.

      OlmoTrace

      I was particularly keen on trying out the ability to "inspect intermediate reasoning traces". Here's how that's described later in the announcement:

      A core goal of Olmo 3 is not just to open the model flow, but to make it actionable for people who want to understand and improve model behavior. Olmo 3 integrates with OlmoTrace, our tool for tracing model outputs back to training data in real time.

      For example, in the Ai2 Playground, you can ask Olmo 3-Think (32B) to answer a general-knowledge question, then use OlmoTrace to inspect where and how the model may have learned to generate parts of its response. This closes the gap between training data and model behavior: you can see not only what the model is doing, but why---and adjust data or training decisions accordingly.

      You can access OlmoTrace via playground.allenai.org, by first running a prompt and then clicking the "Show OlmoTrace" button below the output.

      I tried that on "Generate a conference bio for Simon Willison" (an ego-prompt I use to see how much the models have picked up about me from their training data) and got back a result that looked like this:

      Screenshot of AI2 Playground interface with Olmo 3 32B Think model selected. User prompt reads "Generate a conference bio for Simon Willison". AI response shows expanded "Thoughts" section: "Okay, the user wants me to generate a conference bio for Simon Willison. Let me start by recalling who Simon is. He's a well-known developer, entrepreneur, and author in the tech community. I remember he's the co-founder of co:here and now works at Anthropic. He's famous for his work with SQLite, especially the datasette project. Also, he writes a blog called SimonWillison.net which is quite popular. First, I need to structure a typical conference bio. These usually include his current role, past positions, notable projects, and maybe some achievements or recognitions. I should highlight his key contributions like datasette, which allows easy exploration of SQLite databases via a web interface. That's a big deal in data journalism and open data circles." Right panel shows "OlmoTrace" feature described as "Documents from the training data that have exact text matches with the model response. Powered by infini-gram". First document excerpt discusses technology and innovation, with highlighted match text "societal implications of technology, emphasizing the" shown in bold, surrounded by text about responsibility and merging innovation with intellect. Second document excerpt about Matt Hall has highlighted match "is a software engineer and entrepreneur based in" shown in bold, describing someone in New York City who co-founded a PFP collection and works at Google Creative Lab. Note indicates "Document repeated 2 times in result" with "View all repeated documents" link.

      It thinks I co-founded co:here and work at Anthropic, both of which are incorrect - but that's not uncommon with LLMs, I frequently see them suggest that I'm the CTO of GitHub and other such inaccuracies.

      I found the OlmoTrace panel on the right disappointing. None of the training documents it highlighted looked relevant - it appears to be looking for phrase matches (powered by Ai2's infini-gram) but the documents it found had nothing to do with me at all.

      Can open training data address concerns of backdoors?

      Ai2 claim that Olmo 3 is "the best fully open 32B-scale thinking model", which I think holds up provided you define "fully open" as including open training data. There's not a great deal of competition in that space though - Ai2 compare themselves to Stanford's Marin and Swiss AI's Apertus, neither of which I'd heard about before.

      A big disadvantage of other open weight models is that it's impossible to audit their training data. Anthropic published a paper last month showing that a small number of samples can poison LLMs of any size - it can take just "250 poisoned documents" to add a backdoor to a large model that triggers undesired behavior based on a short carefully crafted prompt.

      This makes fully open training data an even bigger deal.

      Ai2 researcher Nathan Lambert included this note about the importance of transparent training data in his detailed post about the release:

      In particular, we're excited about the future of RL Zero research on Olmo 3 precisely because everything is open. Researchers can study the interaction between the reasoning traces we include at midtraining and the downstream model behavior (qualitative and quantitative).

      This helps answer questions that have plagued RLVR results on Qwen models, hinting at forms of data contamination particularly on math and reasoning benchmarks (see Shao, Rulin, et al. "Spurious rewards: Rethinking training signals in rlvr." arXiv preprint arXiv:2506.10947 (2025). or Wu, Mingqi, et al. "Reasoning or memorization? unreliable results of reinforcement learning due to data contamination." arXiv preprint arXiv:2507.10532 (2025).)

      I hope we see more competition in this space, including further models in the Olmo series. The improvements from Olmo 1 (in February 2024) and Olmo 2 (in March 2025) have been significant. I'm hoping that trend continues!

      You are only seeing the long-form articles from my blog. Subscribe to /atom/everything/ to get all of my posts, or take a look at my other subscription options.

    3. 🔗 r/wiesbaden St. Mauritius Church in Wiesbaden, Germany. (This is great) rss

      submitted by /u/rebelsofliberty
      [link] [comments]

    4. 🔗 r/reverseengineering Reverse Engineering AI Behavior with Structured Data Formats rss

      submitted by /u/pmd02931
      [link] [comments]

    5. 🔗 Locklin on science Wacky fun physics ideas rss

      My reading lately has ventured into weird physics papers. Mainstream physics (unlike machine learning and classical statistics where real progress has been made) is booooring these days. There’s no point in reading another “shittonium on silicon 111” papers, nor am I interested in stupid big budget projects where people always get the expected answer, nor […]

    6. 🔗 r/LocalLLaMA Qwen-image-edit-2511 coming next week rss

      Qwen-image-edit-2511 coming next week | submitted by /u/abdouhlili
      [link] [comments]
      ---|---

    7. 🔗 r/reverseengineering Autonomous exploitation + trace analysis workflows with CAI (open-source) rss

      submitted by /u/Obvious-Language4462
      [link] [comments]

    8. 🔗 r/reverseengineering Quantum Silicon Core Loader v5.5 Released - Universal Micro-VM for Hardware rss

      submitted by /u/ComputerGlobal1249
      [link] [comments]

    9. 🔗 Kagi release notes Nov 22nd, 2025 - Kagi Hub Belgrade rss

      Kagi Hub Belgrade: Making the human web real

      We just opened the Kagi Hub in Belgrade, Serbia!

      If you’re a Kagi member,you can book up to 5 FREE reservations per month and treat the Hub as your base whenever you’re in Belgrade. It is the same space our team uses, so you will be working directly alongside the people shaping Kagi’s future. More details, including how to reserve your spot, are in this blog post: https://blog.kagi.com/kagi- hub

      Having an actual physical space makes our mission to "humanize the web" feel so much more real. It is a place for Kagi members and our fully remote team to work, trade ideas, and build the tools we all wish existed.

      We are looking forward to welcoming you to Kagi's first ever Hub!

    10. 🔗 r/reverseengineering Reverse Engineering Casio's .CR5 File Format rss

      submitted by /u/AthuVaidya
      [link] [comments]

    11. 🔗 HexRaysSA/plugin-repository commits sync repo: +1 plugin, +1 release rss 
      sync repo: +1 plugin, +1 release

## New plugins
- [ida-terminal-plugin](https://github.com/HexRaysSA/ida-terminal-plugin) (0.0.6)
    12. 🔗 r/LocalLLaMA GLM planning a 30-billion-parameter model release for 2025 rss

      GLM planning a 30-billion-parameter model release for 2025 | submitted by /u/aichiusagi
      [link] [comments]
      ---|---

    13. 🔗 matklad TigerBeetle Blog rss

      TigerBeetle Blog

      Nov 22, 2025

      Continuing the tradition, I’ve been also blogging somewhat regularly on TigerBeetle’s blog, so you might want to check those articles out or even subscribe (my favorite RSS reader is RSSSSR):

      Today’s post is a video version of Notes on Paxos!

    14. 🔗 Filip Filmar rules_shar: bazel rules for creating self-extracting archives (shars) rss

      Details at: https://github.com/filmil/rules_shar

      This repository provides Bazel rules for creating self-extracting archives (“shar"s) out of shell binaries. See section “what is this” below for details. Usage To use the rules, add the following to your MODULE.bazel file: bazel_dep(name = "rules_shar", version = "0.0.0") # Select your version, of course. Then, in your BUILD.bazel file, you can use the shar_binary rule to create a self-extracting archive, as a drop-in replacement for the rule sh_binary.

  4. November 21, 2025
    1. 🔗 IDA Plugin Updates IDA Plugin Updates on 2025-11-21 rss

      IDA Plugin Updates on 2025-11-21

      New Releases:

      Activity:

    2. 🔗 r/LocalLLaMA Inspired by a recent post: a list of the cheapest to most expensive 32GB GPUs on Amazon right now, Nov 21 2025 rss

      Inspired by a recent post where someone was putting together a system based on two 16GB GPUs for $800 I wondered how one might otherwise conveniently acquire 32GB of reasonably performant VRAM as cheaply as possible?

      Bezos to the rescue!

      Hewlett Packard Enterprise NVIDIA Tesla M10 Quad GPU Module

      AMD Radeon Instinct MI60 32GB HBM2 300W

      Tesla V100 32GB SXM2 GPU W/Pcie Adapter & 6+2 Pin

      NVIDIA Tesla V100 Volta GPU Accelerator 32GB

      NVIDIA Tesla V100 (Volta) 32GB

      GIGABYTE AORUS GeForce RTX 5090 Master 32G

      PNY NVIDIA GeForce RTX™ 5090 OC Triple Fan

      For comparison an RTX 3090 has 24GB of 936.2 GB/s GDDR6X~~, so for $879 it's hard to grumble about 32GB of 898 GB/s HBM2 in those V100s!~~ and the AMD card has gotta be tempting for someone at that price!

      Edit: the V100 doesn’t support CUDA 8.x and later, so check compatibility before making impulse buys!

      Edit 2: found an MI60!

      submitted by /u/JockY
      [link] [comments]

    3. 🔗 sacha chua :: living an awesome life Tracking my oopses rss

      My stress level seems to be higher this year compared to last year. There are a number of ways I can tell when I need to slow down. I feel more tired, less energetic. Enthusiasm is difficult to muster. I need to break things down into smaller tasks. I make lots of little mistakes: I misplace things, I forget things, I don't think ahead.

      I track my mistakes in my home-made web-based journal under the Oops category. It feels a little better, come to think of it, when I can recover at least some data from a mistake. It's part of life, just a signal that tells me my brain is getting overloaded.

      I thought it would be interesting to analyse the frequency of my oops. For example, here are some recent oopses:

      • I forgot to check the EmacsConf upload folder before e-mailing the speakers a nudge about videos. There were a few more videos in there, whew! It's all good, people are patient and wonderful. Impact: people's patience. (2025-11-21-01)
      • I ate the last of the brown rice because I forgot to check if there was more. Good thing W- had more in the freezer. (2025-11-18-06)
      • I fumbled the Apple Pencil as I took my iPad off the piano. It disengaged from the magnetic lock, slid down the piano cover, and fell on the floor, breaking the tip. I didn't want to rush to catch it because I was tired and I was also holding the iPad. Fortunately, I have a number of backup tips. Impact: maybe $3 to replace that tip eventually. Cause: tired. (2025-11-18-03)
      • I washed the clothes on hot because I'm trying to avoid insect bites, but I accidentally shrank A+'s favourite purple shirt. Maybe next time I can just do a small load of my stuff. Impact: $10. I made up by buying new clothes for her, which I've been meaning to do anyway. #household (2025-11-15-16)
      • I crossed the street against the lights because I wasn't looking at the pedestrian light. (2025-11-11-06)

      Here's a yearly analysis:

      Code for retrieving and grouping my journal entries 
      (append '(("Year" "Count"))
(sort
 (mapcar (lambda (group)
           (list
            (car group)
            (length (cdr group))))
         (seq-group-by
          (lambda (o) (substring (my-journal-date o) 0 4))
          (seq-filter (lambda (o) (string= (my-journal-category o) "Oops")) (my-journal-get-entries))))
 :key 'car))
      Data table
      Year Count
      2017 12
      2018 75
      2019 36
      2020 38
      2021 33
      2022 25
      2023 28
      2024 37
      2025 73
      Code for graphing comments by year 
      import pandas as pd
import seaborn as sns
import matplotlib.pyplot as plt
import numpy as np

df = pd.DataFrame(data[1:], columns=data[0])
df['Count'] = df['Count'].astype(int)
df['Year'] = df['Year'].astype(int)
df = df.sort_values('Year')
plt.figure(figsize=(12, 6))
ax = sns.barplot(x='Year', y='Count', data=df)
plt.title('Oops by Year (2017-2025)', fontsize=16, fontweight='bold')
plt.xlabel('Year')
plt.ylabel('Number of oops entries')
plt.xticks(rotation=45)
plt.grid(axis='y')
for i, v in enumerate(df['Count']):
    ax.text(i, v + 1, str(v), ha='center', fontsize=9)
plt.tight_layout()
plt.savefig('year_count_plot.svg')
return 'year_count_plot.svg'
      2025-11-21T17:15:47.790809 image/svg+xml Matplotlib v3.6.3, https://matplotlib.org/

      2017 was not a full year of data, so that's probably why the number is so low. 2018 was when my dad died. I flew to the Philippines several times with my 2-year-old daughter so that we could spend time with my mom. It's a wonder that I managed to keep things mostly sorted out. Things were mostly manageable in between despite the ongoing pandemic. This year, though, a confluence of factors added a lot more strain on my brain. I wonder if part of it is because I'm concerned about health issues for people I care about. I also worry about the kiddo, school, change, and possibly adolescence. Who knows, maybe I'm starting to go through perimenopause, which apparently tends to include brain fog and mood swings. Fun. These are big things that I won't be able to resolve on my own, but I can get better at not overextending myself.

      Might be fun to do a month-by-month analysis.

      Code for retrieving and grouping my journal entries 
      (append '(("Year" "Month" "Count"))
(sort
 (mapcar (lambda (group)
           (list
            (substring (car group) 0 4)
            (string-to-number (substring (car group) 5))
            (length (cdr group))))
         (seq-group-by
          (lambda (o) (substring (my-journal-date o) 0 7))
          (seq-filter (lambda (o) (string= (my-journal-category o) "Oops")) (my-journal-get-entries))))
 :key (lambda (row) (format "%s-%02d" (car row) (cadr row)))))
      Code for making the heatmap 
      import pandas as pd
import matplotlib.pyplot as plt
import seaborn as sns

df = pd.DataFrame(data[1:], columns=data[0])
df = pd.pivot_table(df, columns=['Month'], index=['Year'], values='Count', aggfunc='sum', fill_value=0).iloc[::-1].sort_index(ascending=True)
plt.figure(figsize=(12, 8))
sns.heatmap(
    df,
    annot=True,
    fmt="d",  # Format as integer
    cmap="YlGnBu",  # Color map
    linewidths=.5,
    cbar_kws={'label': 'Count of "Oops" Entries'}
)
# Set the title and axis labels
plt.title('Heatmap of "Oops" Entries by Month and Year', fontsize=16)
plt.xlabel('Month', fontsize=12)
plt.ylabel('Year', fontsize=12)
plt.savefig('number-of-oops-by-month.png')
return df
      Data table 
      Month  1   2   3   4   5   6   7   8   9   10  11  12
Year
2017    0   0   0   0   0   0   0   0   7   2   0   3
2018    4   7   4  10  10   8   8   1   7   7   5   4
2019    4   4   2   4   4   1   3   5   1   1   2   5
2020    3   1   2   2   1   5   7   7   4   2   2   2
2021    2   2   1   1   2   4   6   4   2   2   1   6
2022    2   3   2   1   3   2   0   3   2   2   4   1
2023    3   1   1   1   5   2   4   5   0   0   3   3
2024    0   1   1   4   4   8   8   1   3   3   2   2
2025    7   1   7   2   6   4   9   8  10   4  15   0
      number-of-oops-by-month.png

      Oooh, what's up with this month, yeah…

      Most of my mistakes are small and easy to fix, just wasting time or patience. Others are a bit more annoying (dropping electronic devices, etc.). Some are potentially life-limiting (gotta make sure I look at the right lights before crossing the street). I tend to have a hard time with:

      • transitions, like coming home after a bike ride: I might accidentally hang up my keys on the wrong hook if I'm not paying attention. I've started saying the steps out loud.
      • tidying: If I have an attentional lapse, I put things in not-quite-the-right-place, so I probably can't listen to podcasts or think about complex thoughts.
      • travel: If I'm biking or walking, I have to pay extra attention.
      • task switching: interruptions, stacks, etc. I say things out loud and write them down if needed.

      When I notice myself making more oopses than usual, I try to sleep more, take things more slowly, offload more of my thoughts to drawings and notes, ask for help, and do fewer things.

      I'm working on single-tasking more instead of getting distracted by interesting thoughts. Maybe I used to be able to think about stuff, but now it's probably better to just let my mind be slightly bored if necessary instead of letting it get overloaded. I have to adapt to my capacity at the moment. I can either trust that those thoughts will come back if they're important, or take a moment to write them down on my phone. I can also give myself more focus time during the day to revisit those thoughts so that I don't get tempted to squeeze them in while, say, I'm putting away the dishes.

      Maybe routines, songs, physical cues like checklists, or pointing and calling (physically pointing to something and saying it out loud for confirmation) can help me with some of my frequently-made mistakes.

      Little by little. I might not be able to get rid of all the little mistakes, but if I can smoothen out some of the frequent ones, have an oops fund for the monetary costs of moderate mistakes, and keep myself from making the life-limiting ones, that might be enough.

      You can comment on Mastodon or e-mail me at sacha@sachachua.com.

    4. 🔗 r/reverseengineering YOU ARE NOT READY FOR THIS: NEURAL NETWORKS ARE KILLING REVERSE ENGINEERING rss

      submitted by /u/SapDragons
      [link] [comments]

    5. 🔗 HexRaysSA/plugin-repository commits sync repo: -1 plugin, -2 releases rss 
      sync repo: -1 plugin, -2 releases

## Removed plugins
- fwhunt-ida
    6. 🔗 r/reverseengineering Made a process injection detector rss

      submitted by /u/Capital-Let-5619
      [link] [comments]

    7. 🔗 News Minimalist 🐢 New daily pill helps lose 10% weight + 10 more stories rss

      In the last 2 days ChatGPT read 63606 top news stories. After removing previously covered events, there are 11 articles with a significance score over 5.5.

      [6.1] Daily pill helps people lose 10% of weight in 18 months, study finds —medicalxpress.com(+10)

      A study published Thursday found a new daily pill, orforglipron, helps people lose about 10% of their body weight, offering a cheaper, needle-free alternative to current injectable drugs.

      The Lancet study involved over 1,500 adults with both obesity and type 2 diabetes. After 72 weeks, those on the highest dose lost 10% of their weight, compared to 2% for a placebo group. Eli Lilly developed the pill.

      The pill has side effects similar to existing drugs and is less potent than the injectable Mounjaro. If approved, orforglipron could be available in 2026 at a significantly lower cost than current treatments.

      [6.4] Trump's Ukraine war end plan favors Russia —apnews.com(+521)

      A U.S.-Russia drafted peace plan proposes ending the war by requiring Ukraine to cede territory and forgo NATO membership in a deal largely favorable to Moscow.

      The 28-point proposal, obtained Thursday by the Associated Press, also offers Ukraine security guarantees, limits its military, and establishes a large international fund for reconstruction while reintegrating Russia into the global economy.

      Specific terms include recognizing Crimea, Luhansk, and Donetsk as Russian. The plan also calls for a ceasefire, amnesty for combatants, and using frozen Russian assets to help rebuild Ukraine.

      Highly covered news with significance over 5.5

      [5.5] Saudi Arabia commits $1 trillion to U.S. investments — annahar.com (Arabic) (+14)

      [5.6] Trump plans massive expansion of offshore oil drilling — economictimes.indiatimes.com (+18)

      [6.2] WHO reports increasing drug-resistant gonorrhea — cidrap.umn.edu*(*+6)

      [5.8] Scientists inch closer to pinprick blood test to detect diseases 10 years before symptoms appear — independent.co.uk (+7)

      [5.7] US tech giants issue bonds for AI investments, raising investor concerns — ctvnews.ca (+7)

      [5.5] US classifies countries with DEI policies as infringing human rights — bbc.com (+2)

      [5.6] Speech-restoring brain chip gets FDA approval for human trial — newatlas.com (+2)

      [5.6] Skin gel delivers insulin painlessly through the skin — zmescience.com (+2)

      [6.0] Fukushima owner edges towards restarting first reactor since meltdown — bbc.com (+14)

      Thanks for reading!

      — Vadim

      You can create your own personalized newsletter like this with premium.

      Powered by beehiiv

    8. 🔗 r/wiesbaden Good food spot rss

      Any good ideas for tasty food restaurant ?

      submitted by /u/Nonthor
      [link] [comments]

    9. 🔗 r/LocalLLaMA I made a free playground for comparing 10+ OCR models side-by-side rss

      It's called OCR Arena, you can try it here: https://ocrarena.ai

      There's so many new OCR models coming out all the time, but testing them is really painful. I wanted to give the community an easy way to compare leading foundation VLMs and open source OCR models side-by-side. You can upload any doc, run a variety of models, and view diffs easily.

      So far I've added Gemini 3, dots, DeepSeek-OCR, olmOCR 2, Qwen3-VL-8B, and a few others.

      Would love any feedback you have! And if there's any other models you'd like included, let me know.

      (No surprise, Gemini 3 is top of the leaderboard right now)

      submitted by /u/Emc2fma
      [link] [comments]

    10. 🔗 r/wiesbaden Kennzeichen BD23 rss

      https://preview.redd.it/vune38174n2g1.jpg?width=1000&format=pjpg&auto=webp&s=1ae6fa2d7e5d1d3c2ee3e3a4f8fc1d5797d5e268

      Gude! Ich sammle in einer App Kennzeichen aller Art. Die gängigen wie WI, SWA, RÜD etc. habe ich schon lange gefunden, aber das Kennzeichen BD23 fehlt mir noch, dabei handelt es sich um das Sonderkennzeichen des Bundeskriminalamtes. Weiß jemand, ob die hier in Wiesbaden herumfahren? und wenn ja, bei welcher Liegenschaft ich gute Chancen habe, ein Kennzeichen zu erspähen? Danke!

      submitted by /u/CTRLPLUST
      [link] [comments]

    11. 🔗 HexRaysSA/plugin-repository commits sync repo: -4 plugins, -4 releases rss 
      sync repo: -4 plugins, -4 releases

## Removed plugins
- gepetto
- ida-terminal-plugin
- parascope
- unicorn-tracer-arm64
    12. 🔗 @binaryninja@infosec.exchange Container support is finally here in Binary Ninja 5.2! You can browse nested mastodon

      Container support is finally here in Binary Ninja 5.2! You can browse nested formats like ZIP, IMG4, or CaRT right in memory with no manual extraction. When a container resolves to a single target, Binja can open it straight away. If there are multiple payloads, the new Container Browser lets you pick what to load. This all works with the Transform API, so you can extend it and add support for whatever formats you need. https://binary.ninja/2025/11/13/binary-ninja-5.2-io.html#container- support

    13. 🔗 The Pragmatic Engineer A startup in Mongolia translated my book rss

      I published The Software Engineer's Guidebook two years ago. The book sold 40,000 copies and generated $611,911 in royalties in its first two years. We need more good books in tech, so I hope that sharing these numbers inspires other techies to write them. I shared more details on how I self-published the book, on the financials, and learnings from publishing in this post.

      An unexpected highlight of publishing the book was ending up in Mongolia in June of this year, at a small-but-mighty startup called Nasha Tech. This was because the startup translated my book into Mongolian. Here's the completed book:

      altThe Software Engineer's Guidebook, in Mongolian. You can buy this translation here

      Here's what happened:

      A little over a year ago, a small startup from Mongolia reached out, asking if they could translate the book. I was skeptical it would happen because the unit economics appeared pretty unfavorable. Mongolia's population is 3.5 million; much smaller than other countries where professional publishers had offered to do a translation (Taiwan: 23M, South Korea: 51M, Germany: 84M, Japan: 122M, China: 1.43B people).

      But I agreed to the initiative, and expected to hear nothing back. To my surprise, nine months later the translation was ready, and the startup printed 500 copies on the first run. They invited me to a book signing in the capital city of Ulaanbaatar, and soon I was on my way to meet the team, and to understand why a small tech company translated my book!

      Japanese startup vibes in Mongolia

      The startup behind the translation is called Nasha Tech; a mix of a startup and a digital agency. Founded in 2018, its main business has been agency work, mainly for companies in Japan. They are a group of 30 people, mostly software engineers.

      altNasha Tech's offices in Ulaanbaatar, Mongolia

      Their offices resembled a mansion more than a typical workplace, and everyone takes their shoes off when arriving at work and switches to "office slippers". I encountered the same vibe later at Cursor's headquarters in San Francisco, in the US.

      Nasha Tech found a niche of working for Japanese companies thanks to one of its cofounders studying in Japan, and building up connections while there. Interestingly, another cofounder later moved to Silicon Valley, and advises the company from afar.

      The business builds the "Uber Eats of Mongolia". Outside of working as an agency, Nasha Tech builds its own products. The most notable is called TokTok, the "UberEats of Mongolia", which is the leading food delivery app in the capital city. The only difference between TokTok and other food delivery apps is scale: the local market is smaller than in some other cities. At a few thousand orders per day, it might not be worthwhile for an international player like Uber or Deliveroo to enter the market.

      altThe TokTok app: a customer base of 800K, 500 restaurants, and 400 delivery riders

      The tech stack Nasha Tech typically uses:

      • Frontend: React / Next, Vue / Nuxt, TypeScript, Electron, Tailwind, Element UI
      • Backend and API: NodeJS (Express, Hono, Deno, NestJS), Python (FastAPI, Flask), Ruby on Rails, PHP (Laravel), GraphQL, Socket, Recoil
      • Mobile: Flutter, React Native, Fastlane
      • Infra: AWS, GCP, Docker, Kubernetes, Terraform
      • AI & ML: GCP Vertex, AWS Bedrock, Elasticsearch, LangChain, Langfuse

      AI tools are very much widespread, and today the team uses Cursor, GitHub Copilot, Claude Code, OpenAI Codex, and Junie by Jetbrains.

      I detected very few differences between Nasha Tech and other "typical" startups I've visited, in terms of the vibe and tech stack. Devs working on TokTok were very passionate about how to improve the app and reduce the tech debt accumulated by prioritizing the launch. A difference for me was the language and target market: the main language in the office is, obviously, Mongolian, and the products they build like TokTok also target the Mongolian market, or the Japanese one when working with clients.

      One thing I learned was that awareness about the latest tools has no borders: back in June, a dev at Nasha Tech was already telling me that Claude Code was their daily driver, even though the tool had been released for barely a month at that point!

      Why translate the book into Mongolian?

      Nasha Tech was the only non-book publisher to express interest in translating the book. But why did they do it?

      I was told the idea came from software engineer Suuribaatar Sainjargal, who bought and enjoyed the English-language version. He suggested translating the book so that everyone at the company could read it, not only those fluent in English.

      Nasha Tech actually had some in-house experience of translation. A year earlier, in 2024, the company translated Matt Mochary's The Great CEO Within as a way to uplevel their leadership team, and to help the broader Mongolian tech ecosystem.

      Also, the company's General Manager, Batutsengel Davaa, happened to have been involved in translating more than 10 books in a previous role. He took the lead in organizing this work, and here's how the timelines played out:

      • Professional translator: 3 months
      • Technical editor revising the draft translation: 1 month
      • Technical editing #2 by a Support Engineer in Japan: 2 months
      • Technical revision: 15 engineers at Nasha Tech revised the book, with a "divide and conquer" approach: 2 months
      • Final edit and print: 1 month

      This was a real team effort. Somehow, this startup managed to produce a high- quality translation in around the same time as it took professional book publishers in my part of the world to do the same!

      A secondary goal that Nasha Tech had was to advance the tech ecosystem in Mongolia. There's understandably high demand for books in the mother tongue; I observed a number of book stands selling these books, and book fairs are also popular. The translation of my book has been selling well, where you can buy the book for 70,000 MNTs (~$19).

      Book signing and the Mongolian startup scene

      The book launch event was at Mongolia's startup hub, called IT Park, which offers space for startups to operate in. I met a few working in the AI and fintech spaces - and even one startup producing comics.

      altBook launch event, and meeting startups inside Mongolia's IT Park

      I had the impression that the government and private sector are investing heavily in startups, and want to help more companies to become breakout success stories:

      • IT Park report: the country's tech sector is growing ~20%, year-on-year. The combined valuation of all startups in Mongolia is at $130M, today.It 's worth remembering that location is important for startups: being in hubs like the US, UK, and India confers advantages that can be reflected in valuations.
      • Mongolian Startup Ecosystem Report 2023: the average pre-seed valuation of a startup in Mongolia is $170K, seed valuation at $330K, and Series A valuation at $870K. The numbers reflect market size; for savvy investors, this could also be an opportunity to invest early. I met a Staff Software Engineer at the book signing event who is working in Silicon Valley at Google, and invests and advises in startups in Mongolia.
      • Mongolian startup ecosystem Map: better-known startups in the country.

      Two promising startups from Mongolia: Chimege (an AI+voice startup) AND Global (fintech). Thanks very much to the Nasha Tech team for translating the book - keep up the great work!

    14. 🔗 r/LocalLLaMA HunyuanVideo-1.5: A leading lightweight video generation model rss

      https://huggingface.co/tencent/HunyuanVideo-1.5

      submitted by /u/abdouhlili
      [link] [comments]

    15. 🔗 HexRaysSA/plugin-repository commits readme: tweaks rss 
      readme: tweaks
    16. 🔗 HexRaysSA/plugin-repository commits readme: add details and support hints rss 
      readme: add details and support hints

closes #7
    17. 🔗 r/reverseengineering Advanced Evasion Techniques in Low Level rss

      submitted by /u/pmd02931
      [link] [comments]

    18. 🔗 HexRaysSA/plugin-repository commits ci: better render logs summary rss 
      ci: better render logs summary
    19. 🔗 HexRaysSA/plugin-repository commits scripts: HCLI API changes rss 
      scripts: HCLI API changes
    20. 🔗 HexRaysSA/plugin-repository commits ci: collect log summary to help triage plugin repo status rss 
      ci: collect log summary to help triage plugin repo status

ref #5
    21. 🔗 HexRaysSA/plugin-repository commits add script to summarize GitHub indexer logs rss 
      add script to summarize GitHub indexer logs

summarize logs: don't rely on gh and colorize with rich
    22. 🔗 HexRaysSA/plugin-repository commits ci: run deploy only after repo sync rss 
      ci: run deploy only after repo sync
    23. 🔗 Kagi Kagi Hub Belgrade: A home base for Kagi members worldwide rss

      We’re excited to announce that Kagi Hub Belgrade ( https://hub.kagi.com ) is now open! Our first office doubles as a free coworking space for all Kagi members.

    24. 🔗 Servo Blog Servo Sponsorship Tiers rss

      The Servo project is happy to announce the following new sponsorship tiers to encourage more donations to the project:

      • Platinum: 10,000 USD/month
      • Gold: 5,000 USD/month
      • Silver: 1,000 USD/month
      • Bronze: 100 USD/month

      Organizations and individual sponsors donating in these tiers will be acknowledged on theservo.org homepage with their logo or name. Please note that such donations should come with no obligations to the project i.e they should be “no strings attached” donations. All the information about these new tiers is available at the Sponsorship page on this website.

      Please contact us atjoin@servo.org if you are interested in sponsoring the project through one of these tiers.

      Use of donations is decided transparently via the Technical Steering Committee’s public funding request process , and active proposals are tracked in servo/project#187.

      Last, but not least, we’re excited to welcome our first bronze sponsorLambdaTest who has recently started donating to the Servo project. Thank you very much!

    25. 🔗 Baby Steps Move Expressions rss

      This post explores another proposal in the space of ergonomic ref-counting that I am calling move expressions. To my mind, these are an alternative to explicit capture clauses, one that addresses many (but not all) of the goals from that design with improved ergonomics and readability.

      TL;DR

      The idea itself is simple, within a closure (or future), we add the option to write move($expr). This is a value expression ("rvalue") that desugars into a temporary value that is moved into the closure. So

      || something(&move($expr))

      is roughly equivalent to something like:

      { 
    let tmp = $expr;
    || something(&{tmp})
}

      How it would look in practice

      Let's go back to one of our running examples, the "Cloudflare example", which originated in this excellent blog post by the Dioxus folks. As a reminder, this is how the code looks today - note the let _some_value = ... lines for dealing with captures:

      // task:  listen for dns connections
let _some_a = self.some_a.clone();
let _some_b = self.some_b.clone();
let _some_c = self.some_c.clone();
tokio::task::spawn(async move {
    do_something_else_with(_some_a, _some_b, _some_c)
});

      Under this proposal it would look something like this:

      tokio::task::spawn(async {
    do_something_else_with(
        move(self.some_a.clone()),
        move(self.some_b.clone()),
        move(self.some_c.clone()),
    )
});

      There are times when you would want multiple clones. For example, if you want to move something into a FnMut closure that will then give away a copy on each call, it might look like

      data_source_iter
    .inspect(|item| {
        inspect_item(item, move(tx.clone()).clone())
        //                      ----------  -------
        //                           |         |
        //                   move a clone      |
        //                   into the closure  |
        //                                     |
        //                             clone the clone
        //                             on each iteration
    })
    .collect();

// some code that uses `tx` later...

      Credit for this idea

      This idea is not mine. It's been floated a number of times. The first time I remember hearing it was at the RustConf Unconf, but I feel like it's come up before that. Most recently it was proposed by Zachary Harrold on Zulip, who has also created a prototype called soupa. Zachary's proposal, like earlier proposals I've heard, used the super keyword. Later on @simulacrum proposed using move, which to me is a major improvement, and that's the version I ran with here.

      This proposal makes closures more "continuous"

      The reason that I love the move variant of this proposal is that it makes closures more "continuous" and exposes their underlying model a bit more clearly. With this design, I would start by explaining closures with move expressions and just teach move closures at the end, as a convenient default:

      A Rust closure captures the places you use in the "minimal way that it can" - so || vec.len() will capture a shared reference to the vec, || vec.push(22) will capture a mutable reference, and || drop(vec) will take ownership of the vector.

      You can use move expressions to control exactly what is captured: so || move(vec).push(22) will move the vector into the closure. A common pattern when you want to be fully explicit is to list all captures at the top of the closure, like so:

      || {
    let vec = move(input.vec); // take full ownership of vec
    let data = move(&cx.data); // take a reference to data
    let output_tx = move(output_tx); // take ownership of the output

      channel

          process(&vec, &mut output_tx, data)
}

      As a shorthand, you can write move || at the top of the closure, which will change the default so that closures > take ownership of every captured variable. You can still mix-and-match with move expressions to get more control. > So the previous closure might be written more concisely like so:

      move || {
    process(&input.vec, &mut output_tx, move(&cx.data))
    //       ---------       ---------       --------  
    //           |               |               |         
    //           |               |       closure still  
    //           |               |       captures a ref
    //           |               |       `&cx.data`        
    //           |               |                         
    //       because of the `move` keyword on the clsoure,
    //       these two are captured "by move"
    //  
}

      This proposal makes move "fit in" for me

      It's a bit ironic that I like this, because it's doubling down on part of Rust's design that I was recently complaining about. In my earlier post on Explicit Capture Clauses I wrote that:

      To be honest, I don't like the choice of move because it's so operational. I think if I could go back, I would try to refashion our closures around two concepts

      • Attached closures (what we now call ||) would always be tied to the enclosing stack frame. They'd always have a lifetime even if they don't capture anything.
      • Detached closures (what we now call move ||) would capture by-value, like move today.

      I think this would help to build up the intuition of "use detach || if you are going to return the closure from the current stack frame and use || otherwise".

      move expressions are, I think, moving in the opposite direction. Rather than talking about attached and detached, they bring us to a more unified notion of closures, one where you don't have "ref closures" and "move closures" - you just have closures that sometimes capture moves, and a "move" closure is just a shorthand for using move expressions everywhere. This is in fact how closures work in the compiler under the hood, and I think it's quite elegant.

      Why not suffix?

      One question is whether a move expression should be a prefix or a postfix operator. So e.g.

      || something(&$expr.move)

      instead of &move($expr).

      My feeling is that it's not a good fit for a postfix operator because it doesn't just take the final value of the expression and so something with it, it actually impacts when the entire expression is evaluated. Consider this example:

      || process(foo(bar()).move)

      When does bar() get called? If you think about it, it has to be closure creation time, but it's not very "obvious".

      We reached a similar conclusion when we were considering .unsafe operators. I think there is a rule of thumb that things which delineate a "scope" of code ought to be prefix - though I suspect unsafe(expr) might actually be nice, and not just unsafe { expr }.

      Edit: I added this section after-the-fact in response to questions.

      Conclusion

      I'm going to wrap up this post here. To be honest, what this design really has going for it, above anything else, is its simplicity and the way it generalizes Rust 's existing design. I love that. To me, it joins the set of "yep, we should clearly do that" pieces in this puzzle:

      • Add a Share trait (I've gone back to preferring the name share 😁)
      • Add move expressions

      These both seem like solid steps forward. I am not yet persuaded that they get us all the way to the goal that I articulated in an earlier post:

      "low-level enough for a Kernel, usable enough for a GUI"

      but they are moving in the right direction.

generated: November 24, 2025 at 09:12:16