• 6 Posts
  • 26 Comments
Joined 2 年前
cake
Cake day: 2023年8月29日

help-circle



  • “apparently it’s a better safer C++, but I’m not going to switch because I can technically do all that stuff in C++”

    The main difference between C++ and D was that (for most of the time in the past) D required garbage collector.

    So, D was a language with similar Algol-style syntax targeting a completely different niche from C++.

    Trying to correct your quote, it should read something like “I’m not going to switch because I can’t technically do all that stuff in D that I’m doing in C++” for it to make any sense.


  • I think the article suffers a bit from not being up to date in regard to the work Java has done with virtual threads.

    There quite a few assumptions being made in the article that would not have been questioned a few years ago, but now these assumptions feel quite unfounded and all the conclusions based on them stand on shaky ground.



  • Some functions also don’t have any parentheses, like field access or infix operators.

    You call things the way they were defined. Problem solved.

    I’m kinda confused, because this is the second time now where your attempt at making a counter argument is actively supporting my point. Is this intentional at your part?

    We could follow this line of thinking further …

    No we don’t. If your point relies on Turing-tarpitting the whole discussion … then you have no point.














  • socOPtoProgramming LanguagesUnified Condition Expressions
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 个月前

    Sure, there are some worse/more limited predecessors – my design was partially motivated by a desire to improve upon these.

    For instance, that ML-derivative you are using for your examples

    • very likely still has if then else in the language, thus making it not unified
    • desperately tries to emulate functionality with guards that simply comes out of the box with my approach
    • relies on the ultimate hack of “match on unit”, because match is very limited in which coding patterns it can express

    Also, none of the examples are “more clear” or “have less magic”:
    Maybe they are more “familiar” to you personally, but that’s about it.

    Too me they just look clunky, full of accidental complexity and trying to work around a poor/limited language design.