I understand where you're coming from. My organization is flexible and isn't ideologically committed to one particular platform. Microsoft's community promise is just that, a promise. It can be changed or revoked at any time in the future.
I've been encouraging adoption of open system practices and tool diversity in my organization. I believe Racket will bring value for my particular needs. I think, although I freely admit I am not sure, that there is a benefit to creating a .NET package for Racket. Will the benefits justify the development investment? I don't know. It seems a worthwhile area to explore. On Monday, January 16, 2017 at 2:11:11 PM UTC-5, Neil Van Dyke wrote: > This doesn't help anyone who's committed fully to a platform, but if one > is not, or when one has the opportunity to evolve, it should be mentioned... > > When an organization emphasizes real open systems (which currently > probably means HTTPS Web services, talking in XML or JSON, and perhaps > SQL, all according to well-defined schema), it's easier to interoperate > with most any platform -- current and future, including all mainstream > languages, innovative new languages, pure Web browser JavaScript, iOS > apps, Android apps, and whatever comes along next. > > (Just because a platform has a standards document, or an open source > implementation was arranged, doesn't mean a platform wasn't created as a > proprietary business move, with much of the usual implications.) -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
