[bitc-dev] Retrospective Thoughts on BitC


25 bookmarks. First posted by tlockney march 2012.


"By now it will be obvious to everyone that I have stopped work on BitC. An explanation of *why* seems long overdue."
programming  from delicious
september 2012 by connolly
Sadness. (But fascinating read.) Retrospective thoughts on the BitC systems programming language: http://t.co/PfkDW3pt /cc @johnregehr
september 2012 by jcaudle
By now it will be obvious to everyone that I have stopped work on BitC. An explanation of *why* seems long overdue. One answer is that work on Coyotos stopped when I joined Microsoft, and the work that I am focused on *now *doesn't really require (or seem to benefit from) BitC. As we all know, there is only so much time to go around in our lives. But that alone wouldn't have stopped me entirely. A second answer is that BitC isn't going to work in its current form. I had hit a short list of issues that required a complete re-design of the language and type system followed by a ground-up new implementation. Experience with the first implementation suggested that this would take quite a while, and it was simply more than I could afford to take on without external support and funding. Programming language work is not easy to fund. But the third answer may of greatest interest, which is that I no longer believe that type classes "work" in their current form from the standpoint of language design. That's the only important science lesson here.
dev  compsci  programming 
march 2012 by dstelow
RT : Fantastic email on BItC's attempt to build a type-safe systems language Follow-up on Rust & Decac h ...
from twitter
march 2012 by wolverian
Inquiring minds would like to know: what is Jonathan Shapiro up to, after announcing BitC's "demise"? (See: )
bitc  shapiro  coyotos  email 
march 2012 by sajith
Fantastic email on BItC's attempt to build a type-safe systems language Follow-up on Rust & Decac
from twitter_favs
march 2012 by disnet
By now it will be obvious to everyone that I have stopped work on BitC. An
explanation of *why* seems long overdue.
programming 
march 2012 by blevin
Jonathan S. Shapiro shap at eros-os.org Fri Mar 23 15:06:41 PDT 2012 By now it will be obvious to everyone that I have stopped work on BitC. An explanation of *why* seems long overdue. One answer is…
from readability
march 2012 by al3x
Sadness. (But fascinating read.) Retrospective thoughts on the BitC systems programming language: /cc
from twitter_favs
march 2012 by tlockney