ckaygusu

I'm not disagreeing on the principle. As the sovereign of the land, of course you're going to prioritize yourself. The prioritization you're talking about does not come in as giving an advantage to the domestic worker, it comes in the form of hostile treatment of people who are here on work visas, and has been living here quite a while.

Why not actually treat them with dignity instead, and give them a legit chance to settle?

Faster you do something, more you rely on your instincts, and instincts alone do not further your game -- or anything you strive to be good at really -- you need to be mindfully thinking it through.

It might be beneficial to spice things up, but this is in general not a good advice.

It's really not a great argument considering that's all he had.

In my over 12 years of experience using git, "how many things git checkout do" is still my go-to example to complain about it.

You almost took words right out of my mouth and wrote it here. Except the part I'm not a business owner, though nevertheless I would not want to be teammates with a person of this attitude.

> Can’t this be accomplished with JavaScript? Assuming your interested in clean code and best practices.

There's nothing that prevents you from swimming against a stream, but we know swimming with the stream is faster. Same thing here. It's not impossible in javascript, but typescript makes code maintenance much more easier.

> Can’t you also write unit tests in JavaScript?

"Being more than sum of its parts" and all that.

> This is a false sense of security. “Compiling” without errors just tells me I did not do something dumb like assign a string to an int. Is this really the main issue devs have? From what I have seen no… Devs usually need to chase down and understand the code regardless of type checking.

Typescript does not solve all the software engineering problems. It makes common problems and annoyances much more easy to handle.

Doing Typescript for a living.

2 out of 3 of the items you wrote down has to deal with old baggage, so whatever form of language you are dealing with those, you aren't going to have a good time. You can either bite the bullet and write the type definitions yourself, or just disable the type system altogether, which, if you can isolate it to a certain area in the code, you are fine.

If you are writing code that some other person is going to read and/or you are interested in having it behave reliably in the long run, I think a static type system is a must. Coupled with good unit tests, if the type checker does not complain, you can be very confident the code you wrote is working and will work for a vast majority of the cases.

Typescript is especially great because, unlike some other statically typed languages, you can choose not do use it in some cases (e.g., setting up mocks for tests, writing a small script to see how stuff works, etc), which is liberating.

I went from Python to Typescript. Python is still my go-to language for random tasks, though unless I have a good reason to do otherwise, I don't want to deal with a production codebase that does not do static type analysis anymore. I don't know others, but I just get more done in less amount of time in this way.

Yup, this is exactly the problem with modern politics. Take the absolute worst of the other side and project it to all of them. You like Republicans? You can't be anything other than a neo nazi racist white supremacist extremist. You leaning left? Then you have to be a communist shill who wants to tax every remotely financially successful person to death and take all liberties away from everyone ever. It's really tiring.

Nope, we were talking about visas and legal status, and about getting kicked out if lack of visa. But whatever, I think you get the point.

Oh man.

I am going through F1->H1B process. I do not have an H1B visa, and I have a document that tells me I am allowed to stay in the country in the H1B status between a time period, and you are telling me I am in trouble because I do not have a visa. Ok, I suppose.