Project status: life support

[za-creature]

coffeescript was a language ahead of its time, and that comes with a downside. After a cascade of failures, I don't really have any skin in it anymore. I will continue maintaining this project for as long as people are using it, but for now I've made my peace with js

if anyone wants to take over, I'm happy to hand over the keys: for the foreseeable future, I can only moderate

[danielbayley]

@za-creature I'll take the keys if you like? However, have you seen @aminland /eslint-plugin-coffee? I'm wondering if it makes this project obsolete… can ESLint replace all the features of coffeescope with this plugin… what are your thoughts?

[za-creature]

The eslint plugin might exhibit some issues with the coffeescript-to-javascript translation. My main concern is the everything-is-an-expression syntax in coffeescript which might produce unexpected results depending on how the translation is done.

If you want to pick it up, I'm happy to send users your way. However, while I personally trust you, I can't make that decision for everyone that uses this project. If you choose to fork and continue development, I will release 0.6.0 which will fail the npm build with a link to coffeescope3 (or whatever you would like to call it).

Regardless of your decision, I would like to thank you for supporting this project. I'm currently completely out of the coffeescript scene, mostly doing python backend these days and if I ever do get back to frontend, I'll probably be using vanilla javascript. I don't really like it, but I have a 'it's good enough' opinion of it, especially with native support for async/await which sort-of makes a lot of the really clever stuff from coffeescript no longer that useful.

Let me know how you want to proceed