I’m also on Mastodon as https://hachyderm.io/@BoydStephenSmithJr .

  • 13 Posts
  • 1.43K Comments
Joined 3 年前
cake
Cake day: 2023年10月2日

help-circle
  • I don’t think objects without a subjective experience need to give or are capable of giving consent. I don’t think anyone needs to ask their fleshlight for consent, e.g.

    If it were a living deer, then it would need to give consent but be unable to. (I think it’s reasonable to say any supposed communications from the deer is less trustworthy than “Facilitated Communication”, and not sufficient consent.)




  • There’s a cap on how much you (and your employer) pay per SSN / year. So, for particularly high wages or salaries, the percentage goes down, for every dollar made above the cap.

    Also, things like stock( option)s often made up a significant portion of compensation for high earners and those aren’t subject to SSI tax at all, IIRC.









  • I want a language with an internal/core calculus of GRTT with a specific grading that I believe will provide both optimal evaluation and prompt resource release. You aren’t going to get that by building on top of another language.

    Of course you could do it as a library for another language, but the few values you could lift/lower and the necessary analysis do to bidirectional type inference/checking mean that you are writing a compile phase whether you call it that or not. In theory, you might save on the tokenizer/parser, but those are trivial to write. You might be able to reuse parts of the API/ABI, which could be an advantage if the underlying language has a good, stable one that can reflect your linking/calling/passing restrictions; but that’s not likely.







  • If you read the literature, particularly “Types and Programming Language”, you’ll find that “dynamic typing” isn’t even considered typing. If you can have a type error at runtime you’ve defeated the reason to add a type system: to reduce runtime errors. The hope is that “well-typed programs don’t go wrong” tho there are some limits to what any type system can do (e.g. Rice’s Theorem).

    That said. Static v. Dynamic is much more precise than Strong v. Weak and should be preferred.

    Implicit v. Manifest is less useful just because it’s a broad spectrum, basically inculcating how much type inference is done and “how much” generally depends a lot the input program(s). Haskell does whole-program inference, tho GHC (the only Haskell compiler) has a number of syntactic forms that can’t be inferred. Scala only does local inference. C doesn’t infer types, though is gets close with how it treats functions with no-argument in the prototype and varargs stuff. C++ uses auto for some type inference, which is still somewhat manifest, but also mostly implicit.

    I think weak typing is a good name for when there are invisible coercions, but that doesn’t actually have much to do with proper types.

    Anyway, great comment, If more people would use static/dynamic and explicit/implicit instead of strong/weak, there’d be less miscommunication.