Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider moving away from CoffeeScript? #67

Closed
Siilwyn opened this issue Aug 6, 2016 · 4 comments
Closed

Consider moving away from CoffeeScript? #67

Siilwyn opened this issue Aug 6, 2016 · 4 comments

Comments

@Siilwyn
Copy link

Siilwyn commented Aug 6, 2016

Moving forward, before Wire explodes in popularity 😃 I think it's worth thinking about and discussing if CoffeeScript is worth using instead of vanilla JavaScript. CoffeeScript requires a compile step and additional understanding which adds an extra hurdle for people to contribute.

Looking at GitHut JavaScript has roughly 22 times more repositories and is growing faster in popularity while the amount of repositories in CoffeeScript is stagnating.

@bennycode
Copy link
Contributor

CoffeeScript was the programming language which suit us the most when starting to work on Wire for Web. Moving with the times we are evaluating TypeScript and ECMAScript 6 in conjunction with the Babel compiler. What's your take on that, @Siilwyn?

@Siilwyn
Copy link
Author

Siilwyn commented Aug 12, 2016

All three have useful features and it depends on the core contributors preference, vision and experience. The more familiar you are with a language, the easier it is to understand. The size of the project is also an important factor TypeScript's compile-time type checking comes in handy in a large code base and should lead to fewer bugs.

I would say use ES6 because then you're part of the largest development community, rather than a subset. Unless you think a lot of bugs could be prevented by type checking. Another added benefit would be that in the future the build step with Babel can be removed which leads to less complexity.

@bennycode
Copy link
Contributor

At the moment we evaluate both (TypeScript & ES6) because we like the benefit of a typed language (TypeScript) but want to be future proof (ES6).

First steps in TypeScript are made here:

We are also investigating on how to transition from "CoffeeScript" to "ES6" for our webapp. We might follow the approch of @kevinsawicki:

Stay tuned! ✌️

@herrmannplatz
Copy link
Contributor

#891

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants