> my gut is screaming no

seems like you already made up your mind, so why bother?

TypeScript is helpful (or at least meant to be) for teams as it aims to block the cleverness of its individual contributors. Especially people only familiar with dynamic type systems are rather fighting a static type checker at first and "it's not helping them". A "strong" type checker should enforce everyone to write stuff in a simpler form and that gets in the way of productivity for some people.

If you can maintain your mindset and write your code in a simple form that could easily satisfy a type checker (coming from rust), then why bother with additional tooling if it won't provide more value to you? Or to phrase it differently: if you can maintain a strong mindset with confidence, bringing in additional tooling for that project later on, when it will be become plausible, won't be that hard. But if you doubt your mindset, it might be a helpful choice to let a type checker look over your shoulder from the beginning.

I recently started working on a project that added TS after the project was very mature. The biggest problem is the project was never intended to have types so they feel very shoehorned in and, imo, cause far more problems than they are solving. I think in this specific case the project simply should not have been updated with types.

I have worked with JS a lot and have only used TS in this one instance. I would be interested in working on a project that included TS from the beginning to see a better representation of TS.

Also, fwiw, we have solved many of the same problems with linting and automated tests. But this requires education and maintenance; it would be interesting to compare this effort with a TS project.

> strapping on types to eternity.

You can write TS that way. Most people who write a lot of typescript don't though. Instead of describing JavaScript's inherent limitlessness, you can deliberately reduce the size of the infinity within any given context.

Your app just knows what values it's going to get out of a function. Your IDE happily suggests the exact right set of property names to make a function work right.

You're not really working alone because you're going to be integrating with external libraries and APIs. Many of them include typescript support because it takes the guesswork out of working with them.

I don't have any problems getting functions to work or reading the docs to use APIs, so typescript isn't solving anything for me there.

I wouldn't mind using a very minimal amount of typescript, basically JS with proper Enums, typed function parameters, and return types, but there seems to be a ton of hurdles to jump just to get started with it.

If I was working for a company, I'd be happy to spend 6 months of their time learning how to use it properly, but I don't think I can justify it for myself right now, I don't have the time to be fighting with a code editor for weeks/months.

Types are useful, even as a solo developer. My memory just isn't good enough. It's nice to have a compiler tell me: "Yeah, there on line 974? You're doing something stupid there; go fix it."

Note that I said types are useful. I have no experience with TypeScript.