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

The Deno Company

deno.com

Post reply on HN
Print view View original

391–400 of 446 posts

Re: The Deno Company

#391

Post by reader_mode »

forty wrote: post #308
wperron wrote: post #286

Earlier quoted context omitted.

Insofar as we take `.ts` files seamlessly yes -- though to be clear, one does not simply "run" TypeScript. There are no runtimes for TypeScript directly (there's AssemblyScript that _looks_ like TypeScript, but isn't exactly TypeScript) We've simply incorporated the type-checking and transpiling steps into the deno cli, making it super simple to get going, no config needed.

Exactly. And I guess the package still needs to be compiled to JS before deploying to production? To avoid shipping a full TS compiler on a production server which would be a crazy thing to do.

Why do you need a full TS compiler - you can just strip type annotations ala babel.

Re: The Deno Company

#392

Post by IgorPartola »

qbasic_forever wrote: post #384
IgorPartola wrote: post #374

Earlier quoted context omitted.

They can always get acquired by Amazon first.

It wouldn't surprise me if that's the eventual end goal. Amazon is looking for good Rust talent too from what I've read.

That’s the goal of almost all startups. Your chances of being acquired by a FAANG company are millions of times greater than going IPO. It is almost always the exit strategy.

Re: The Deno Company

#393

Post by ggregoire »

nightski wrote: post #385
ggregoire wrote: post #313

Earlier quoted context omitted.

So if you need that package in your 10 projects, do you copy those 20 lines of code in your 10 projects? Yikes. Then what happens when it requires a change? Do you make the change in all your projects? Double yikes. When it becomes 30 lines, do you still copy/paste those 30 lines in all your projects? Do you also copy/paste the tests related to those 30 lines in all your projects? ... Having reusable code wrapped int…

Or you create a library which contains a collection of 10-20 line of code modules and share it among your projects.

Yes I agree it's better to have one library with 20 helper functions than 20 libraries with 1 function each. Think Lodash.

Although some people will then complain about the size of the library...

Re: The Deno Company

#394

Post by qwtel »

davnicwil wrote: post #73

What I find most exciting here is: > Our infrastructure makes it possible to... create custom runtimes for different applications [like] Cloudflare Worker-style Serverless Functions Fascinated to see what happens here. The serverless / edge compute paradigm fits Javascript hand-in-glove philosophically, but until now it's always felt quite clunky to me. When I've tried it out, I've always been left thinking "but this…

There's lots of things going on this this space. It seems every other day I discover another Cloudflare Workers-like implementation (granted, most of them are for testing/development). I'm cataloging them here for anyone who's interested: https://workers.js.org

Re: The Deno Company

#395

Post by speedgoose »

ggregoire wrote: post #393
nightski wrote: post #385

Earlier quoted context omitted.

Or you create a library which contains a collection of 10-20 line of code modules and share it among your projects.

Yes I agree it's better to have one library with 20 helper functions than 20 libraries with 1 function each. Think Lodash. Although some people will then complain about the size of the library...

Yes. Every Lodash function is available in its own npm package too. I use it like this, I rather have 4 lodash packages than the big whole lodash library in one package with almost everything left unused.

Re: The Deno Company

#396

Post by speedgoose »

FunnyLookinHat wrote: post #40
gorjusborg wrote: post #23

Earlier quoted context omitted.

I've only dipped my toes in the water with Deno, but it solves a few pain points I've felt with Node. Direct deps via url vs npm as middleman, a standard library (thank goodness!), and single binary distribution. Types are great too, but these other things would be enough for me.

The built-in Typescript support is amazing, but the selling feature for me was the ability to generate static binaries. Shipping is much easier when your built process can produce a single output!

A NodeJS Docker container is a few lines. I agree Deno's single binary is a nice feature but it's not very interesting for everyone.

Re: The Deno Company

#397

Post by speedgoose »

TheMagicHorsey wrote: post #239

This is probably unpopular here, but I wish people would just stop using Javascript on the server. Well, I wish they would stop using it period, but at least in the browser it makes some sense. Edit: to be clear, I have no beef with Typescript, Dart, Clojurescript, and the many other languages that compile into JS. It's JS itself I have issue with. I feel like it gives too much flexibility to young programmers to scr…

If you have to use JavaScript, you can configure eslint with some plug-ins to have pretty good safeguards or training wheels. You will still miss some strong typing but eslint will warn or prevent most of the awful or stupid code.

Re: The Deno Company

#398

Post by musingsole »

kyawzazaw wrote: post #387
musingsole wrote: post #376

Earlier quoted context omitted.

> And yet we've never seen anyone beat Amazon yet. That largely depends on your definitions of "beat" and "win". There are plenty of software infrastructure firms out there that Amazon has yet to smash into the ground. Nature seems to think (and I agree) simply existing is winning.

Please give examples. I would like to learn more about it (even if subjective)

DigitalOcean is a competitor of comparable size (even if its like a pebble to a boulder): https://finance.yahoo.com/news/blavatnik-backed-digitalocean...

Re: The Deno Company

#399

Post by runawaybottle »

speedgoose wrote: post #395
ggregoire wrote: post #393

Earlier quoted context omitted.

Yes I agree it's better to have one library with 20 helper functions than 20 libraries with 1 function each. Think Lodash. Although some people will then complain about the size of the library...

Yes. Every Lodash function is available in its own npm package too. I use it like this, I rather have 4 lodash packages than the big whole lodash library in one package with almost everything left unused.

JS libraries only did that to reduce bundle size being sent to the browser. It’s done out of necessity, not because it makes any sense.

Exporting out one method at a time is pretty absurd.

Re: The Deno Company

#400

Post by speedgoose »

runawaybottle wrote: post #399
speedgoose wrote: post #395

Earlier quoted context omitted.

Yes. Every Lodash function is available in its own npm package too. I use it like this, I rather have 4 lodash packages than the big whole lodash library in one package with almost everything left unused.

JS libraries only did that to reduce bundle size being sent to the browser. It’s done out of necessity, not because it makes any sense. Exporting out one method at a time is pretty absurd.

Lodash has a lot of features that are not needed anymore or even dangerous sometimes. If you don't need them, why would you install them?
Post reply on HN