Jared Parsons

Work on compilers and languages. Creator of VsVim.
He/Him
#BlackLivesMatter

[Jared Parsons @jaredpar]

Full Span<Tee> shirt

#span #dotnet

[Jared Parsons @jaredpar]

@nick_guerrera More predictions

[ErikEJ @ErikEJ]

dotNET blog: A faster, lighter C# Dev Kit https://t.co/fpzmRo6b37

[EgorBo @EgorBo]

(Deleted my prev. post JIC) .NET devs should really stop introducing blazing fast (de)serializers 🙂. The world is going through a period when anyone using e.g. GLM5.3 can easily find and exploit a memory safety issue - many projects are overwhelmed by 1000s of potential CVE reports, though not everyone chooses to report what they find. Deserializers often accept untrusted input from external sources, making them prime targets for attacks. Embrace safety over saving a few nanoseconds and fewer heap allocations.

[Jared Parsons @jaredpar]

@KooKiz @EgorBo Possible it was done to reduce friction when porting from C. Didn't want devs to have to add a loop in a struct ctor.

[Jared Parsons @jaredpar]

@KooKiz @EgorBo My guess though is that it has to do with C. A lot of struct features were done such that it would be easy to port equivalent C code to C#. Initializing a fixed buffer in 1.0 ... not sure if there was a good concise syntax for that

[Jared Parsons @jaredpar]

@richcampbell Alternative approaches to consider are putting a side car file on disk (simple json style file) and reading that at runtime for the mapping.

[Jared Parsons @jaredpar]

@richcampbell That approach though is working around reproducible builds by making them not a reproducible build. The original path being baked into the module init will break reproducibility

[Jared Parsons @jaredpar]

@jcoehoorn @davidfowl Plumber: you’re calling me to install a sink?
Me: why don’t you take a look in that cabinet and tell me what you see.
Plumber: I take it back. I’ve only seen that once in my career. I may have to come back later with other parts.

[Jared Parsons @jaredpar]

@jcoehoorn @davidfowl You know what it’s going to be: plumbing. It’s always plumbing.

[Jared Parsons @jaredpar]

@_cartermp Yep

[Jared Parsons @jaredpar]

@AbdurRafaySale2 Sorry. This is Redmond only

[Jared Parsons @jaredpar]

Interested in working in .NET Tooling? My team is hiring for a few roles. This is a great to impact the .NET ecosystem, work with devs all across Microsoft and help drive the .NET platform forward.

https://t.co/IcSLpDXPoS
https://t.co/lSxsm4pqxB

[Sergiy Teplyakov 🇺🇦 🇺🇸 @STeplyakov]

Hey #dotnet people! Exciting news! I've launched my YouTube channel: "Dissecting the Code".

It's going to be very similar to my blog, where I'll cover .NET internals, performance tips & tricks, and more deep dives. #csharp

I've already published the first two videos:
➡️ Episode 0: What You'll Learn Here
➡️ Episode 1: Dissecting Variable Lifetime
I hope you'll like it! Please share, subscribe, and let me know what you think! Your support means a lot to me. 🙏
Links to the channel & videos are 👇

[Jared Parsons @jaredpar]

@riosgeorge @davidfowl @GarethSeth We want the end result to look as close to possible if you had started with a project in the first place.

[Jared Parsons @jaredpar]

@riosgeorge @davidfowl @GarethSeth A top priority of this effort is ensuring we have a smooth, and aesthetic, transition to a real project. Many of our design decisions come down to "okay, but how does that work once the customer transitions to a real project?"

[David Fowler @davidfowl]

We’re about to take C# to the next level. Look out Python 👀

#dotnet #csharp

[Jared Parsons @jaredpar]

@EgorBo @STeplyakov @davidfowl Once you invoke unsafe you are effectively responsible for the safety of your code.