via @dotnet : VSTest is Removing its Newtonsoft.Json Dependency

https://ift.tt/PYIZ0Ny
#VSTest #NewtonsoftJson #SystemTextJson #JSONite #dotnet11 #VisualStudio #VS2024 #dotnetTest #TestExplorer #NuGet #SecurityUpdate #SerDe #JsonDependency #BreakingChange #DotNe…

Nice surprise, @MediaArea have uploaded a bunch of #NTTW9 videos including mine on JSONID:

https://www.youtube.com/watch?v=ZMVb3Bc_irc

Check out their YouTube, and also I'd love to hear feedback on JSONID too. Please follow it on GitHub: https://github.com/ffdev-info/jsonid/

#digipres #serde #FileFormats #JSON #YAML #TOML

Annoying... There is a bug open for serde since 2017 conserning f64::NAN/ JSON null value.

No justification about why no one seem to want to fix it.

I don't know why you wouldn't try to fix this in 9 fucking years!

At least make it so that serializing then deserializing a f64::NAN don't throw out the entire structures?

Or alternativelly, (still annoying to me but coherent) throw an error when serializing NAN value? Just so that you don't end up with some unusable json file?

My preference would be to be able to handle nan, and infs value gracefully without needing me to write my own damned serializer/deserializer.

#rust #serde

Unfair #rustlang #serde Quiz: What's the difference between these four types' deserialization behavior (ignoring the type name)?

#[derive(Deserialize)]
struct One {
field: Option<String>,
}

#[derive(Deserialize)]
struct Two {
#[serde(default)]
field: Option<String>,
}

#[derive(Deserialize)]
struct Three {
#[serde(deserialize_with = "Option::deserialize")]
field: Option<String>,
}

#[derive(Deserialize)]
struct Four {
#[serde(default, deserialize_with = "Option::deserialize")]
field: Option<String>,
}

Today, I once again wake up worrying about #Rust 's future.

Why is a shitbag such as #dtolnay still allowed to single-handedly maintain fundamental libraries for the ecosystem? Why is he part of Library API team? How is he not permabanned for single-handedly permanently damaging Rust by killing off comptime reflection over his racism? How is he not permabanned for the power play he attempted to pull with his "RFC" after pushing pre-compiled binary to serde without notice? Why are MIC companies routinely tolerated at Rust conventions? Why does no one talk about it, despite the problems not being solved? Has #Ruby takeover taught people nothing? Will Rust survive another year without turning into #fashtech?

So many questions. I think about them every time I use Rust, which is often.

Apropos of nothing.

#RustLang #serde #FOSS #OSS #OpenSource

Just released a new crate, it lets you serialize output of methods using `serde`.

https://github.com/j-g00da/serde-more

#serde #rust #rustlang