Live data from Hacker News

Viewing profile — j-james

j-james

HN member
Joined
Sat, Nov 30, 2019, 7:27 PM UTC
HN karma
1,132
Public activity
253 items

About j-james

No profile information was provided.

Recent public activity

  1. comment
    Comment #40314834

    I think this is all true. Though with regard to your earlier example, it should be noted that Nim, too, has an extraordinarily powerful compile-time programming system: but it take…

  2. comment
    Comment #40314809

    https://github.com/nim-lang/RFCs/issues/548

  3. comment
    Comment #40270564

    It will not emit warnings saying it did that. The static analysis is not very transparent. (If you can get the right incantation of flags working to do so and it works, let me know…

  4. comment
    Comment #39472973

    That relies upon the benevolence of corporations to much more of an extent than I am comfortable with. 20 years of social media has convinced me that that's a bad idea. And, I thin…

  5. comment
    Comment #39472657

    I cannot see how BlueSky's moderation system can ever work. Decoupling moderation and hosting means there's no onus to do the moderation that they describe: which makes me think it…

  6. comment
    Comment #39087148

    You don't want nimterop, you want futhark ( https://github.com/PMunch/futhark ). The C FFI Nim library lineage goes c2nim --> nimterop --> something i forgot --> futhark.

  7. comment
    Comment #38999888

    Ah, I was referring to disruptek. I don't know why you two hated each other's guts, mostly due to being less active back then indeed. For what it's worth I didn't think the banning…

  8. comment
    Comment #38998824

    Some context: dom96 here was the BDFL-in-2nd-command of Nim for quite some time. There is personal beef between dom96 and some of the primary nimskull contributors, which mostly in…

  9. comment
    Comment #38977871

    Well, they're not classes, they're interfaces, and so you can implement multiple interfaces for multiple types, and so you have to implement them separately from the type declarati…

  10. comment
  11. comment
    Comment #38946668

    I'd be a little interested to hear what you like about C++'s syntax! As a non-C++ programmer, I mostly think of the language as a pile of mistakes that kinda had to happen for othe…

  12. comment
    Comment #38838419

    Nim is particularly C-like. The automatic memory management is optional and exposes destructors, it exposes pointers and is quite usable on embedded systems (see: Futhark, Ratel), …

  13. comment
    Comment #38819215

    Well, it has a runtime. Checking and updating the reference count (more so the latter) is not zero-cost. This runtime is just deterministic. Of course, then do we have the same def…

  14. comment
    Comment #38814045

    Koka is garbage collected. There are several terminology ambiguities in play: the documentation takes "garbage collection" to refer to tracing garbage collection as opposed to runt…

  15. comment
    Comment #38511744

    The downsides of this approach are unfortunately that it makes wrapping certain low-level libraries an absolute pain in the ass (especially anything to do with keyboards). But over…

  16. comment
    Comment #38511725

    Heh, neat to see you've got the Perceus paper there too. That is in fact the other part (the "ARC") of Nim's memory management for those unaware - with the only differences being N…

  17. comment
    Comment #37303204

    Hmm, a strong type system? Is there any overlap between the Wit IDL and other similar projects like crABI?

  18. comment
    Comment #36963585

    Really, I'm quite hopeful for crabi: https://github.com/rust-lang/rust/pull/105586 An ABI for languages with a proper type system seems fantastic. Swift, Rust, Nim, D all share ver…

  19. comment
    Comment #36963156

    > You can also not really have productive and well-fitting errors-as-values in a language that emphasizes UFCS Eh, https://github.com/arnetheduck/nim-results and associated syntax …

  20. comment
    Comment #36962248

    > It's not so much a competitor (in performance or clarity) to Odin or Zig as it is a competitor to Go or something That seems accurate. Dealing with raw pointers as one does in Od…

  21. comment
    Comment #36961450

    Ones that have not been mentioned so far: - npeg lets you write PEGs inline in almost normal notation: https://github.com/zevv/npeg - owlkettle is a declarative macro-oriented libr…

  22. comment
    Comment #36961160

    I know, I know! I do very much like the "type wrapper" approach more than the "object variant" approach. Perhaps in the future we'll simply have both and have no reason to debate ;…

  23. comment
    Comment #36960416

    I have a shortlist of pain points: - Tooling is not great. The language server has a tendency to silently crash on occasion, and it's no rust-analyzer to begin with. A tooling rewr…

  24. comment
    Comment #36960196

    Yes, an experiment was run a while back, incorporating community-maintained code in a "fusion" repo shipped with the compiler by default. It didn't work very well. Discoverability …

  25. comment
    Comment #36159904

    Right, but I'm curious about the calling-Zig-from-C interop, not the other way around.