developer-mike

5 ms·

1. 1.▲
   (Dart 2) Future<void> vs. Future<Null>, what's the difference?(medium.com)

   1 points by developer-mike 8y ago|0 comments
2. 2.▲
   by developer-mike 8y ago

   This is true in the same sense that "a JIT" should really be "a JIT compiler." Used as "a JIT," the term is given new meaning (to refer to a compiler implicitly). And used as "JIT language," its givin
3. 3.▲
   by developer-mike 8y ago

   The language is, however, designed to be JITted. Languages are not designed in isolation.
4. 4.▲
   What I Learned Making My Own JIT Language(mikedrivendevelopment.com)

   291 points by developer-mike 8y ago|118 comments
5. 5.▲
   Else If Is Not Special (Except in Python)(mikedrivendevelopment.com)

   2 points by developer-mike 10y ago|0 comments
6. 6.▲
   Review of Wake: a language aimed at testability, expressiveness, and typesafety(yobriefca.se)

   2 points by developer-mike 12y ago|0 comments
7. 7.▲
   by developer-mike 12y ago

   Thanks! These are great resources for some cool programs and I will be sure to submit!
8. 8.▲
   by developer-mike 12y ago

   I'd absolutely be interested in that type of engagement, papers, and presentations. I haven't written a technical paper before, but tried to make one on the testability here: https://docs.google.com/document/d
9. 9.▲
   by developer-mike 12y ago

   Great question! I wanted to compile to js with a better interface than emscripten.
10. 10.▲
    by developer-mike 12y ago

    I can imagine so; But as a counterpoint, isn't it worse with forced implicit returns, where you never have a choice but to return something, and you have to scan the code carefully to see if it was required? Maybe I'll add a &#x27
11. 11.▲
    by developer-mike 12y ago

    This is covered in the FAQ. Partly, I allow it because there are no parsing ambiguities with it, so why not. But moreover, depending on type name & variable names, intelligently beginning or ending with an alias can lead to extremely fl
12. 12.▲
    by developer-mike 12y ago

    Thanks! Great comment, I'd planned on adding implicit returns, and may copy rust on that one!
13. 13.▲
    by developer-mike 12y ago

    Correct, there is runtime typesafety in javascript. However, type-safety is a spectrum; truthiness and falsiness for instance is not very typesafe. I will revise this to be clearer (your nitpick is valid) but I think the heart of the issue
14. 14.▲
    by developer-mike 12y ago

    Thanks! I think with programming languages its important that it looks just strange enough. Luckily I have a few simple ideas that drive most of those unique syntaxes, hopefully making the uniqueness both justifiable and attention-grabbing.
15. 15.▲
    by developer-mike 12y ago

    Good memory! Yeah, I had posted that to Reddit, where it didn't do too well, but someone posted it here where (for some reason!) it did much better. Figured in addition to the story of creating Wake, I'd post the home page so peop
16. 16.▲
    by developer-mike 12y ago

    Hey! Creator of Wake here. This looks like a nice language! Lots of syntactic niceties, and it looks extremely feature complete. Nice work! I'm not surprised you learned a lot given how many features it supports!
17. 17.▲
    The Wake Programming Language(wakelang.com)

    81 points by developer-mike 12y ago|57 comments