5 ms·

Kind of obsoletes NetPad, and as soon as there's debugging, LINQPad can be put out to pasture. LINQPad was instrumental for me many years ago, and I appreciate

by moogly 1y ago

Kind of obsoletes NetPad, and as soon as there's debugging, LINQPad can be put out to pasture. LINQPad was instrumental for me many years ago, and I appreciate that, but that stone-age text editor is not usable for actually writing/editing code in this decade.

pjmlp 1y ago
Only if they do all GUI features and extension points, which I doubt pretty much.
- moogly 1y ago
  There's very useful stuff there for sure, just gated behind an unfathomably deficient code editor. IMO Albahari should just embed Monaco in it.
- Salgat 1y ago
  Looks like they will be adding support for VS Code, including for debugging. "In upcoming .NET 10 previews we’re aiming to improve the experience of working with file-based apps in VS Code, with enhnanced IntelliSense for the new file-based directives, improved performance, and support for debugging."
  - pjmlp 1y ago
    Still, it isn't like graphically dump a data structure like in LinQPad.
pletnes 1y ago
Linqpad is super cool in certain .net ways, but oh man the text editor component is the worst one I interact with on a regular basis. I wish that part would be replaced by neovim or monoaco or, basically, anything. The snappiness, the table visualizations and so forth - very nice. It’s also been unable to keep up with notebook tech for many potential use cases. I guess it’s a one man show and it shows. Still, massive hat tip - I use Linqpad every day because it’s super useful for playing with your SQL data.
gwbas1c 1y ago
I dunno about obsoleting LINQPad yet. Half the power on LINQPad is its UI; I'd like to see how comparable VSCode / VS are with dotnet run vs LINQPad. IE: LINQPad has a great way to visualize results. If dotnet run only outputs text, or otherwise requires a lot of plugins to visualize an object graph, there will still be quite a niche for LINQPad. In contrast, if all you're using LINQPad for is to double-check syntax, then dotnet run might be a better option. (Sometimes if I'm "in the zone" and unsure about syntax that I use infrequently, I'll write a test LINQPad script.)
pragmatic 1y ago
My main usecase for linqpad is database interactive stuff or exploratory code with .dump(). I see this as more of a complement to that. However I have worked at places that HATED powershell and we used linqpad for almost all scripting. It worked ok.

by moogly 1y ago

pjmlp 1y ago

Only if they do all GUI features and extension points, which I doubt pretty much.

moogly 1y ago
There's very useful stuff there for sure, just gated behind an unfathomably deficient code editor. IMO Albahari should just embed Monaco in it.
Salgat 1y ago
Looks like they will be adding support for VS Code, including for debugging. "In upcoming .NET 10 previews we’re aiming to improve the experience of working with file-based apps in VS Code, with enhnanced IntelliSense for the new file-based directives, improved performance, and support for debugging."
- pjmlp 1y ago
  Still, it isn't like graphically dump a data structure like in LinQPad.

pletnes 1y ago

Linqpad is super cool in certain .net ways, but oh man the text editor component is the worst one I interact with on a regular basis. I wish that part would be replaced by neovim or monoaco or, basically, anything. The snappiness, the table visualizations and so forth - very nice. It’s also been unable to keep up with notebook tech for many potential use cases. I guess it’s a one man show and it shows. Still, massive hat tip - I use Linqpad every day because it’s super useful for playing with your SQL data.

gwbas1c 1y ago

I dunno about obsoleting LINQPad yet. Half the power on LINQPad is its UI; I'd like to see how comparable VSCode / VS are with dotnet run vs LINQPad. IE: LINQPad has a great way to visualize results. If dotnet run only outputs text, or otherwise requires a lot of plugins to visualize an object graph, there will still be quite a niche for LINQPad. In contrast, if all you're using LINQPad for is to double-check syntax, then dotnet run might be a better option. (Sometimes if I'm "in the zone" and unsure about syntax that I use infrequently, I'll write a test LINQPad script.)

pragmatic 1y ago

My main usecase for linqpad is database interactive stuff or exploratory code with .dump(). I see this as more of a complement to that. However I have worked at places that HATED powershell and we used linqpad for almost all scripting. It worked ok.