101010.pl

Ype Kingma<a href="https://meow.social/@mimir" class="u-url mention" rel="nofollow noopener" target="_blank">@mimir</a> 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 <a href="https://mastodon.green/tags/UDP" class="mention hashtag" rel="nofollow noopener" target="_blank">#UDP</a> (not TCP) over <a href="https://mastodon.green/tags/wireguard" class="mention hashtag" rel="nofollow noopener" target="_blank">#wireguard</a>. For <a href="https://mastodon.green/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustlang</a> udp means: do it yourself, no existing crates, allow for missing data, and <a href="https://mastodon.green/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a> for the udp packet contents.

Tomáš Slíž<a href="https://mastodon.social/@davedelong" class="u-url mention" rel="nofollow noopener" target="_blank">@davedelong</a>, they mention <a href="https://social.rust-lang.org/@rust" class="u-url mention" rel="nofollow noopener" target="_blank">@rust</a> <a href="https://iosdev.space/tags/Serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#Serde</a> 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.”

Jons MostovojsIf you're in King's Hall at <a href="https://social.doma.dev/tags/RustNationUK" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustNationUK</a>, I found the crate Adam Harvey told us not to post on the social media about!<a href="https://deps.dev/cargo/serde" rel="nofollow noopener" target="_blank">https://deps.dev/cargo/serde</a><a href="https://social.doma.dev/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a> <a href="https://social.doma.dev/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> <a href="https://social.doma.dev/tags/rustnation" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustnation</a>

argv minus one<a href="https://hachyderm.io/@fasterthanlime" class="u-url mention" rel="nofollow noopener" target="_blank">@fasterthanlime</a> I see I'm not the only one who pronounces <a href="https://mastodon.sdf.org/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a> in a way that rhymes with “merde”.

Kat Marchán 🐈<a href="https://github.com/kdl-org/kdl-rs/pull/83" rel="nofollow noopener" translate="no" target="_blank">https://github.com/kdl-org/kdl-rs/pull/83</a>the work has begun to add <a href="https://toot.cat/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a> support to <a href="https://toot.cat/tags/kdl" class="mention hashtag" rel="nofollow noopener" target="_blank">#kdl</a> 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

balletproof vestCoding question: is there something for <a href="https://beach.city/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> like <a href="https://beach.city/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a> where the serialized version of the data can be a format you define, not Just Fucking JSONBefore 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.

Larry GarfieldI'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!<a href="https://github.com/Crell/Serde" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Crell/Serde</a><a href="https://phpc.social/tags/Serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#Serde</a> <a href="https://phpc.social/tags/Serialization" class="mention hashtag" rel="nofollow noopener" target="_blank">#Serialization</a> <a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> <a href="https://phpc.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a>

Yellow FlagAnd I’ve thrown out that solution again. Instead of messing with <code>serde::Deserialize</code> which never quite works as it should, I’ve decided to extend the API and support flattened structs properly. I’ve added my solution to <a href="https://github.com/serde-rs/serde/issues/2186#issuecomment-2143387697" rel="nofollow noopener" target="_blank">this already much too long thread</a> where lots of people spent lots of time trying to make things somehow work with Serde’s APIs.<a href="https://infosec.exchange/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a> <a href="https://infosec.exchange/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a>

Yellow FlagI finally managed to create a <code>serde::Deserialize</code> implementation that would support <code>flatten</code> and <code>deny_unknown_fields</code> at the same time. The issue was mostly how the Serde API makes this task difficult for no good reason from what I can tell.I sort of see why it has to be static strings everywhere, but why static slices as well? That’s an implementation detail of the default implementation and IMHO not actually required anywhere. And why is it so hard to get to the list of fields supported by an implementation?I guess this use case was never a priority, but configuration files where a typo in a field name won’t be recognized are a major PITA…<a href="https://infosec.exchange/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a> <a href="https://infosec.exchange/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a>

Mo Bitar :ferris:🚩 SAVE THE DATEMy online talk about how to speed up <a href="https://fosstodon.org/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> serialization with <a href="https://fosstodon.org/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a> by up to 2.25x 🚀What to expect: 🙂 A simple example with JSON 🧐 How serialization in serde works 🛠️ Manually implementing the Serialize trait 🌟 Serialization with the newtype pattern ⏱️ Benchmarking with divan 🤔 Discussing the overhead of allocationsOn Tuesday, 20 February at 13:00 CET<a href="https://lunch.rs/meetups/2024-02-20" rel="nofollow noopener" translate="no" target="_blank">https://lunch.rs/meetups/2024-02-20</a>Boost? 🥰<a href="https://fosstodon.org/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a> <a href="https://hachyderm.io/@hds" class="u-url mention" rel="nofollow noopener" target="_blank">@hds</a>

Larry GarfieldI've just tagged the 1.1 release of <a href="https://phpc.social/tags/Serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#Serde</a> for <a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a>. Now with improved value object support, so you can deserialize properties directly into their own validated value object!<a href="https://github.com/Crell/Serde" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Crell/Serde</a><a href="https://phpc.social/tags/Serialization" class="mention hashtag" rel="nofollow noopener" target="_blank">#Serialization</a> <a href="https://phpc.social/tags/OSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OSS</a>

Mo Bitar :ferris:Faster Rust Serialization 🚀 <a href="https://mo8it.com/blog/faster-rust-serialization" rel="nofollow noopener" translate="no" target="_blank">https://mo8it.com/blog/faster-rust-serialization</a>A blog post about avoiding allocations and improving the performance of serialization in <a href="https://fosstodon.org/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a>!It doesn't only apply to JSON, but to any <a href="https://fosstodon.org/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a> serializer.The example in the blog post shows a speedup of up to 2.25x 🤯Feedback welcome :blobcatheart:<a href="https://fosstodon.org/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a>

Chris Gioran 💔Can anyone shed some light on why serde_json doesn't have a Serialize::to_slice() that accepts an externally provided buffer? serde_json_core has it and that's what I'll use. I guess my question is why serde_json_core would have this method but serde_json wouldn't.<a href="https://fosstodon.org/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a> <a href="https://fosstodon.org/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> <a href="https://fosstodon.org/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustlang</a>

Chris Gioran 💔Today's <a href="https://fosstodon.org/tags/glowdust" class="mention hashtag" rel="nofollow noopener" target="_blank">#glowdust</a> development livethread - finish the function serialization/deserialization code. Yesterday I left things halfway done with the deseralization of the function definitions and value storage. I couldn't figure out how to take a json map and pass it down the <a href="https://fosstodon.org/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a> chain. That's the first thing I'll need to figure out. The rest should be easy.

Mo Bitar :ferris:Now that the <a href="https://fosstodon.org/tags/Serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#Serde</a> issue is resolved by removing the binary, I want to thank <a href="https://mastodon.social/@decathorpe" class="u-url mention" rel="nofollow noopener" target="_blank">@decathorpe</a> again, not only for reporting the issue, but also for all his efforts in the <a href="https://fosstodon.org/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> and <a href="https://fosstodon.org/tags/Fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fedora</a> communities ❤For others: Please don't call things like this "drama" again. This is pushing back against mistakes that would affect the whole community. I love how much the community cares and that such problems are not ignored 🥰We are not here to only get things done, we are building a future ❤<a href="https://fosstodon.org/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a>

Michael van Niekerk 🦀 ☕️ ⚛After the big <a href="https://techhub.social/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a> ruckus, @dtolnay made this Pre-RFC, which is frankly brilliant if it were to be implemented as such.Basically 1) compile macros to WASM 2) WASM runtime keeps WASM script to only make source tokens (no network calls, etc).<a href="https://internals.rust-lang.org/t/pre-rfc-sandboxed-deterministic-reproducible-efficient-wasm-compilation-of-proc-macros/19359" rel="nofollow noopener" target="_blank">https://internals.rust-lang.org/t/pre-rfc-sandboxed-deterministic-reproducible-efficient-wasm-compilation-of-proc-macros/19359</a><a href="https://techhub.social/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustlang</a>

Ivan Enderlin 🦀Rust devs push back as Serde project ships precompiled binaries, <a href="https://www.bleepingcomputer.com/news/security/rust-devs-push-back-as-serde-project-ships-precompiled-binaries/" rel="nofollow noopener" target="_blank">https://www.bleepingcomputer.com/news/security/rust-devs-push-back-as-serde-project-ships-precompiled-binaries/</a>.A short summary of what’s happening around serde right now in Rust.<a href="https://fosstodon.org/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a> <a href="https://fosstodon.org/tags/serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#serde</a>

Mo Bitar :ferris:dtolany's dictatorship…<a href="https://fosstodon.org/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> <a href="https://fosstodon.org/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a> <a href="https://fosstodon.org/tags/Serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#Serde</a>

Larry GarfieldBased on the discussion here and in the PR, I've gone ahead and completed the PR to support null values in <a href="https://phpc.social/tags/Serde" class="mention hashtag" rel="nofollow noopener" target="_blank">#Serde</a>. If you use it currently, please review and make sure it doesn't break more than I already know it does. 🙂 <a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> I'll probably merge in a week or so, baring any contrary reviews.<a href="https://github.com/Crell/Serde/pull/25" rel="nofollow noopener" target="_blank">https://github.com/Crell/Serde/pull/25</a>

Matt CampbellRust drama

Recent searches

Search options

Administered by:

Server stats:

#serde