3 ms·

I get the whole Rust -> Iron thing, but when I see Iron prefix I think of dotnet because of https://github.com/ironlanguages https://github.com/ironlanguages an

by graynk 2y ago

I get the whole Rust -> Iron thing, but when I see Iron prefix I think of dotnet because of https://github.com/ironlanguages https://github.com/ironlanguages and https://ironsoftware.com/ https://ironsoftware.com/

TheRealPomax 2y ago
Given that it's an implementation of Microsoft's RDP, not sure that's a "but" in this very specific case =)
badlibrarian 2y ago
I think of IronPython and IronRuby and IronScheme, early attempts at Microsoft trying to combine cornmeal with .NET and open source and calling it a burrito. https://ironpython.net/ https://ironpython.net/ https://en.wikipedia.org/wiki/IronRuby https://en.wikipedia.org/wiki/IronRuby https://en.wikipedia.org/wiki/IronScheme https://en.wikipedia.org/wiki/IronScheme
- graynk 2y ago
  yep, that's my first link
- SpaceL10n 2y ago
  Iron Icons comes to mind as well https://www.webcomponents.org/element/@polymer/iron-icons https://www.webcomponents.org/element/@polymer/iron-icons
tracker1 2y ago
That was my first thought as well. Surprised to see they're still seeing updates. Also surprised to never see an IronJS or IronTypescript or similar really.
- snoman 2y ago
  It be weird to see MS make an IronTypescript given that they created typescript.
  - tracker1 2y ago
    TypeScript as it exists from Microsoft isn't a runtime engine.
    - ffsm8 2y ago
      Wouldn't that be IronNode, then? Especially now that node-ts is a thing
      - deleted 2y ago
        [deleted]
- int_19h 2y ago
  Early .NET (pre-4.0) included JScript.NET, which was effectively "IronJS", except that it predated the convention.
  - tracker1 2y ago
    Iron* is based on dynamic language support... JScript.Net wasn't and was abandoned well before.