You aren’t though. In most languages that use the latter declaration you would prefix the declaration with final or const or the like to specify it won’t be updated.
But if it were rust, this meme would not make sense, since you would just type let a and type inference would do its thing. Which is much more ergonomic.
Probably would still use TypeScript, because I use that for work. 🤷♂️ Rust just seems like… a lot. Regarding Rust, I’ve seen a lot of praises and a not so insignificant amount of complaints that make me very hesitant to take the plunge. Can’t remember off the top of my head what it was, specifically, but it was enough for me to write it off, that much I remember.
People really overstate it, it’s not that hard. It has a reputation of being difficult because people use it for difficult, low-level tasks, OS stuff, parsers, cryptography, highly optimised serialisation, but those things would be hard in any language. For a newcomer it’s, IMO, way easier than say C++, because it doesn’t have a mindbogglingly huge std lib with decades of changing best practices to try to figure out. To do simpler things in it is really pretty straightforward, especially if you’re already comfortable with a robust type system.
This contradicts what I’ve heard others say about it. I have a feeling it is quite subjective, and this might just be an anecdotal recommendation because you have an easy time with it. Maybe I will too! But maybe I won’t.
Either way, one part of me really wants to try it, but one part has very little time in life. 🥲
Also comparing it to C++ might not be the flex we think it is. 😅
Well sure, I guess you’re right, it’s definitely a bit subjective and some people have an easier time with some languages and ways of thinking than others for sure. And I didn’t really mean to say that it was totally super easy, but… no kind of programming is really super easy. It is quite different and that in itself has a learning curve.
My recommendation is for sure anecdotal, but I think the point about it seeming more difficult than it really is because people often use it for difficult stuff is actually true.
You’re encoding more information in the typescript one. You’re saying it’s a string that will get updated.
Yeah, it’s explicitly distinct from
const a: Stringwhich says it won’t change, andvar a: String, which means this is legacy code that needs fixing.If there’s only two options you only need one keyword
True, but var and let are not same in js, so there is three.
if(true) {var a = "dumdum"}console.log(a)Is valid and functioning javascript. With let it is not.
Ah, but this is JS, so there are three options! And they all function entirely differently. And your assumptions don’t apply, either. :D
You aren’t though. In most languages that use the latter declaration you would prefix the declaration with final or const or the like to specify it won’t be updated.
deleted by creator
That looks like rust ngl
It’s also valid rust syntax.
But if it were rust, this meme would not make sense, since you would just type
let aand type inference would do its thing. Which is much more ergonomic.let a = String::from(“Hello, world!”).into()I’ll see myself out.
At least be fair and cut out the
.into()And bow to the compiler’s whims? I think not!
This shouldn’t compile, because .into needs the type from the left side and let needs the type from the right side.
If type constraints later in the function let the compiler infer the type, this syntax totally works.
Like if the variable is then used in a function that only takes one type? Huh.
Type inference is a pretty big thing in TypeScript as well though. In fact it’s probably the biggest thing about it, IMO.
I don’t know typescript. But if that’s the case, this meme doesn’t make much sense.
Who writes the types of variables in a language with type inference unless forced by the compiler?
Maybe it’s a language without type interference?
Either way, it sometimes makes sense in TypeScript to help the type system out a little bit.
let array: string[] = [];In this situation, the type system can’t infer that the empty array should be a
stringarray, because there are no items to go by.I was thinking the same thing. who would write typescript if they could just do Rust?
I would because I know TypeScript and I don’t know Rust.
ok but then you can’t do Rust, so this does not apply.
but if you did… !
Probably would still use TypeScript, because I use that for work. 🤷♂️ Rust just seems like… a lot. Regarding Rust, I’ve seen a lot of praises and a not so insignificant amount of complaints that make me very hesitant to take the plunge. Can’t remember off the top of my head what it was, specifically, but it was enough for me to write it off, that much I remember.
People really overstate it, it’s not that hard. It has a reputation of being difficult because people use it for difficult, low-level tasks, OS stuff, parsers, cryptography, highly optimised serialisation, but those things would be hard in any language. For a newcomer it’s, IMO, way easier than say C++, because it doesn’t have a mindbogglingly huge std lib with decades of changing best practices to try to figure out. To do simpler things in it is really pretty straightforward, especially if you’re already comfortable with a robust type system.
This contradicts what I’ve heard others say about it. I have a feeling it is quite subjective, and this might just be an anecdotal recommendation because you have an easy time with it. Maybe I will too! But maybe I won’t.
Either way, one part of me really wants to try it, but one part has very little time in life. 🥲
Also comparing it to C++ might not be the flex we think it is. 😅
Well sure, I guess you’re right, it’s definitely a bit subjective and some people have an easier time with some languages and ways of thinking than others for sure. And I didn’t really mean to say that it was totally super easy, but… no kind of programming is really super easy. It is quite different and that in itself has a learning curve.
My recommendation is for sure anecdotal, but I think the point about it seeming more difficult than it really is because people often use it for difficult stuff is actually true.
C# has const string a = “Hello, World”;
var in js is legacy, and default should be let, but changing that would break everything
Meanwhile if it’s rust it’s the opposite. (Variables that can change must specify that they are mutable)