3 ms·

The language doesn't seem like the interesting part here. Bosque appears mainly to be a vehicle for exploring a different way of thinking about compiler IR. Fro

by rossng 6y ago

The language doesn't seem like the interesting part here. Bosque appears mainly to be a vehicle for exploring a different way of thinking about compiler IR. From the MSR site[1]: > In the Bosque project we ask the question of what happens if the IR is designed explicitly to support the rich needs of automated code reasoning, IDE tooling, etc. With this novel IR first perspective we are exploring a new way to think about and build a language intermediate representation and tools that utilize it. Our initial experiments show that this empowers a range of next-generation experiences including symbolic-testing, enhanced fuzzing, soft-realtime compilation with stable GC support, API auto-marshaling, and more! [1] https://www.microsoft.com/en-us/research/project/bosque-programming-language/ https://www.microsoft.com/en-us/research/project/bosque-prog...

dunk010 6y ago
I know that Microsoft are all about grabbing as much developer mindshare as possible these days, but does nobody remember Steve Yegge and is Grok system at Google? It's basically this, just ten years ago. Having the IR not throw away anything so that the tooling can have a richer interaction. I guess the best way to be successful is to bury your sources.
- sterlind 6y ago
  Grok seems to have been open-sourced as Kythe, and I suspect it was significantly nerfed like other things they've released (e.g. bazel) Additionally, it looks like Kythe was never fully stabilized, and there's been no widespread usage of it. It's shovelware. I don't think you should blame MS for not citing an internal tool that they never properly released.
- goto11 6y ago
  The Roslyn C# compiler also doesn't throw anything away - you can recreate the source from the AST, completely with white-space and comments. This is necessary to support safe refactorings, so I don't think this is a novel idea. IntelliJ must have supported something like this for ages. Bosque sounds like something beyond Roslyn, but it is not clear to me what.

by rossng 6y ago

dunk010 6y ago

I know that Microsoft are all about grabbing as much developer mindshare as possible these days, but does nobody remember Steve Yegge and is Grok system at Google? It's basically this, just ten years ago. Having the IR not throw away anything so that the tooling can have a richer interaction. I guess the best way to be successful is to bury your sources.

sterlind 6y ago
Grok seems to have been open-sourced as Kythe, and I suspect it was significantly nerfed like other things they've released (e.g. bazel) Additionally, it looks like Kythe was never fully stabilized, and there's been no widespread usage of it. It's shovelware. I don't think you should blame MS for not citing an internal tool that they never properly released.
goto11 6y ago
The Roslyn C# compiler also doesn't throw anything away - you can recreate the source from the AST, completely with white-space and comments. This is necessary to support safe refactorings, so I don't think this is a novel idea. IntelliJ must have supported something like this for ages. Bosque sounds like something beyond Roslyn, but it is not clear to me what.