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
remove typescript #55655
remove typescript #55655
Conversation
This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise. |
It looks like you've sent a pull request to update some generated declaration files related to the DOM. These files aren't meant to be edited by hand, as they are synchronized with files in the TypeScript-DOM-lib-generator repository. You can read more here. For house-keeping purposes, this pull request will be closed. |
@DarrenBaldwin07 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
I only unlocked this to react to the PR. 😄 |
"Fully recognize that TypeScript offers some people some advantages, but to my eyes, the benefits are evident in this PR. The code not only reads much better, it’s also freed of the type wrangling and gymnastics needed to please the TS compiler.
We write all our client side code at 37signals now in pure JavaScript and the same too with any internal libraries. This is going to bring that in line.
All the love and appreciation to contributors who would prefer TypeScript. This is one of those debates where arguments aren’t likely to move anyone’s fundamental position, so I won’t attempt to do that." -- DHH