Re:Nitra, JetBrains’ research project for language tooling, ...
by citizenmatt on Tuesday May 27, 2014 @07:17AM
(#7803854)
Mono support isn't at the top of our priority list right now. However, the Nemerle binaries work on mono, so it's possible you could build the command line compiler and sample applications under Linux. If you get it working, a pull request would be very cool!
Re:Nitra, JetBrains’ research project for language tooling, ...
by phpnode on Tuesday May 27, 2014 @07:13AM
(#7803844)
The rest of JetBrain's products are cross platform, so there's a good chance that this will be in future.
Re:Nitra, JetBrains’ research project for language tooling, ...
by citizenmatt on Tuesday May 27, 2014 @07:19AM
(#7803860)
We do have a lot of future plans for Nitra, but for now, it's worth pointing out that the products that are cross platform are Java based, while Nitra is based on .net. The project is currently Windows only.
Re:Nitra, JetBrains’ research project for language tooling, ...
by mythz on Tuesday May 27, 2014 @11:05AM
(#7804835)
Interesting, what made you decide on .NET (i.e. given you're predominantly JVM based)? Was it just based on the Nermerle's team preference?
Re:Nitra, JetBrains’ research project for language tooling, ...
by citizenmatt on Tuesday May 27, 2014 @12:22PM
(#7805239)
I wouldn't say we're predominantly JVM based. We've also got ReSharper, dotTrace, dotMemory, dotCover and dotPeek, which are all .net based.
But basically, it's because Nitra is an extension and evolution of work done on Nemerle, and Nemerle is a .net language.
Re:Nitra, JetBrains’ research project for language tooling, ...
by mythz on Tuesday May 27, 2014 @03:23PM
(#7806303)
Is ReSharper written with C#? I thought I heard it was written with C++.
Re:Nitra, JetBrains’ research project for language tooling, ...
by citizenmatt on Tuesday May 27, 2014 @05:37PM
(#7807027)
It's written in C#, with some of the Visual Basic support written in VB. Parts of ReSharper for C++ are written in C++ and C++/CLI.
I had an idea of an IDE that instead of being built around a language was built around frameworks and workflows in that language, which would require deep understand of the target language. This seems like a great step in that direction, but it's a shame I can't run it on Linux :(