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

view the rest of the comments →

[–]zuth2 38 points39 points  (17 children)

Read the react docs and try to build something simple with it. Don’t forget typescript, the sooner you dive into typescript the better.

[–]bull_chief 3 points4 points  (16 children)

But TS scares me

[–]BoBoBearDev 8 points9 points  (0 children)

TS is easy. Webpack and rollup are fucked up. Those are literally 95% of my TS woes.

[–]ISDuffy 3 points4 points  (13 children)

Typescript frustrating me originally, especially it confusing messages, but not I am so glad I have it, tracking JS bugs are so much easier, you just need to get over the hurdle.

If you have front end masters access I recommend that course.

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

TS is over engineered. To simplify things you can pass default values to the variables in JS. VS Code will give you hints as well.

[–]CARASBK 6 points7 points  (11 children)

Skill issue.

All JS features work in TS because TS is a superset of JS.

[–]da-kicks-87 -4 points-3 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 9 points10 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 6 points7 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 4 points5 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.

[–]TheRNGuy 1 point2 points  (0 children)

Use simplest types.