4 ms·
So I read Eric Lippert's blog post on Roslyn[1], where he says the motivation for the project was because other teams within Microsoft were re-implementing part
by lmkg 15y ago
So I read Eric Lippert's blog post on Roslyn[1], where he says the motivation for the project was because other teams within Microsoft were re-implementing parts of the C# compiler piecemeal, so it made sense to expose those parts as an API. You know what that reminds me of? Steve Yegge's Platform rant. Specifically, the part where Bezos made Amazon convert all of their existing development infrastructure into services, that other units can make use of. That's what Roslyn is, on a much smaller scale: refactoring an application (the compiler) to be services-oriented platform.
http://blogs.msdn.com/b/ericlippert/archive/2011/10/19/the-roslyn-preview-is-now-available.aspx http://blogs.msdn.com/b/ericlippert/archive/2011/10/19/the-r...
- mullr 15y agoNot really, no. It's more like a compiler as a library with a nice API.
- barrkel 15y agoLibraries can be platforms too. Platforms are a mode of operating when providing, on an ongoing basis, something that third parties use. There are several "promises" around platforms: a promise not to break compatibility, a promise not to coopt client software features, and - oddly enough - a promise to be incomplete, so that third parties have opportunities to build.
- scott_s 15y agoThe authors certainly see it in this way: The transition to compilers as services dramatically lowers the barrier to entry for creating code focused tools and applications. From http://msdn.microsoft.com/en-us/hh500769 http://msdn.microsoft.com/en-us/hh500769 I agree with the parent. Yegge's platform rants is what I thought of, too.
- contextfree 15y agoNot only that, but iirc the project Steve Yegge is actually working on at Google is something along the same lines - a code analysis platform (for the JVM I think?)