Replies: 3 comments 1 reply
-
|
You might want to subscribe to #4195 as either there would be a community fork to continue, or another equivalent project to take over, just with or without Microsoft involvement. |
Beta Was this translation helpful? Give feedback.
-
|
Java supports both single file execution and REPL (JShell). Why is .NET going to throw away the latter for the sake of the former? It's a ridiculous decision. Is .NET trying to kill https://github.com/jonsequitur/dotnet-repl and https://github.com/waf/CSharpRepl? It's a great pain in the butt to create even a single file for just a few expressions. |
Beta Was this translation helpful? Give feedback.
-
|
I love how this was the official migration path for SQL Notebooks created via Azure Data Studio...which was also dropped just a few months ago. I feel like I'm on a chained deprecation path. At least they seem to have moved that to the MSSQL Extension (unlike .NET Interactive). But this is still cutting just about everything else. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This is really a hard one to fathom. I know people are grumbling about this being bad timing as the cited path away from the also demised Azure Data Studio was to Polyglot notebook and .NET Interactive but for me I'm just hugely disappointed its gone for its own sake.
Microsoft technology and Microsoft choices often have their extremely bizarre abrupt bits of nonsense - Like releasing a new client for Remote Desktop (or rather the two or three different remote desktop clients) and naming it 'Windows App' - or renaming the Office app, the Microsoft 365 Copilot App. But I would console myself that things like Visual Studio Code and Powershell exists, and that Microsofts developers had enough love of the products to produce fantastic tools like Polyglot or Powershell notebooks.
It was great to see peoples faces light up when it was possible to demonstrate notebooks with markdown, powershell, KQL, SQL, C# and graphics/process diagrams all in the same book.
This really was the holy grail of producing descriptions / knowledge and training around the Microsoft stack.
With so many Microsoft technologies Id been using notebooks to document - the process for extractions and interactions into Azure, documenting APIs available for things like Graph, ServiceNow - We'd been documenting our 100 databases and their content - we had just started also using it to explore the use of AI with our corporate systems.
Surely running fat code, or highlighting a bit of code with nothing around it by hashed comments and sticking in breakpoints - cant be, in any ones mind - the best way to explore and develop technology.
This is the sort of thing that just makes me doubt Microsoft - and there are enough haters our there already.
It wouldnt be so bad if there were some explanation.
What is the logic behind it.
I understood Data Explorer going, because that just seemed to be a data centric version of Visual Studio code - that eventually SHOULD be moved to Visual studio code.
So what are Microsoft doing
Beta Was this translation helpful? Give feedback.
All reactions