SVGs as Elm Code

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • Elm

    Compiler for Elm, a functional language for reliable webapps.

  • mint-lang

    :leaves: A refreshing programming language for the front-end web

  • Nope, because anyone forking would have to come up with new name and run their own community.

    If you are building an SPA then there is always Mint[1] (it's an Elm like language).

      [1]: https://github.com/mint-lang/mint

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • specifications

    Specifications related to Jevko. (by jevko)

  • Notice that here I used a convention where names which end with "=" become XML attributes, whereas names which don't become children.

    I have used the same convention here (except I don't bother with transforming names with spaces into camelCase): https://github.com/jevko/specifications/blob/master/easyjevk... to generate this HTML file: https://htmlpreview.github.io/?https://github.com/jevko/spec...

    Now I intend to write specifications that codify conventions like this into different formats based on this fundamental syntax of square brackets.

    It can be useful for all kinds of things. Its advantage is extreme simplicity and flexibility.

    BTW, for clarity I have to say that the format that I used here: https://news.ycombinator.com/item?id=32995047 does a bit more transformations -- it actually sometimes treats whitespace as a separator (e.g. in `svg width[391]` space is a separator). That allows for extreme conciseness, but is not necessary and introduces complexity.

  • spec

  • Notice that here I used a convention where names which end with "=" become XML attributes, whereas names which don't become children.

    I have used the same convention here (except I don't bother with transforming names with spaces into camelCase): https://github.com/jevko/specifications/blob/master/easyjevk... to generate this HTML file: https://htmlpreview.github.io/?https://github.com/jevko/spec...

    Now I intend to write specifications that codify conventions like this into different formats based on this fundamental syntax of square brackets.

    It can be useful for all kinds of things. Its advantage is extreme simplicity and flexibility.

    BTW, for clarity I have to say that the format that I used here: https://news.ycombinator.com/item?id=32995047 does a bit more transformations -- it actually sometimes treats whitespace as a separator (e.g. in `svg width[391]` space is a separator). That allows for extreme conciseness, but is not necessary and introduces complexity.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts