Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If they're going to write their own compiler/linker/assembler suite, why even bother remaining compatible with C? Why not just create a specifically-optimized "kernel-ese" DSL?


But that's what C is.

edit: my argument can be summarized in sections 1 and 2 in an essay I wrote for a class a year ago: http://people.cs.vt.edu/~scschnei/ece5530/languages.pdf


OTOH several other OS projects have their own DSLs: Oberon, Vault, BitC, and Sing#.


I think we're abusing the title "Domain Specific Language." I'm only familiar with BitC and Sing# on that list, but I call those systems programming languages. Granted, one could consider systems programming the domain, but since systems programming is so ubiquitous in computing and for a long time that was the only kind of programming, I think it's inaccurate to call those DSLs.

Anyway, with the exception of Oberon, the others are still research projects. I don't think a research language is appropriate for implementing the Linux kernel.

I do hope that in the future, something as important as the Linux kernel is implemented with a modern systems programming language - it would indicate progress - but Linux is an immediate need.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: