Live data from Hacker News

Viewing profile — simonrepp

simonrepp

HN member
Joined
Sat, Aug 04, 2018, 1:15 PM UTC
HN karma
57
Public activity
38 items

About simonrepp

No profile information was provided.

Recent public activity

  1. story
  2. comment
    Comment #20735552

    You are correct! The thinking behind this is that for the majority of file-based configuration and content usecases the expected types are fixed and known beforehand already - ergo…

  3. comment
    Comment #20732999

    tl;dr: Another alternative to YAML (among many great others), this one designed and developed by me: https://eno-lang.org/ I've been doing a lot of research and development on lang…

  4. comment
    Comment #18628283

    Very cool! If it succeeds and you'd like to publish any part of it at some point, I'll gladly pick it up for a collection of case studies on eno-lang.org, just let me know then. Me…

  5. comment
    Comment #18620447

    Awesome, very happy to see this. Now I'm curious - are you putting this to use somewhere already? Or is it for the time being "just" an experiment for the joy of implementing in it…

  6. comment
    Comment #18606709

    The design principle for types in eno is that the language itself has no notion of types, there are only plain textual representations. Meaning, types are never inferred from a doc…

  7. story
    Show HN: Enophp – PHP library for the eno notation language

    The eno notation language[1] now also has an official PHP library: https://eno-lang.org/php/ It features the same API and featureset as the JavaScript / Python / Ruby libraries, an…

  8. comment
    Comment #17787730

    On npm that's in fact already covered, scrutinize the list https://www.npmjs.com/search?q=eno :)

  9. comment
    Comment #17787640

    That road (C or Rust parsing core through bindings) will likely be taken, but for the initial development and jump-starting the ecosystem it was important for me to start with impl…

  10. comment
    Comment #17787575

    Thanks for that feedback! I'll see what I can do to communicate the API type concept better, I'm generally struggling to pack all the bandwidth of things into the little available …

  11. comment
    Comment #17787541

    Associated fifties right away too, although not that colorful :)

  12. comment
    Comment #17787534

    Thanks for the encouragement! I like the philosophy of friends! (even though I too don't need quite the power of it (yet). ;))

  13. comment
    Comment #17784361

    I appreciate the input :) but the thing is that the typing concept in eno as it is now is essentially what makes eno eno. Every application that uses eno decides for itself what ty…

  14. comment
    Comment #17783227

    Well spotted, good question! It's also been asked in another thread on HN, I'm quoting myself here: "eno has neither indentation nor closing tags of any sort, that means if you use…

  15. comment
    Comment #17783173

    Yes through sections ! See https://eno-lang.org/introduction/ . You can nest as deeply as you want and multiple sections on the same level automatically turn into a list of section…

  16. comment
    Comment #17783131

    ruamel.yaml in python does that to a certain degree from what I've read, you might want to check it out if yaml is ok for your usecase! ( https://yaml.readthedocs.io/en/latest/ ) I…

  17. comment
    Comment #17783074

    Sure! Cultural research = notoriously underfunded, so although they have and rely on a relational database that holds their data (previously Postgres) the cost and effort associate…

  18. comment
    Comment #17783005

    Hey, first off thanks! :) 1a) because faster was only one aspect, it also needed to be easier, even more pressingly that in fact. 1b) see answer by other poster (thanks!) 2) Not wh…

  19. comment
    Comment #17782953

    Regarding types check out https://eno-lang.org/javascript/#loaders - basically eno allows arbitrary types on the language level and provides loaders for all primitive types and cur…

  20. comment
    Comment #17781986

    One of the design conderations was and is that the format is very strict (and that way predictable), but at the same time as helpful as possible in identifying, communicating and r…

  21. comment
    Comment #17781938

    From what I saw, I think for at least a few parsers this might be the case because they are built on generated parser code, and it's just easy to run into unfavorable bits and piec…

  22. comment
    Comment #17781264

    Conveying what types to enter is not an eno-specific problem, as a user without schema or code access you don't know which types a blank YAML/TOML file expects either! Asides the a…

  23. comment
    Comment #17781195

    You're right, not yet ! Jump-starting the whole ecosystem was a major time investment for me but now that there is public exposure providing a formal spec has a higher priority bec…

  24. comment
    Comment #17781140

    Syntax vs Semantics is distinguished by ParseError vs ValidationError in the eno libraries - I'll keep the importance of distinguishing them in mind for the schema development too …

  25. comment
    Comment #17781064

    1) Yes! (You can directly dump it to a language-native structure with the raw() method too, this is not 1:1 YAML/TOML style generic deserialization though as there are no fixed typ…