Closed mayakraft closed 6 months ago
Personally, I think ES6 Javascript (with JSDoc style comments) over Typescript for a few reasons:
Rich Harris took the words out of my mouth recently. link
Related to #25 which we should definitely do one way or another.
Personally I'd rather go in the other direction and port to Civet. This would be an easier transition (as it's mostly CoffeeScript compatible), and because it's largely TypeScript compatible (most shorthand is optional), maybe it would be better for others contributing? (Not sure - it still might be intimidating.)
That's cool. in that case, Civet might be the best solution concerning types and ease of translation. Not sure I would bet on it if the aim is to increase community contributions. In that case I might still push for JS/TS as the safer bet. But, again, whatever people think! happy to hear more thoughts.
If the motivation is to invite more contribution, I will certainly recommend TypeScript over alternatives. TypeScript is the de facto standard of JS development, while Civet is, to be honest, almost never discussed within the JS community, despite the hard work by @edemaine. Some numbers to support my point: https://npmtrends.com/@danielx/civet-vs-coffeescript-vs-typescript
I notice this happened on another thread. thanks for the help @Mokshit06 !
Just wanted to throw this out there to gauge a response:
Can we convert the
src/
folder from coffee script into ES6 Javascript or Typescript?This would be for the sole purpose of getting more code contributions from the community. If it resulted in no increase in contribution activity I would feel like I wasted everyone's time. Can we leave this issue open for a while, and if anyone has feelings about this would you like to leave a response?
1,300-1,700 lines of coffee script code, no tests to port.