Re:Deno 1.6 supports compiling TypeScript to a single execut...
by svnpenn on Thursday December 10, 2020 @12:41AM
(#25370213)
My point is, what is even the point of using Deno? If its for static typing... well Go has that.
So what is the benefit?
Re:Deno 1.6 supports compiling TypeScript to a single execut...
by throw_m239339 on Thursday December 10, 2020 @02:22AM
(#25370836)
> So what is the benefit?
A better type system(covariance, dependent types) than Go's and generics, a richer ecosystem, deploying the same codebase on the server and in the client...
Re:Deno 1.6 supports compiling TypeScript to a single execut...
by Soremwar on Thursday December 10, 2020 @02:07AM
(#25370744)
What's even the point of using Go? If it's for static typing Rust has that
So what's the benefit?
Same can be said about any language really, it's personal preference
Re:Deno 1.6 supports compiling TypeScript to a single execut...
by ben509 on Thursday December 10, 2020 @12:26PM
(#25376025)
If you wrote a browser client in Javascript / Typescript, then it makes sense to write a backend in it as well since it's easy to share code and data between them.
Now you can also write CLI tools that are trivial to deploy and can also share code with everything else.
This is the same motivation behind other languages that do the reverse; compile to JS / WASM.
Re:Deno 1.6 supports compiling TypeScript to a single execut...
by fareesh on Thursday December 10, 2020 @02:37AM
(#25370933)
Guessing here - is there any value from a team / engineering point of view to having shared code for custom classes / data structures between client and server? Here I assume client to be mean browser
The point is that this makes deploying a Deno application simpler. Binary size is kind of the wrong metric to worry about.