Remove TypeScript, for now #178
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've become increasingly frustrated with the degree to which TypeScript impedes development velocity in this repo. In my own personal experience it has had a significant net negative impact on productivity — I am spending much more time appeasing the compiler than actually building stuff.
The mental effort we are spending futzing around with TypeScript (which doesn't just mean adding types, but dealing with tsconfig files and addressing the quirks of things like rpt2, etc) would be much more profitably spent writing tests, in my opinion.
I definitely believe in the utility of types when it comes to ensuring a project's continued long term maintainability. But the exploratory phase, when things are changing frequently and designs are speculative and need rapid iteration, is not the time to worry about types in my view — it has the effect of strangling the codebase before it has a chance to take shape.
I realise this proposal will be unpopular with some people! Some context: SvelteKit is being used for a major project at the NYT which will be seen by millions of people. We are trying to get it published soon, which means I'm trying to get it to a state of production-readiness, if only in the case where app developer === framework developer. Right now, I'm being bombarded with status update requests, and 'I'm debugging an inscrutable error from rpt2' is not a satisfying response.
Let's lay off the type stuff for now and focus on functionality.