• 6 Posts
  • 22 Comments
Joined 2 years ago
cake
Cake day: August 29th, 2023

help-circle
  • 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 month ago

    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.









  • Case insensitive FSs aren’t a new thing.

    More precisely, they came up in a time where Unicode was not a thing.

    Yes, you need to attach the locale to the filename. No, I have no idea off the top of my head of how different file systems encode or store that.

    They don’t. None of them.

    Or, if it is, then let’s go back to eight characters from the English alphabet in all caps. 8.3 filenames. Why not? […] Why are spaces, cyrillic, special characters and long names worth doing but case insensitivity isn’t?

    Because you cannot have both.

    It is either “spaces, cyrillic, special characters and long names” or case insensitivity.