Lmst

🤦‍♂️ Someone thought it was a good idea to mix Rust's crusty rigor with Python's whimsical magic, using #Serde as the glue. Because nothing screams 'user-friendly' like making #Rust dance to Python's tune through a #serialization library! 🎻✨
https://ohadravid.github.io/posts/2025-05-serde-reflect/ #Python #programming #userfriendly #HackerNews #ngated

A Rust API Inspired by Python, Powered by Serde

https://ohadravid.github.io/posts/2025-05-serde-reflect/

#HackerNews #Rust #Python #API #Serde #Programming #Languages

@mimir

This may not fit the 90% same machine situation but:

A few years ago, I looked around for IPC that would reliably scale to more than 1000 connections doing about 1 message/second with a few hundred bytes/message, and with forward secrecy.

The only thing that still fits that is #UDP (not TCP) over #wireguard.

For #rustlang udp means: do it yourself, no existing crates, allow for missing data, and #serde for the udp packet contents.

I always wondered why I always found the #serde deserialization API (from a deserializer implementer's perspective) so hard to keep straight in my head. It dawned on me today: it's because it's a 3-body problem. You have 3 types to think about: Deserialize, Deserializer and Visitor.

@davedelong, they mention @rust #Serde framework, so they are not too far from your idea.

“The Serde ecosystem consists of data structures that know how to serialize and deserialize themselves along with data formats that know how to serialize and deserialize other things.”

New Rust crate alert: eserde! 🦀

Tired of getting just one error at a time when deserializing with `serde`? `eserde` (built on top of `serde`) reports multiple errors at once, making API debugging way smoother.

Read @algo_luca ’s deep dive on why we built it & how to use it ➡️ https://mainmatter.com/blog/2025/02/13/eserde/

#Rustlang #serde #eserde

If you're in King's Hall at #RustNationUK, I found the crate Adam Harvey told us not to post on the social media about!

https://deps.dev/cargo/serde

#serde #rust #rustnation

Ok, a (half a) day of satisfaction was enough.
Everything works well still, but there is room for optimization. Not the optimization of #rust code, but of the RMI structure itself. There needs to be a family of RMI request structs, and I'm thankful to #rust for not providing me with #oop stuff, because I really don't need going down that rabbithole.
Containment will suffice, I'm just eager to see what #serde will have to say about it...

Will add more nodes soon.
And a menu to select different files.

It turned out to be pretty complicated because I have to create different buffers and images in the GPU and not in the CPU. And this leads to a lot of manual deserialization in #serde.

That was quite a journey. So happy, it worked out in the end.

(Still experimenting a lot with extreme formatting.)

@fasterthanlime

I see I'm not the only one who pronounces #serde in a way that rhymes with “merde”.

A sneak peek into tomorrow's episode of Self-Directed Research ...
❗😇 ☢️

#serde

#unsafe

https://github.com/kdl-org/kdl-rs/pull/83

the work has begun to add #serde support to #kdl rs!

It'll take me a bit, but the parser refactor that'll let me do this is going well.

anyway this is all very exciting because I think not being able to use serde has tbh been a huge blocker for folks adopting kdl in Rust

EDIT: answer found, please see downthread

Coding question: is there something for #python like #serde where the serialized version of the data can be a format you define, not Just Fucking JSON

Before you ask: no I can't change the format to JSON, it's hardcoded into this DVD player I have. Yes, you read that right.

Great article by Alisa Sireneva!

https://purplesyringa.moe/blog/i-sped-up-serde-json-strings-by-20-percent/

#rust #serde #json

I’ve just released version 2.0.0 of my data matching library criterium for Rust.

It supports serde now, which means one can write out the conditions directly in json/toml/whatever …

It can also compile to multi-table SQL queries for use with rusqlite.

#rust #sqlite #serde :drgn_flat_happy:

Rust's serde should really support default literals! 🦀

➡️ Read more: https://serde.rs/attr-default.html

✨ Tracking issue: https://github.com/serde-rs/serde/issues/368

#rustlang #serde #serialization

Написать X-docker-isolation-provider сложно — но не невозможно

Вы когда-нибудь чувствовали себя пионерами? Вот именно так я себя и ощущал, когда писал docker-isolation-provider для платформы ассоциативного программирования Deep . Все было так: в один прекрасный день у нас на платформе связей решили - было бы славно портировать нашего бота в Deep . А для этого нужно было написать так называемые провайдеры . Провайдеры нужны лишь для одной цели - дать возможность пользователю выполнять пользовательские хэндлеры на любом языке. Тогда я просто подумал, что было бы неплохо помочь парням, которые вероятно Rust никогда в жизни не видели . Ох, как же я тогда ошибался…

https://habr.com/ru/articles/822093/

#deepfoundation #программирование #история_разработки #rust #actixweb #serde #wasm

TPM2 command encoding with #bincode and #serde:

            let options = DefaultOptions::new()
                .with_fixint_encoding()
                .with_big_endian();
            buf.extend(&options.serialize(&(Tag::NoSessions as u16)).unwrap());
            buf.extend(&options.serialize(&22_u32).unwrap());
            buf.extend(
                &options
                    .serialize(&(CommandCode::GetCapability as u32))
                    .unwrap(),
            );
            buf.extend(&options.serialize(&(Capability::Handles as u32)).unwrap());
            buf.extend(&options.serialize(&HR_PERSISTENT).unwrap());
            buf.extend(&options.serialize(&1_u32).unwrap());

#rust #rustlang

Form data (x-www-form-urlencoded) support in #Axum is a bit disappointing. It uses #serde’s serde_urlencoded underneath, which in principle is fine. But the problem is that HTML forms don’t let you *not send* a value, which makes the whole thing useless with optional fields. You can set a field in a form to not be required and send an empty value (`?foo&bar=3&…` or `?foo=&bar=3&…` for empty `foo`) but then serde treats it as a present empty string and fails deserialization.

#Rust #Rustlang

I've just tagged a new release of Crell/Serde, version 1.2.

This release includes support for Unix timestamps, makes TypeFields more flexible and customizable, and fixes an issue with handling null values. Note that the latter fix has a very small BC break that only impacts a select number of custom Importers, so odds are you won't notice.

Get it while it's hot!

https://github.com/Crell/Serde

#Serde #Serialization #PHP #Programming

#Serde

Client Info