News for hackers. Stuff that matters.
Re:An Introduction to Nitra by breckinloggins on Tuesday November 12, 2013 @04:09PM (#6721119)
This gets us ever closer to the goals of the elusive (and presumably abandoned?) Grok project [1].

I'd love to see syntax highlighters (like Pygments), editors and IDEs, autocompletion providers, debuggers, and all other language-related tooling consume a standardized canonical "language description format". Making a new language? Bam! It's automatically supported by Visual Studio, Eclipse, Emacs, vim, Sublime Text, gdb, Pygments, the list goes on.

The extension capabilities are also awesome. Let's say I have a huge project and, at a certain level of abstraction, users aren't allowed to use fprintf(stderr, ...), they need to use LOG(...). It would be great to have a file in your project that can tell your environment to give you the "red squigglies" and autofix information for such situations.

http://bsumm.net/2012/08/11/steve-yegge-and-grok.html

Re:An Introduction to Nitra by nswanberg on Tuesday November 12, 2013 @05:04PM (#6721568)
Steve spoke about Grok earlier this year: http://www.youtube.com/watch?v=uRO3dNJx5Dw (sadly the video is only worth listening to), and at the end of the talk guesses there would be more public information 1.5 years from then.
Re:An Introduction to Nitra by turbolent on Tuesday November 12, 2013 @01:09PM (#6719533)
Looks very similar to OMeta (http://tinlizzie.org/ometa/)
Re:An Introduction to Nitra by hhariri on Tuesday November 12, 2013 @01:11PM (#6719557)
Does OMeta allow extending existing languages or provide tooling around it such as analysis, refactoring, navigation?
Re:An Introduction to Nitra by turbolent on Tuesday November 12, 2013 @02:14PM (#6720150)
It's object-oriented and especially designed to be extensible. The slides on the pages contain many examples. It's fairly stand-alone and isn't integrated into an IDE. However, it's small, which allows for easy implementation (see original OMeta in Smalltalk, Ometa/JS, Ometa#, etc.) and could be used as a base for implementing these IDE features.

I'd love to see a cleanup of OMeta/JS and combining it with CodeMirror.

Re:An Introduction to Nitra by agumonkey on Tuesday November 12, 2013 @01:20PM (#6719641)
seems more like an metaIDE framework
Re:An Introduction to Nitra by SuddsMcDuff on Tuesday November 12, 2013 @02:10PM (#6720114)
I hope some of the work they've done filters back into Nemerle. A lot of people were very excited when JetBrains picked up the Nemerle team but it's not clear that they have any intention of supporting the project - they just wanted the team...
Re:An Introduction to Nitra by hhariri on Tuesday November 12, 2013 @02:12PM (#6720133)
The Nemerle team is still active and the project is very much alive. In addition, Nitra uses Nemerle.
Re:An Introduction to Nitra by radicalbyte on Tuesday November 12, 2013 @01:46PM (#6719886)
I've been waiting for this for a year; the idea of having a language-within-a-language is extremely powerful.

Take our product: we have javascript, typescript, XML and SQL stored in strings in our C# codebase. As you can expect, these are really hard to maintain, and just has hard to move to separate templates.

Oh, did I mention that we also have our own templates, our own DSL, handlbar templates, jQuery templates and templates used in various libraries.

Nitra can support that all in one tool.

Re:An Introduction to Nitra by sebkomianos on Tuesday November 12, 2013 @06:03PM (#6722030)
Am I being too simplistic when I think the following holds?

Easier to make a DSL => Wider adoption of new languages => Better grounds for experimentations => Much more creative stuff => More accessible technology

Re:An Introduction to Nitra by hhariri on Wednesday November 13, 2013 @01:36AM (#6723745)
Don't see why not...
Re:An Introduction to Nitra by _random_ on Tuesday November 12, 2013 @02:46PM (#6720416)
This is so awesome! I hope the resulting assemblies will be PCL though.