Skip to content
This repository has been archived by the owner on Mar 8, 2021. It is now read-only.

Random List of Ideal Ecosystem Tooling #13

Open
brekk opened this issue Nov 7, 2020 · 2 comments
Open

Random List of Ideal Ecosystem Tooling #13

brekk opened this issue Nov 7, 2020 · 2 comments
Labels
📘 proposal An idea for a thing

Comments

@brekk
Copy link
Contributor

brekk commented Nov 7, 2020

A non-exhaustive-list-of-things-that-make-a-language-nice-to-use

(NELOFTMALNTU)

  • auto-format + linting - prior art: prettier
  • auto-documentation - potential integration jsdoc
  • testing framework - prior art: tape (keep-it-simple-stupid) or jest (complex-yet-subtly-tricky)
  • CLI string-formatting - avoid left-pad / colors / chalk headaches
  • CLI tool building - prior art: yargs-parser
  • build tool - prior art: rollup
  • REPL - prior art: snang / ipython
  • Solid and consistent standard library - prior art: ramda
@aboeglin
Copy link
Contributor

aboeglin commented Nov 8, 2020

I think we should roughly try to sort them by importance and effort and then see where we want to start spending our efforts. I think a standard library is still the first goal. As from there we can build all others within Madlib.

@aboeglin
Copy link
Contributor

aboeglin commented Nov 8, 2020

Formatting should be rather simple as we have an AST already. So instead of targeting JS, we just target Madlib. That's probably one of the only tools, appart maybe from the REPL, that I would write based on the code of the compiler.

@brekk brekk added 📘 proposal An idea for a thing and removed enhancement labels Dec 9, 2020
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
📘 proposal An idea for a thing
Projects
None yet
Development

No branches or pull requests

2 participants