Ten or more years ago Microsoft’s interest in dynamic languages materialized under the Dynamic Language Runtime project, a project that aimed to port such languages to the CLR to allow them to inter-operate with the .NET languages under the same roof. I shared my thoughts about in a review of Pro DLR in .NET 4.0 book.
The following excerpt from that review reveals the essence of the DLR:
A runtime that sits atop the CLR and hosts dynamic languages.It makes implementing a new language, be it a dynamic, application or domain specific one, much easier to build since you can use ready made parts and leverage existing functionality; for example instead of implementing a GC you plug into the CLR’s GC.
IronPython and IronRuby were just such dynamic language ports and there was also third party IronJS. However, within a short space of time, Microsoft axed them. As to why, there was a lot of speculation, as we reported in Microsoft’s Dynamic Languages Are Dying:
There have been suggestions that the once well supported project (Ruby on Rails) simply clashed with Microsoft’s recent ASP .NET MVC developments.
After all you don’t really want two MVC frameworks in the same .NET development space and while IronRuby may just be a language it is natural to think of Rails when considering an MVC framework to use with it. Perhaps it was feared that comparisons between a .NET Rails and ASP .NET MVC might not have been flattering.
Taking the matter further, I even posed a question to Scott Hunter, Director of Program Management .NET, on his January 2019 blog post “Starting the .NET Open Source Revolution“, with:
Why were the DLR based languages such as IronPython and IronRuby gone defunct? Were they victims of their success in that they were competent competitors to the .NET languages like C#?
Scott’s answer was:
There were points in time where with .NET we just tried to do too many things at the same time. The DLR languages were more victims of us just trying to focus the basics of .NET again.
During that time frame we were building new web frameworks based on competition and starting our open source journey. Back then we gave customers so many options that it made the platform appear more complicated.
Since then Microsoft has changed direction. It now loves open source and everything Linux, even to the extend of porting SQL Server to it, see SQL Server on Linux, Love or Calculated Move?. Microsoft owns GitHub, see Microsoft GitHub – What’s Different, and Visual Studio Code, the code editor that it open sourced in 2015 has continued to grow towards being a sophisticated IDE.
The Python series was released last year and we covered it in
Learn Python with Microsoft.
- Declaring variables (3:53) followed by Demo (6:55)
- Working with strings (3:19) followed by Demo (2:47)
- Converting strings to numbers (2:13) Demo (4:37)
- Handling errors with try/catch/finally (3:18) Demo (3:34)
- Boolean logic with switch and other syntax (7:08) D (9:04)
- Creating arrays (1:30) followed by Demo (1:46)
- Functions (9:33) followed by Demo (8:02)
- Promises for long running operations (9:33) Demo (8:02)
- Async/await for managing promises (9:33) Demo (8:02)
- Package management (5:06) followed by Demo (6:54)
- How to install Node.js on Windows
- How to set up VS Code for Node.js development
- How to work with files and directories with Node.js
- How to create a GET API with Node.js and Express
- How to use advanced debugging features in VS Code
All of the videos are easy to follow intending to kickstart your journey into coding with Microsoft.
GitHub Command Line Tool Reaches General Availability
GitHub has announced the general availability of its new command-line tool, GitHub CLI. The tool lets you issue pull requests and work with issues from the command line to give developers a more seaml [ … ]
AWS Training On Coursera, edX and Future Learn
Amazon Web Services is running three versions of a new free training course on how to build modern Java apps on both Coursera and edX.
or email your comment to: email@example.com