3 ms·

Interesting list, but I don't quite get the idea. Is it implying JavaScript shouldn't be used to work on JavaScript, just for the sake of it? To me it almost so

• capableweb 5y ago
  Nope, the list is implying that "here is a resource of tooling built for JS but NOT made in JS", not sure where you get the other implication from. Just as "awesome-lists" about security is not implying that you should hack other people and so on. I think the motivation is to show that just because you want to write a tool for the JS ecosystem, you don't have to use JS if you don't want to. And I like the idea, I think more languages and their communities should cross-pollinate, we can all learn a lot from each other, even though some like types and some do not.
  • numlock86 5y ago
    > Nope, the list is implying that "here is a resource of tooling built for JS but NOT made in JS", [...] So the list is indeed arbitrary. > I think the motivation is to show that just because you want to write a tool for the JS ecosystem, you don't have to use JS if you don't want to. No one ever said you had to.
• devit 5y ago
  They are much faster and memory-efficient than the tools written in JavaScript. Part of it is language (e.g. obviously Rust is much better than JavaScript for algorithmic code) and part the fact that someone using another language is likely motivated to do a good job.
  • numlock86 5y ago
    > They are much faster and memory-efficient than the tools written in JavaScript. Can you show some benchmarks/profiling results?