Recommend me one and try to list the advantages of each one

You've listed the only two, and one is just transpiled to the other. JS is essentially the only game in town for front-end web. You'll need to know it no matter what else you use.

Types are extremely helpful and TS is a fine language in itself but the cracks show quickly IMO. On a greenfield project I'd rather have it than not, but I prefer my team use it minimally. IMO/E people try to do/check/prevent/enforce FAR too much with the type system, and burn time doing nothing useful. I've seen plenty of people online and in person tie themselves in knots trying to do pointless bits of metaprogramming to get the thing to do type gen or throw errors if a future dev writes certain code. It's particularly painful to introduce to large brownfield projects IME (half a dozen experiences over the last decade) that do bits of type juggling etc. I've vowed never to add it to an existing project again, as the reward is just worth the effort and by the time you realise you'll be left with a ton of casts and any s you once thought temporary. It also feels clunky when you're pulling a load of typedefs (which are often just superficial interface defs) from a separate package and trusting that they're good. Multiple types are just a mistake IMO. I never use them and I don't think they should exist. number | string or an object/interface where each prop is atype | null | undefined ... yeah, thanks for that. If your datastore is also like that then god help you all.

Also, I've heard big companies are ditching TS

Some are, many aren't. It doesn't really affect anything for you. If you know JS very well then learning to use TS productively is a few hours reading and playing around. It's not a big investment.