SebastianVerified account

@slicknet so the next logical step is to just support listing in core. Once that happens then babel-eslint won't be necessary

@slicknet and just be cumbersome to maintain.

@sebmck what I'm saying is, why not work with us on this problem? It could make ESLint better and free Babel from such concerns.

@slicknet Babel is always going to have to be concerned about it though? Experimental/non-standard syntax is always going to exist.

@sebmck I'd like ESLint to be extensible enough to deal with experimental features and alternate ASTs going forward.

@slicknet Still requires weird integration from the Babel side which is awkward when it can just be in-house and first class.

@slicknet What Im trying to say is no matter how good the Babel-ESLint integrat. is, itll never be better than Babel integrating with itself

@sebmck @slicknet but ESLint solves other problems outside of Babels core purpose. Pluggable rules, great linting documentation.