This is a very junior take and not a good look for the company you're advertising here. Statements like "Go is like metal to plastic TS" make it seem like you wouldn't actually be able to explain the differences between the two (and, ironically, the strength and quality of Go's type safety are debatable. You could argue TypeScript has better type safety than Go -- but then again, what kind of developer would pick one over the other solely because of this specific criterion?)
You also seem to have missed that TypeScript is entirely optional when working with Deno -- it just comes with tsc built-in in case you want to work with it, saving you from setting up your own transpilation pipeline.
Why are people even arguing Node vs. Deno? They're two different things, and Node will not go away over night because of Deno.
This. It's the typical case where someone hates something just because he doesn't understand it. I lost it when the post compared type safety with types in docs. It just shows a complete lack of theoretical knowledge.
// , “It is not so important to be serious as it is to be serious about the important things. The monkey wears an expression of seriousness... but the monkey is serious because he itches."(No/No)
// , “It is not so important to be serious as it is to be serious about the important things. The monkey wears an expression of seriousness... but the monkey is serious because he itches."(No/No)
So, you're saying there's a company named "4r7d3c0"?
Ohhhh, I get it. The 4 is an "A" and the "7" is a "t", 3 is an "e" etc.
Yeah I guess you've kind of got a point there. Not sure if I'd call that "advertising," but there's definitely not the usual effort to separate person from org.
I agree.
If you work with technologies, the phrase "I'll never use put_technology_name_here_" shows shortsightedness... changes are always going to happen, whether you want it or not
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a very junior take and not a good look for the company you're advertising here. Statements like "Go is like metal to plastic TS" make it seem like you wouldn't actually be able to explain the differences between the two (and, ironically, the strength and quality of Go's type safety are debatable. You could argue TypeScript has better type safety than Go -- but then again, what kind of developer would pick one over the other solely because of this specific criterion?)
You also seem to have missed that TypeScript is entirely optional when working with Deno -- it just comes with
tscbuilt-in in case you want to work with it, saving you from setting up your own transpilation pipeline.Why are people even arguing Node vs. Deno? They're two different things, and Node will not go away over night because of Deno.
because there's people already calling Deno the Node "killer" 😆
This. It's the typical case where someone hates something just because he doesn't understand it. I lost it when the post compared type safety with types in docs. It just shows a complete lack of theoretical knowledge.
Regardless of whether any of us agree with what he's saying, where in this post does he mention Art Deco?
dev.to has organization pages, for where to post things where "my thoughts are my own" doesn't apply.
His user name is literally the name of the company.
So, you're saying there's a company named "4r7d3c0"?
Ohhhh, I get it. The 4 is an "A" and the "7" is a "t", 3 is an "e" etc.
Yeah I guess you've kind of got a point there. Not sure if I'd call that "advertising," but there's definitely not the usual effort to separate person from org.
I agree.
If you work with technologies, the phrase "I'll never use put_technology_name_here_" shows shortsightedness... changes are always going to happen, whether you want it or not