frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
2127•jasondavies•16h ago•985 comments

Levent Alpöge claims proof of the Generalized Riemann Hypothesis [pdf]

https://alpo.ge/remark.pdf
2669•iamronaldo•21h ago•1845 comments

Inkling 2 Mini

https://thinkingmachines.ai/news/inkling-2-mini/
1043•jasondavies•15h ago•194 comments

ClawDOS – An AI coding agent for DOS

http://ricapar.net/ClawDOS/
75•Ricapar•5h ago•21 comments

RCE in Gnupg

https://lists.gnupg.org/pipermail/gnupg-announce/2026q4/000517.html
24•gdgghhhhh•2h ago•2 comments

We promoted developers into architects without informing them

https://manidoraisamy.com/developer-to-architect.html
449•QueensGambit•17h ago•248 comments

Surprisingly Adorable Insect Portraits

https://amateurphotographer.com/latest/these-astonishing-insect-portraits-reveal-a-hidden-world-y...
54•NordStreamYacht•4h ago•12 comments

NINLIVE: The Nine Inch Nails live archive

https://ninlive.com/
269•CharlesW•12h ago•70 comments

Unforced Navier-Stokes Singularity and the Generalized Riemann Hypothesis

https://terrytao.wordpress.com/2026/11/20/unforced-euler-singularity-unforced-navier-stokes-singu...
455•archon1410•17h ago•190 comments

Clojure will affect the way you think about programming (2017)

https://eli.thegreenplace.net/2017/clojure-the-perfect-language-to-expand-your-brain/
106•sammatilda•8h ago•33 comments

Ask HN: I have been unemployed for 2y. 15 years of experience, US. What to do?

232•LetThingsBeDiff•12h ago•180 comments

Language Models Can Rewrite Their Own Weights

https://arxiv.org/abs/2611.21885
417•lwhsiao•18h ago•123 comments

Sir Brian May adds new dimension to Hera asteroid

https://www.esa.int/articles/about-us/directorates/operations/space-safety/hera/sir-brian-may-add...
118•mooreds•12h ago•25 comments

Engineer's Guide to Career Growth – Advice from My Time at Stripe and Facebook

https://review.firstround.com/the-engineers-guide-to-career-growth-advice-from-my-time-at-stripe-...
11•kurinikku•2d ago•2 comments

Valkey kills the skiplist, cuts sorted set overhead by up to 43%

https://valkey.io/blog/from-skiplist-to-b+tree/
142•reconditerose•3d ago•48 comments

FBI reportedly investigating apparent hack of its criminal database

https://www.bbc.com/news/articles/cvze7de86pk3o
24•theanonymousone•46m ago•1 comments

Fewer slides, more dragons

https://www.breakingchange.blog/p/fewer-slides-more-dragons
38•firloop•2d ago•15 comments

DreamCoder: Coding harness and IDE from the author of Mastering Emacs

https://www.masteringemacs.org/article/announcing-dreamcoder
225•facundo_olano•15h ago•73 comments

Microsoft's SideWinder Strategic Commander was a failed attempt

https://www.rockpapershotgun.com/microsofts-sidewinder-strategic-commander-was-a-failed-attempt-t...
15•Tomte•3d ago•3 comments

Nasdaq erases all 2026 gains as AI sell-off dampens Anthropic’s second day

https://www.theguardian.com/business/2026/nov/20/global-stock-markets-slump-anthropic-ipo-ai-sell...
330•cdrnsf•21h ago•607 comments

Finite-time blow-up for the Navier–Stokes equations

https://github.com/tristanbuckmaster/navier-stokes/
294•trotro•19h ago•92 comments

Acoustic parameters of bird vocalizations&their perceived pleasantness by humans

https://www.frontiersin.org/journals/bird-science/articles/10.3389/fbirs.2026.1794594/full
3•bookofjoe•2d ago•0 comments

Slopstrap – Make your site look hastily vibecoded

https://slopstrap.mikelacher.com/
294•mlacher•19h ago•55 comments

3-legged Persian leopard's 150-mile journey highlights Caucasus border hazards

https://news.mongabay.com/short-article/2026/11/three-legged-persian-leopards-150-mile-journey-hi...
25•rguiscard•3d ago•6 comments

Show HN: Tinnitus frequency finder and audio notch tool

https://trynotched.com/find
181•brianrhea•3d ago•116 comments

Exascale fusion simulation team named finalist for 2026 Gordon Bell Prize

https://www.alcf.anl.gov/news/exascale-fusion-simulation-team-named-finalist-2026-gordon-bell-prize
4•rbanffy•2h ago•0 comments

Vibecoding an inference chip

https://ankitg.me/blog/vibecoding-inference-chip/
151•ankitvgupta•17h ago•62 comments

Why the Airbus A321XLR often gets stuck climbing for first few hours of flight

https://simpleflying.com/airbus-a321xlr-often-stuck-climbing-1st-few-hours-flight/
123•edward•1w ago•88 comments

Serious cyberattack thought backed by wealthy operators

https://www.ruv.is/english/2026-11-20-serious-cyberattack-thought-backed-by-wealthy-operators-493411
93•Bender•11h ago•47 comments

Winedroid – run Android apps without Android (WASM demo)

https://winedroid.soham.sh/demo/
155•sohzm•15h ago•42 comments
Open in hackernews

A Rust API Inspired by Python, Powered by Serde

https://ohadravid.github.io/posts/2025-05-serde-reflect/
58•lukastyrychtr•1y ago

Comments

ohr•1y ago
(Author here) I needed to do a bit of "reflection" in a Rust crate but didn't want to implement a procedural macro, so I used Serde (which is a (de)serialization crate) instead.

This is also a deep dive into Serde internals - hope you'll like it!

snthpy•1y ago
Yes, great post! Thank you.
dundarious•1y ago
Pardon me, but I prefer the original by 1 million miles.

  let res = raw_api::query("SELECT * FROM Win32_Fan");
  for obj in res {
    if obj.get_attr("ActiveCooling") == Value::Bool(true) {
        if let Value::String(name) = obj.get_attr("Name") {
            if let Value::UI8(speed) = obj.get_attr("DesiredSpeed") {
                println!("Fan `{name}` is running at {speed} RPM");
            }
        }
    }
  }
If actually concerned about the need to know UI8, then create a typedef DesiredSpeedT or similar. This is equivalent to the struct Fan.

Edit: I understand the post is probably more of a playful exercise than anything else, but I really think the original is far far better (smaller, simpler, etc.) and hope that is not lost on people.

ohr•1y ago
That's understandable, but I think it depends on how many different structs like this you have and how many fields you need to work with (for our usecase, we had tens of structs with tens of fields each).

There's also an Alternatives section in the article about other approaches that can achieve similar results, but of course 'do nothing' is also a valid option.

Edit: > If actually concerned about the need to know UI8 ..

Just a small note: even if you don't care about the fact that it's a UI8, you still have to use the correct type. For example, if the field happens to be returned as UI4, this code won't work!

dundarious•1y ago
Right, but isn't the struct definition equivalent in line count and effort compared to some typedefs and perhaps a handful of trivial-to-inspect oneline helper functions?

Regarding the UI8, don't you have to get your version's struct data member type correct to the exact same degree as a typedef in my suggestion?

ohr•1y ago
> don't you have to get your version's struct data member type correct

No, since Serde will happyly fill a `u64` field with any other `u{8,16,32}` value, and even with signed types (as long as the actual value is non-negative) - this is sort of what happens when you deserialize a JSON `[1, 2, 3]` into `[u64]`.

dundarious•1y ago
Yes, but an equivalent to `impl<'de> Deserializer<'de> for ValueDeserializer` handles that. That could be a useful helper.
LtWorf•1y ago
dgacmu•1y ago
This kind of sells the reason not to wrap things behind an object interface, doesn't it?

    for fan in c.query("SELECT * FROM Win32_Fan"):
        if fan.wmi_property("ActiveCooling").value is True:
            print(f"Fan `{fan.wmi_property('Name').value}` is running at {fan.wmi_property('DesiredSpeed').value} RPM")
vs "SELECT Name, DesiredSpeed from Win32_Fan where ActiveCooling"

Obviously, this doesn't matter when you have 5 fans, but in general, you want to push your restrictions as deeply into the query as possible from an optimization standpoint.

ohr•1y ago
In WMI, the fields are lazy loaded when you do a `*` query, but the real crate [does use the same Serde reflection tricks](https://github.com/ohadravid/wmi-rs/blob/main/src/query.rs#L...) to create the correct field list when you query a struct which improves perf a lot!
vlovich123•1y ago
> Obviously, this doesn't matter when you have 5 fans, but in general, you want to push your restrictions as deeply into the query as possible from an optimization standpoint.

Depends where the database lives. If it's an in-process SQLite DB instance, there's no difference & doing this in code is easier to understand than more complicated SQL queries (of course not necessarily in this case but in general). But in all other cases you are correct about efficiency in general (although again other effects can dominate & make it irrelevant).

lnyng•1y ago
Interesting post. We wrote this “below” utility [1] that monitor system metrics similar to atop. We want the ability to collect all metrics into a single object, pass it around and visualize it elsewhere. Naturally we need some way to query into fields or even nested-struct fields. For example, to get the file cache usage of a particular process, we need to go through sample->processes->pid->memory->file cache. To do it ergonomically and also type-safely, we end up using proc macro to generate enums that represent field paths of the structs and then use them to query values of non-struct (leaf) fields. I always wonder if there are simpler ways or existing proc macro derives to safe us the efforts. Maybe I do need to look into serde internals for some inspirations.

[1] https://github.com/facebookincubator/below/blob/main/below/b...

lovasoa•1y ago
In my opinion, the clean way to implement this is with methods instead of attributes for name, desired_speed, etc...
xpe•1y ago
The title is vague in my opinion. What kind of API? What problem does it hope to solve? The article uses querying system data as examples, but after skimming it, I’m not sure why I would care. My comment is also a criticism of the article, since I couldn’t skim in quickly to figure out if I should spend more time on it.
ohr•1y ago
(Author here) Thanks! That's useful feedback.

I also agree - the final article isn't skim-friendly enough, which drives away some readers.

xpe•1y ago
Glad you are open to feedback. My top question is: What kind of people do you want to read this and why?
vlovich123•1y ago
I don't really understand what this offers above diesel.rs which AFAIK is a similar reflection interface except with much more flushed out ORM capabilities (much more complex filtering, joining etc) & support for an assortment of SQL dialects.
VWWHFSfQ•1y ago
> let res: Vec<Fan> = query();

It might feel more natural, and less magical if this used a turbofish instead

    let res = query::<Fan>();

Very neat
throw_a_grenade•1y ago
That's wdat minijinja does internally. As an argument to Template::render() you can give it any struct that implements Deserialize. That's how you can get varying (sic) variables to a single function and even attributes on "objects" processed by tte template.
I wrote typedload in python. Once they show you an API with hundreds of types you appreciate not having to do like that all the time.
dundarious•1y ago
I don't see the issue with just using an equivalent to `impl<'de> Deserializer<'de> for ValueDeserializer` then.
LtWorf•1y ago
There's unions, there's stuff that uses reserved words in the language as field names... You are obviously not familiar with this task.
dundarious•1y ago
The "generic macro over struct definitions" approach is the one that has at least some trouble dealing with these situations, not the "getter function with string argument" approach. I've had to do plenty of json and protocol buffers wrangling (meaningfully different, I know), and versioned packed struct memcpy/reinterpret_cast "parsing" as well.

My point is I don't want to do "this task" at all if "this task" means layering funky auto-generated machinery on top of what is already a perfectly reasonable API.

olalonde•1y ago
Why? It's much more verbose and error prone (e.g. "stringly typed"). Do you never deserialize JSON?
dundarious•1y ago
What's the difference between mistyping in the string here and mistyping in the struct definition? And yes I have.
olalonde•1y ago
You only need to get it right once, and from then on the compiler will catch any mistakes if you use it incorrectly. In contrast, every time you write obj.get_attr("DesiredSpeed"), there's a chance you'll make a typo and the compiler won't warn you about it.