-
Notifications
You must be signed in to change notification settings - Fork 170
CoffeeScript v2 #595
Comments
Hey. Sorry for the late reply. I have been taking a break from working on stuff on github since the beginning of the year. I have always been accepting bugfixes, I just haven't really received many recently. I took a look at v2 and what I thought would maybe take an hour has taken up my entire night to fix all the little problems v2 has. Personally for me at the moment I probably won't have time to add new features once version 2 comes around. I will push my fixes for cs2 (I found an issue with cs2 while testing) but I think if people want further changes someone is probably going to have to step in and help out. |
Hi! No worries, thanks for the reply! My case in point was that CoffeeScript is far from dead and CoffeeLint is a beautiful project which many people use and will continue to use after CS v2 is out. Please don't kill it. :) Just wanted to point that out. You could put it in the README that you're looking for help/contributors/maintainers/etc. Hopefully someday someone will come along. Thanks for the time you're spending on CoffeeLint! |
@swang - I tried using your branch
How do I fix this? |
@boris-petrov I'm using a local clone and |
CoffeeScript 2 is coming! I'm reading that this project here is almost abandoned. I completely do not agree that CoffeeScript is dead and should be replaced by ES2015. CS is still a much more beautiful language, is easier to write and I personally have no intention of switching over to JS any time soon. I'm absolutely sure that I'm not alone in my thinking.
Are we going to see new releases for CoffeeLint (e.g. working with the new things in CoffeeScript 2, bugfixes, etc) or is this project practically dead?
The text was updated successfully, but these errors were encountered: