News for hackers. Stuff that matters.
Re:Cello: Higher level programming in C by icebraining on Monday July 15, 2013 @07:34PM (#6049196)
Why can't we embed vim or emacs in a web document?

We can, that's not the issue. The problem is that if you embed an editor - any editor - into the project, you're forcing everyone to use it, while currently each developer has the freedom to choose his own.

And if don't embed the editor, then there's nothing to discuss; one can already use web based editors if one wants to, and I can use VIM ;)

Can I please point out that building graphical interfaces in ASCII is just about as bone-headed as my suggestion? :)

The whole reason I like VIM is because it barely has any graphical interface. The whole experience is extremely content focused, without a mess of buttons and toolbars obstructing the vision. I talk to it[1], it does what I tell it, and it stays out of my way.

So I agree, but it doesn't apply in this case :)

[1] http://yanpritzker.com/2011/12/16/learn-to-speak-vim-verbs-n...

Re:Cello: Higher level programming in C by williamcotton on Monday July 15, 2013 @08:13PM (#6049329)
What if <THIS SPACE LEFT BLANK> and the end-user can supply their own editor?

But then, how do we ship around the source editors meta data that is REALLY important, like, custom DSL syntax highlighting?

Do we need a universal syntax highlighting engine? What other universal engines do we need to build interfaces in to Emacs and Vim and Eclipse and XCode and Visual Studio in order to tackle some of these issues?

Re:Cello: Higher level programming in C by icebraining on Monday July 15, 2013 @08:45PM (#6049417)
You just need some standard, structured format for describing the syntax of a particular language. And we already have these; we use them as source for the parsers of the languages themselves. So it's mostly a question of augmenting them to provide highlighting-specific hints to the symbols.