Jon Sequeira

Thanks, @gbaydin. For the most part these simpler outputs are our goal, so you can expect to see changes here to use the F# printers by default. The current defaults...

My current thinking is that we can allow this decision to be different per subkernel by adding support for subkernels specifying their own formatting rules, so for example the `FSharpKernel`...

> I believe .NET objects (unqualified) simply don't have a good default for revealing their expanded structure, either internal or external, besides ToString() (with some expansions for known types like...

> Anyway we can think this over again for F#, and perhaps for C# too I've seen that there are a few different use cases for printing output. At the...

> Do we have any evidence about how often users want more expansive/structured views? Yes, though not yet in a formal user study. In both the educational and developer productivity...

The screen shots here are very outdated. I think this issue should likely be closed or at least reassessed in light of (among other things) the GA of Plotly.NET v2.0.0...

Thank you @nhirschey! @houstonhaynes, the `Area-F#` tag indicates issues that are specific to F#. We've largely been focused on areas that affect all users. It's difficult to support every language...

Consider using [Python environment tools](https://github.com/microsoft/python-environment-tools) for more efficient environment discovery.

Currently, the closest thing to this is under the `Connect to new cell kernel` command:  This will insert cells into the notebook rather than simply running the package acquisition...

This is partially addressed by #3810. I'm going to close it because actually running the NuGet acquisition code on the user's behalf requires a much wider design discussion, but #3810...