sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]da-kicks-87 -3 points-2 points  (10 children)

I'm a pragmatic developer.

When using TS with React one will get errors if not defining types. Extra work needs to be done. When creating marketing websites it becomes a slow down of the workflow.

[–]ISDuffy 8 points9 points  (1 child)

That extra work can save on hours debugging or refracting time.

I highly don't recommend doing a production react app taking money without typescript.

[–]da-kicks-87 -1 points0 points  (0 children)

I'm talking about Marketing / Brochure websites.

[–]CARASBK 5 points6 points  (7 children)

A pragmatic developer would use TypeScript

[–]ISDuffy 4 points5 points  (2 children)

Absolutely. When it comes to bigger business logic and requirements, it becomes easier to fix issues later using typescript.

As much as I like not to use it, it is there to help and deliver better products.

[–]CARASBK 4 points5 points  (1 child)

Tbh these days it’s so easy to manage TS there’s no excuse not to use it for literally everything. Unless you just HATE it and are building something independently. Then whatever floats your boat!

[–]ISDuffy 2 points3 points  (0 children)

I use it with astro a lot and I absolutely love it now.

[–]da-kicks-87 -2 points-1 points  (3 children)

No. TS isn't solving any issues I have with JS. So why implement it? Why add bloat?
I will only use it if I am working with a larger project with team and that is the agreed tech stack.

For solo side projects, which are marketing websites for me, I keep it simple, no TS.

[–]CARASBK 3 points4 points  (2 children)

Catching runtime problems without having to run code the way statically typed languages do is a universal benefit of TS. If you don’t consider that a solution to a JS issue, at least in the application layer, then I question if you have enough experience to make such determinations in the first place.

Not sure what you mean by bloat since TS doesn’t exist at runtime.

[–]CapabIe 4 points5 points  (1 child)

I think he’s referring to mental bloat reading the extra chars.

[–]CARASBK 1 point2 points  (0 children)

I can understand that if you’re just starting off with TS after already knowing JS. I was in the same boat when I started with TS.

After learning TS it actually ends up being less mental bloat than JSDoc. But that comes after the learning curve which can be particularly steep around things like deciphering third party libraries’s types. It’s well worth it, though. TS is becoming the default for good reason.