Live data from Hacker News

Deno raises $21M

deno.com

61–70 of 397 posts

Re: Deno raises $21M

#61
post #33

Interesting how this will play out. It's an ambitious goal to consolidate client side and server side javascript ecosystems which is quite fragmented today. On the other hand, this may only increase fragmentation further by introducing another target to develop for (wait for transpilers that can automagically convert between deno and node code). I will always look at javascript as this problem kid that cannot get its…

https://xkcd.com/927/

Re: Deno raises $21M

#62
post #53
post #33

Interesting how this will play out. It's an ambitious goal to consolidate client side and server side javascript ecosystems which is quite fragmented today. On the other hand, this may only increase fragmentation further by introducing another target to develop for (wait for transpilers that can automagically convert between deno and node code). I will always look at javascript as this problem kid that cannot get its…

There is already a system for building a NPM node package from a Deno package, called dnt (deno to node). It's maintained by some Deno team members. Here's a blog post they wrote about porting "Oak" (a deno HTTP server framework) to Node: https://deno.com/blog/dnt-oak The nice thing about Deno conceptually, is that it's much more similar to the browser platform than node is. It uses ES6 only, has things like `fetch`…

Not to take away from the rest of your message, I thought you wanted to get up to speed on that `fetch` is now available in nodejs core since version 17 or something like that (think it got included early this year).

Re: Deno raises $21M

#63
post #11

The color changing on this page gives me a migraine: https://deno.com/deploy I like Deno in principle, but I'd love to see how Slack, Github and Netlify are using it.

Weird... it's having the same affect on me, something about slowly fading to white background is making me flinch. Is this a known phenomenon?

I suspect that it basically confuses your brain because it tries to adjust the "white balance" so that the background becomes normal white. But the background is just saturated enough and changing so quickly that it just can't follow.

Re: Deno raises $21M

#64
post #53

Earlier quoted context omitted.

There is already a system for building a NPM node package from a Deno package, called dnt (deno to node). It's maintained by some Deno team members. Here's a blog post they wrote about porting "Oak" (a deno HTTP server framework) to Node: https://deno.com/blog/dnt-oak The nice thing about Deno conceptually, is that it's much more similar to the browser platform than node is. It uses ES6 only, has things like `fetch`…

Not to take away from the rest of your message, I thought you wanted to get up to speed on that `fetch` is now available in nodejs core since version 17 or something like that (think it got included early this year).

I think this requires the `--experimental-fetch` command-line argument (per https://nodejs.org/tr/blog/release/v17.5.0/), so I don't think it qualifies as "by default".

Re: Deno raises $21M

#65
post #23

Deno deploy seems cool and all, but I haven't seen any great rationale for using their service over say Cloudflare Workers.

Yeah unless I'm missing something isn't this just a stand alone company offering roughly workers?

This is an open source JavaScript runtime with a hosted business model. Deno is great. Deno Deploy is a reasonable way for them to make money.

Re: Deno raises $21M

#66
post #11

The color changing on this page gives me a migraine: https://deno.com/deploy I like Deno in principle, but I'd love to see how Slack, Github and Netlify are using it.

> I like Deno in principle, but I'd love to see how Slack, Github and Netlify are using it.

https://docs.netlify.com/netlify-labs/experimental-features/...

All this dynamic processing happens in a secure runtime based on Deno directly from the worldwide network edge location closest to each user.

Re: Deno raises $21M

#67
post #14

Earlier quoted context omitted.

You don’t get $21M from investors for nothing. They will force the square peg through the unicorn-shaped hole - or kill the company trying

> You don’t get $21M from investors for nothing. Do you think that investors see every company that isn't a unicorn as "nothing"? I think you're living in a fairytale

If you're a venture capitalist, this is in fact the model.

Re: Deno raises $21M

#69
This question is going to make me sound like a jerk, but why do you want to write your back-end in JS? Deno looks like a great improvement over node.js, but I don't feel compelled to use it. It seems like people jumped to node based on some performance promises that didn't really pay off (IMO). And since then, we have newer options like Rust, Go, and Elixir as performant back-end options, and even older choices like Ruby and Python have continued to improve.

Seems like the standard arguments would be that developers already know JS, and that you can share code with the browser. I don't find these highly compelling.

EDIT: I haven't learned typescript yet, based on the replies, it seems like that could be a good reason to choose it. Seems like a nice middle-ground between typical scripting and compiled languages.

Re: Deno raises $21M

#70
post #14

Earlier quoted context omitted.

You don’t get $21M from investors for nothing. They will force the square peg through the unicorn-shaped hole - or kill the company trying

> You don’t get $21M from investors for nothing. Do you think that investors see every company that isn't a unicorn as "nothing"? I think you're living in a fairytale

They do, but that's not a bad thing. Sequoia invests in companies they think could be worth multiple billions.

If Deno reaches 30% of the impact of Node, their company could be worth billions.

In the meantime, we get a better open source runtime because they have money to build it out.

Post reply on HN