Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nitra, JetBrains’ research project for language tooling, goes open-source

blog.jetbrains.com

Post reply on HN
Print view View original

11–20 of 42 posts

Re: Nitra, JetBrains’ research project for language tooling, goes open-source

#12

Post by shadowmint »

Can't wait to have a play with this (once I dig up my windows laptop...).

I have such amazing respect for the amazing products from jetbrains; having toys to play with like this is just fantastic.

I'm particularly interested in the component based grammars; I'd don't quite understand how you can get away with not breaking the 'parent' grammar when you drop an arbitrary child grammar inside of it, but quite looking forward to finding out~

Re: Nitra, JetBrains’ research project for language tooling, goes open-source

#13

Post by jimmcslim »

phpnode wrote: post #8
girvo wrote: post #2

Hah! I've been looking for something like this lately, to have some platform to integrate Hack and TypeScript into some IDE. TextAdept with LPEG has been nice, Komodo Edit/IDE would be better but their docs are out of date, Sublime Text is great but you're too limited in UIs you can build. I had an idea of an IDE that instead of being built around a language was built around frameworks and workflows in that language,…

The rest of JetBrain's products are cross platform, so there's a good chance that this will be in future.

Given the renewed spirit of open-ness at MS, and more support from Xamarin for Mono, there's a chance that this might be sooner rather than later?

Re: Nitra, JetBrains’ research project for language tooling, goes open-source

#14

Post by jimmcslim »

I wonder if the open-sourcing of Microsoft's Roslyn, C# compiler project, had an impact on this decision?

At any rate, I might have a look at this and see if a grammar for Delphi can be built... the state of tooling on that platform is quite frankly dire.

Re: Nitra, JetBrains’ research project for language tooling, goes open-source

#16

Post by citizenmatt »

jimmcslim wrote: post #14

I wonder if the open-sourcing of Microsoft's Roslyn, C# compiler project, had an impact on this decision? At any rate, I might have a look at this and see if a grammar for Delphi can be built... the state of tooling on that platform is quite frankly dire.

No, it's always been the plan to open source Nitra. It's come from the team who built Nemerle, which is open source, and the team obviously wanted to continue in this manner. And JetBrains has a pretty good track record with open source - e.g. the IDEA platform that is IntelliJ's Community Edition is fully open source.

Re: Nitra, JetBrains’ research project for language tooling, goes open-source

#17

Post by S4M »

lapusta wrote: post #7
S4M wrote: post #3

So, this will be the Emacs Lisp of IntelliJ?

It's written in Nemerle, that runs on top of CLR. I believe it's targeted to .NET, VisualStudio & Resharper audience.

I don't see how that is addressing my point. Emacs Lisp is the scripting language of Emacs, and you can use it to build AST to deal with syntax highlighting and autocompletions amongst other. And that's what Nitra is intended for, and it doesn't matter that it is written in Nemerle.

Re: Nitra, JetBrains’ research project for language tooling, goes open-source

#18

Post by citizenmatt »

shadowmint wrote: post #12

Can't wait to have a play with this (once I dig up my windows laptop...). I have such amazing respect for the amazing products from jetbrains; having toys to play with like this is just fantastic. I'm particularly interested in the component based grammars; I'd don't quite understand how you can get away with not breaking the 'parent' grammar when you drop an arbitrary child grammar inside of it, but quite looking fo…

You can consider an extensible grammar as a "nested" grammar. You have certain extension points in the "parent" and you can attach a new grammar here.

For example, it would be easy to take a C# grammar and add a new operator, such as the null propagator "?.", since the list of operators is extensible. This wouldn't break anything, as it's just a new token for a binary expression.

Or, you could add something bigger, such as LINQ, by extending C# 2.0's Expression syntax rule with a LINQ query expression.

Post reply on HN