Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Deno raises $21M

deno.com

Post reply on HN
Print view View original

311–320 of 397 posts

Re: Deno raises $21M

#311

Post by throwawaylala1 »

irrational wrote: post #228
nickjj wrote: post #217

From the post: > For example, it is integrated with GitHub in such a way that on every push it will provision a new server running specifically that code, deployed to the edge, worldwide, and persisted permanently. Want to access the code your app was running a month ago at commit f7c5e19? It will be served up instantly at a moment's notice. It costs you nothing to have that bit of JavaScript responding to requests i…

There are ways to version your database schema. Then you just need to make sure your code version is tied to your database version.

You can't restart all of your web services atomically. What happens if two web services are running two different versions for a couple seconds?

Re: Deno raises $21M

#312

Post by ascorbic »

Vinnl wrote: post #156
brundolf wrote: post #78

Earlier quoted context omitted.

What is their actual business model? I know there's Deno Deploy, and presumably they offer some kind of enterprise-support type deal. But the first is easily copied by competitors (in an already-crowded market), and the other isn't super lucrative. Is there anything else? I love Deno and want it to succeed, but it doesn't feel like a unicorn, and I'm worried about it being expected to become one

Considering that one of those competitors is Netlify, then either the incumbent (i.e. Netlify) is in a great position to benefit from a succeeding Deno, or Deno Deploy does succeed and Netlify can profit from that. A bunch of other participants (GitHub/Nat Friedman, Automattic) seem like they could benefit from a thriving ecosystem around Deno as well, even if Deno Deploy isn't particularly successful.

Netlify Edge Functions use Deno Deploy, as do Supabase Edge Functions. I'd imagine that's a significant part of their revenue. (I work at Netlify, but have no insight into the financials of this arrangement)

Re: Deno raises $21M

#313

Post by bowsamic »

spartanatreyu wrote: post #229
bowsamic wrote: post #100

Earlier quoted context omitted.

The world doesn’t exist to cater to your weird specific thing that gives you a headache

As a matter of fact, it's exactly the opposite. We have web accessibility standards and companies get sued for not following them.

That is terrible

Re: Deno raises $21M

#314

Post by intothemild »

vcryan wrote: post #188

Deno overstates the problem it is intended to solve because its founders needed to justify achieving funding by being developer-famous. Let's say a company were to adopt this tech over Node, well, it seems like it would be slightly better, but probably not much of a game-changer. I'll leave it to y'all to talk about what tech is truly interesting as I don't want to seem ideological/biased, I just don't see how Deno i…

> its founders needed to justify achieving funding by being developer-famous.

If I remember my Javascript-of-the-week-drama correctly, didn't Deno become a thing because a couple node/npm devs were upset that there was someone in the core node/npm team who did a bad thing?

Am I remembering this right?

Re: Deno raises $21M

#315

Post by ascorbic »

potamic wrote: 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…

Deno code is really close to browser code. If you have ESM code that runs in the browser and doesn't need access to the DOM then it's a good bet it'll run on Deno, and vice versa. They use web standards for most things, and anything proprietary is put on the Deno global object. For standards that need adapting to work outside the browser, they're working with Cloudflare and others on WinterCG, which is defining a common baseline for these non-browser runtimes.

Re: Deno raises $21M

#316

Post by ascorbic »

tambourine_man wrote: post #61
potamic wrote: 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/

That's not a fair reply. One of the main benefits of Deno is that they're using existing standards. It's Node that's the outlier.

Re: Deno raises $21M

#317

Post by ascorbic »

TazeTSchnitzel wrote: post #15

> Early in cloud computing, virtual machines were the compute abstraction […] This is funny to me because serverless sounds to me like the return of PHP (etc) shared hosting. What's old is new again?

Anyone who has had to maintain a shared PHP server would say that's very different. I used PHP for years, and now use serverless functions (both Lambda and Deno). Serverless means you don't need to worry about anything except the code. It scales automatically. It never needs updating. It doesn't go down in the middle of the night. It can roll back deploys instantly. Sure, you could pay for managed hosting, and then pay more for scaling, and set up automation for deploys, but give me serverless functions any day of the week. They just work.

Re: Deno raises $21M

#318

Post by bengale »

javajosh wrote: post #250
Androider wrote: post #205

Earlier quoted context omitted.

It's usually not enough to be a bit better than what you're trying to displace, you have to be 10X better than the status quo to have any real impact. For example, SVN tried to be a better CVS, while Git came out of left field and destroyed the competition by being 10X better. In that, Deno reminds me of the once-hyped Meteor.js. Meteor.js also though that funding could be the answer, but it wasn't. They're both clev…

>Deno reminds me of the once-hyped Meteor.js In substance they are similar in that they both want/ed tighter "vertical integration" of tools ("DX") in an opinionated way, with the money-making plan being convenient paid hosting. "Look how easy and fun it is to make powerful stuff; we hope you give us money to host it for you!" So far the only company that's had success with this pitch is Amazon of all people, by offe…

> In substance they are similar in that they both want/ed tighter "vertical integration" of tools ("DX") in an opinionated way, with the money-making plan being convenient paid hosting. "Look how easy and fun it is to make powerful stuff; we hope you give us money to host it for you!" So far the only company that's had success with this pitch is Amazon of all people, by offering a staggering array of partially specialized EC2 instances behind an API.

I think NextJS and Vercel probably fall into this bucket as well.

Re: Deno raises $21M

#319

Post by nl »

brundolf wrote: post #309
nl wrote: post #295

Earlier quoted context omitted.

You have to work pretty hard to make Python (or any other language with reasonable web frameworks) busy-wait! Blocking is NOT the same as busy wait.

Ah, I didn't realize there was a distinction Still, despite that it seems like there's a big advantage to be had

Is there thought?

What's the actual difference between (JS):

  let x = await doSomeLongProcess();
  console.log("done: " + x);
vs (Python)

  x = await do_some_long_process()
  print("done: " + x)

Re: Deno raises $21M

#320

Post by ascorbic »

mkroman wrote: post #161
pseudosavant wrote: post #92

As a Deno fan I was surprised to learn that the free tier for Deno Deploy includes 100k requests per day and 100GB of bandwidth monthly. I know I'll be trying it out now.

> Up to 10ms CPU time per request So less than 17 minutes of CPU time per day - not a lot, but also not nothing.. But at 10ms per request, what would one use it for? Just server-side rendering for something simple?

Bear in mind this is CPU time, not wall clock time. I work with both AWS Lambda functions and Deno Deploy functions every day. I hit the 10s Lambda timeout all the time (things like slow API calls or network requests), but I never hit the timeout for Deno Deploy. You can even use it for things like Server-Sent Events or Websockets. It'll keep the connection open indefinitely, as long as it's not using the CPU.
Post reply on HN