Deep .NET: An even DEEPER Dive into LINQ with Stephen Toub and Scott Hanselman

[@VanillaCaramelFudge]

I am totally in favor of a deep dive series. This is great

[@yonatan2608]

exactly.

[@soberacidtrip]

Question for Stephen for a future video: I often hear you say "If I could go back and do Tasks/async await differently..." but you never really elaborate. I would love to know what things you would do differently!

^ same

[@alexisfibonacci]

And what are they doing for Green Threads?

[@guiorgy]

Second that

[@guiorgy]

​@@alexisfibonacciwasn't that abandoned?

[@dvanrooyen1434]

Likely because it’s based on a state machine rather than concurrent patterns . Remember it’s only syntactic sugar but is often implemented in cases where developers intend for true asynchronous cases and it ain’t all that…

[@QuaKx]

These Deep dive series is amazing. For an experienced dev this is gold, because it's actually quite a lot of information that you didn't already know.

[@liquidpebbles]

The tangent on simd was fascinating. I have pondered on optimizing loops before and now learning that they can be vectorised and have multiple operations happen at a time just expanded my views. Please keep doing this series. This is the stuff we developers need out on the webs. Top tier computer scientists with decades of experience just talking about concepts at all different levels. Epsecially for people like myself who work for themselves or maybe don't have colleagues or friends in the developer space, these kinds of coversations are incredibly valuable.

[@alexisfibonacci]

Nick Chapsas has a video on those array parallelisations.

[@draganradovac8803]

It's great to have the internals explained and demonstrated showing every step in detail. Really liked the "(unit)i < (unit)source.Length". Awesome guys.

[@АртемБаляница]

I adore these deep dive series. Can't wait for a deep dive into Entity Framework to finally understand how this magic works.

[@frogger3d]

These sessions are great. I would love a DEEP dive into the reactive extensions.

[@renatogolia211]

Also how IAsyncEnumerable methods are implemented would be cool.

[@taconaut8276]

Love this series on several aspects. Both hosts work very well together. It gives great insight into 'magic' we use on a daily basis and now take for granted. We see what thoughts and considerations go into optimization, after a solid basis has been created. Which in the end opens up the mind to see things through a different lense and gives ideas for new concepts and patterns. Great job!

[@erlittle]

I love this series of deep dives. Even more so, the mentioning and tie ins to lowered and IL. This stuff is gold no matter you level, there is something to take away for everyone. Even internal to MSFT, ive told coworkers and other devs about this (and the async one especially).

[@s.hosseinhosseini8330]

It's amazing where we started from in the previous video and where we got down to what is happening in the lowest levels. I love this series.

[@ChrisPerone-cl3gf]

Thank you for this video series on LINQ, very educational!

[@VitalyPavluk]

DEEP Dive series are amazing!! They are not "bla-bla-super-duper" talks but a diamond gems that reveals hidden aspects of technology!! Keep up such an excellent talks!

[@MatteoGariglio]

I'm amazed by how clear and insightful it is. Stephen's ability to break down complex topics into understandable, low-level explanations is truly commendable. This video has been incredibly helpful in deepening my understanding. A huge thank you to Stephen Toub and the team behind this invaluable instructional content!

[@marklord7614]

Holy crap, how cool is this. Another one.

[@shanselman]

Darn tootin’

[@mrqbboy]

This is pure gold. Very educational and doesn't ever get boring. Great job, Scott and Stephen. I hope more of these come out.

[@alexsheppard-godwin7855]

This is the awesome, super interesting and ties how of things I thought I knew but didn't quite have right into a super clear narrative.

[@estepor]

At 38:38, had the if statement explicitly checked for i>=0 && i

[@bshrikant123]

Long overdue to bring best of architects and programmers to show us how its done, looking forward to more.

[@fabii5555]

Can't wait for the next episode of Deep dotnet. There is always so much to learn!

[@MikeSigsworth]

That tangent about SIMD was awesome. It's not something I've ever dove into. I had to pause and ask CoPilot what you guys were talking about. Really awesome stuff guys! Love this series!

[@naughtiousmaximus7853]

No way, I am just approaching half of the previous one. This is awesome!

[@seancpp]

Loving this content--Deep dives that don't treat the viewer like an idiot. There's not enough software dev content out there that assumes the viewer is already an expert.

[@letsplay1122]

This is amazing, please make more of these!

[@SlackwareNVM]

This was amazing. I would also love to see an implementation of Thread Pool and a Task Scheduler.

[@grsevero]

Love the SIMD conversations

[@verdantblast]

Seeing Stephen Toub, it suddenly occurred to me that we seem to be seeing Performance Improvements in .NET 9 soon? Time flies.

[@yufgyug3735]

invaluable content. uncovers much more than just reading documentation and/or books

[@marklnz]

Deep dotnet! Deep dotnet! Love the idea - please give us more!

[@mykhailokozlov6641]

I have just one word on my mind - wow! Keep doing such deep videos!

[@CuriouslyContent]

Tell us in the comments if this is what you want to see... Yes. Never waste a Toub Tangent. That's where deep learning happens!

[@sjark5000]

This series is great. Please do continue with it!

[@fernandohelwanger2417]

This series is absolutely amazing! Thank you so much, great content!

[@FawzTech]

Loved it! This is great, thank you

[@codewithfrenchy]

Thx guys, please do more of theses!

[@TheOneAnOnlyGuy]

Fantastic content, thanks Scott and Stephen!

[@DestinationDub]

Stephen: Sorry, I'm probably getting a bit nerdy. Scott: Well, tell us in the comments if this is what you want to see? Comments: THIS IS WHAT WE WANT TO SEE!!!!!!!!!!!!!!!!!!!

[@bshrikant123]

Can I suggest Stephen Toub and Joe Albahari together moderated by amazing Scott, from a designer and consumer perspectives and show us great stuff is built

[@schlott1970]

Just brilliant Scott and Stephen. Keep going these are brilliant

[@trannhan1432]

What an excellent job. Thank you!

[@stephajn]

I am loving these videos! Keep them coming.

[@SinanNAR]

loving this series

[@stevanfreeborn]

I'd definitely buy a CTRL-Z to Glory t-shirt 😅

[@BlazorMisterMagoo]

Wish I could explain code as well as you do - loving this Deep dotnet

[@MladenMihajlovic]

Awesome deep dive - we want more! ;-)

[@yusufcirakkk]

Liked the video already because you know, Stephen Toub.

[@__angle]

Thank you so much this kind of very interesting topic are really great ! Please more !!!! 🥰😍🥰

[@guiorgy]

Would it be possible to have a Source Generator that recognizes linq call chains and generates dedicated enumerators for those?

[@fxfighter]

In regard to optimization at 48:00, why are type checks being used within an entry method at all? Why can't there be overloads and generics to support these separate paths instead? Then tree trimming would work properly and it should just be straight up faster as there's slightly less code to execute.

[@roman-urum]

Thank you, this content is like intellectual honey. Looking forward your next deep C# videos.

[@AndrzejPauli]

Ohh boy!! MOAR! 🙂

[@DanGolick]

We want part three!

[@mfsbo]

33:00 a very good example of how programmers think

[@utubekade]

excellent optimization hints.

[@porcinetdu6944]

Great series

[@HeinrichTeitge]

Great videos, thank you!

[@cokert3]

At 1:15:34, what exactly causes the `Where` to be dropped/abandoned?

[@pagorbunov]

You do Where, then Select. When calling Select you check if your source happens to be WhereEnumerable and if so then instead of returning SelectEnumerable you combine them into single WhereSelectEnumerable and return it.

[@cokert3]

@@pagorbunov Oh, right. In my mental model, I was missing that nothing's actually executed until the call chain is "materialized" (ie, .ToList() or whatever is called). I was visualizing it as "Execute Where, pass those results to Select" and confused how we were skipping execution of the Where. What's really going on is at the end, we wind up one "thing" whose execution will "materialize" the results. And the new WhereSelect grabs the Where's arguments (source and predicate) and in effect "jumps the queue". ... I think that makes sense? Words are hard, massive respect to communicators like Scott and Steve who can communicate arcane details understandably but also precisely...

[@giovannimorleschi1750]

Continue the series!!!! xD i love this DDD(otnet)

[@egvijayanand]

57:23 Why not use var values = from ... Implicitly typed variable. Defined for this kind of scenario. No need to type it again and again.

[@jmctoob2]

These are so great!!

[@mahdiyar6725]

love to see how plinq is implemented .

[@thiagomenezes2k7]

Brilliant stuff

[@cccyberfamilydk]

Great. More of that. :) Gooooood informative content.

[@rasheed9947]

Thanks, a lot

[@PolatPINAR]

This is gold

[@higuchihiguchihiguch]

Great! Take care of your throat, Stephen!

[@bluecup25]

Everybody hop on the submersible. It's 100% safe.

[@_Miguel_Roman_]

awesome!

[@acedonk]

"Knowledge is power"

[@angelochiello]

I'm addicted.. I can't work anymore... GIVE ME MORE!!!

I think the LINQ keywords are totally superfluous and unnecessary. They can't and don't cover all use cases, like when I have to create my own extension methods to operate on enumerables. The keywords might make sense if you were loosely copying SQL syntax but instead they exactly (and awkwardly) match the extension method chaining.

[@mrqbboy]

It's time.

[@leknyzma]

did you guys stream or was this pre recorded? ?

[@shanselman]

pre recorded last week but we do it all in one take

[@CuriouslyContent]

Instead of Kill two birds with one stone, we Steven should use: feed two birds with one grain :)

[@saifeddinebenromdhane7553]

so cool

[@ivandrofly]

Part 1 - kzbin.info/www/bejne/rnzVammkft52fK8&ab_channel=dotnet

[@naveenkp7849]

Stephen Stephen Shephen

[@muhammadtariq8323]

Hard to read code. Next time may be use Dark theme for better code visibility

[@B_knows_A_R_D-xh5lo]

😊😊😊

[@Janisku7]

on your risc-V chip what havent being invented yet

[@ethanr0x]

One person too many.

[@DevelTime]

This would be superb video if only not presentation -- you found space for padding (top and bottom), for taskbar, for face frames, and well in rest you squeezed the least important content -- the code with 2px font. Awesome logic/thinking.

[@shanselman]

Given how hard we are personally working on these videos and these series, I would remind you that we are real humans doing their best. I look forward to your well-produced videos on these topics. That said, I agree this one got a little fancier and that we should zoom in on the code more. That message can be delivered without dripping sarcasm. 🥰

[@DevelTime]

@@shanselman "I would remind you that we are real humans doing their best." Of course, but even with stellar content if you don't wrap it appropriately it is not so good after all, and the effort to some degree is wasted. From the other side -- in previous episodes you reminded about font size, during this one you completely skipped this part. And either I am dreaming, or you constantly were squinting your eyes and moving forward. Think about even less fortunate people, with worse eyesight, thank you (checklist would help a lot).