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

Deno 1.27

deno.com

Post reply on HN
Print view View original

41–50 of 71 posts

Re: Deno 1.27

#41

Post by kitsonk »

shafyy wrote: post #16
triyambakam wrote: post #7

I'm an eager and early adopter of Deno. I however look forward to ecosystem improvements, and the interop with npm is helpful. I was working on a side project recently that was a simple CRUD app and I just ended up going with Express on Node after fighting with Oak on Deno for a few days. It was still in the way enough to slow down the rapid fire development process that happens when you're still figuring out an idea…

I'm also dipping my toes in Deno (with Fresh) for a side project. Just curious, what were the blockers you came across with Oak?

Yeah, I would be interested to understand what challenges you had with oak too.

Re: Deno 1.27

#43

Post by rubenfiszel »

We bet big on deno with Windmill (OSS platform to turn scripts into internal UI and workflows) [1][2] and are extremely pleased. The language design choices and the performances/caching strategies are a perfect match for building a distributed workflow runtime at scale. However, the compatibility with npm was the most requested feature. Before the compatibility mode with npm was released, we were about to build a completely separate mode of execution based on node. This solves it very elegantly.

Also super excited about the lsp improvements. I believe we are the only project to have a webeditor that features lsp integration with deno in the web (to test, go on [3], New Script -> Next, it works really well). It's very pleasant to work with and make the webeditor experience match closely a local dev setup. We are super excited about the improvements and I am about to try tonight if we can have the inline hints work with monaco. As we are fully open-source, one can see how we are able to pull it off [4][5].

[1]: https://windmill.dev

[2]: https://github.com/windmill-labs/windmill

[3]: https://app.windmill.dev

[4]: https://github.com/windmill-labs/windmill/blob/main/frontend...

[5]: https://github.com/windmill-labs/windmill/blob/main/lsp/pyls...

Re: Deno 1.27

#44

Post by [deleted] »

JoyrexJ9 wrote: post #39
triyambakam wrote: post #7

I'm an eager and early adopter of Deno. I however look forward to ecosystem improvements, and the interop with npm is helpful. I was working on a side project recently that was a simple CRUD app and I just ended up going with Express on Node after fighting with Oak on Deno for a few days. It was still in the way enough to slow down the rapid fire development process that happens when you're still figuring out an idea…

Yeah NH gives a warped lens on how ready these runtimes & frameworks are for real work. Threads about Deno and Bun pop up almost weekly, yet in my experience they remain a long, LONG way from the stable (and admittedly stale) experience we have with Node and NPM

[deleted]

Re: Deno 1.27

#45

Post by brundolf »

alberth wrote: post #28

Dumb question: which appears most promising? Deno, Just-JS or Bun? (Genuine question. Not trolling)

From the little I've read about just-js, I'm not sure it's even trying to be a competitor with the others for their main use-cases

I think Deno has the strongest overall vision, and it's a vision I really want to see become the new default

Bun is compelling with its blistering pace and its ruthless dedication to performance, compatibility, and Just Works user experience. However, it's still very new and missing a lot of key features, and subjectively it just feels too "chaotic" for my tastes. They're designing it as they go, as fast as they can, but it feels like a wild ride. I'm not sure the creator even knows exactly where it'll end up, and in general it seems to prioritize "does everything you'd like it to right now" over "lay a new, better foundation for how the JS ecosystem works, unburdened by the historical baggage of Node"

Two very different mindsets; it'll be really interesting to see which one wins. Personally I'm rooting for Deno, but I think each of them is pushing the other one to be better.

Re: Deno 1.27

#46

Post by simlevesque »

e63f67dd-065b wrote: post #24

> RBTree has been removed from the collections module in favor of RedBlackTree. > direction has been removed from the collections module in favor of Direction. > CSVStream has been removed from the encoding module in favor of CsvStream Hmm I smell an interesting story here. If it's renaming for the sake of renaming then that's kinda dumb and breaks backwards compat for no reason, but presumably there's a better reaso…

Node.js before v1 (maybe even until v4) was like this. It took like 5 years.

Re: Deno 1.27

#47

Post by Tomuus »

nerdponx wrote: post #27

Maybe this is a weird question, but how does Deno compare to Node when it comes to the various "languages that compile to JS"? For example Purescript, Fable, Elm, etc. does everything mostly just work, or should one stick to Node for those?

Things mostly just work. Remember Node.js is mostly APIs on top of JS the language. If those tools compile to JS in the browser, they can compile to Deno. Deno is a more stabdards-based runtime than Node, it's closer to how the browser works.

Re: Deno 1.27

#48

Post by [deleted] »

brundolf wrote: post #45
alberth wrote: post #28

Dumb question: which appears most promising? Deno, Just-JS or Bun? (Genuine question. Not trolling)

From the little I've read about just-js, I'm not sure it's even trying to be a competitor with the others for their main use-cases I think Deno has the strongest overall vision, and it's a vision I really want to see become the new default Bun is compelling with its blistering pace and its ruthless dedication to performance, compatibility, and Just Works user experience. However, it's still very new and missing a lot…

[deleted]

Re: Deno 1.27

#49

Post by andrewmcwatters »

I'm curious how strongly Deno matters to the developers in this space. Honestly, I just don't care. I really, really don't care. When Node.js succeeded PHP in industrial practice, it was enough then to get me to move since everyone had already jumped onboard quickly.

Now, it's gotta take a LOT for me to want to move. I'm already too productive with Linux, Nginx, MySQL, and Node.js w/ Express, and React on the front-end. I have little to no reason to try anything out.

On a similar note, while people are switching from Webpack to Turbopack, I'm kicking back writing actual product features with a near buildless process. Because I simply don't care. I use the "Run JSX Preprocessor" straight out of the docs as I work and commit the output.

Screwing around with switching back and forth and changing build configurations every few years reminds me of when back in the day people would supercustomize their desktop environments instead of just accepting them as they are.

Is anyone really working up a sweat over security theatre like passing in args to flip permissions flags?

Could you imagine how ridiculous that would sound in literally any other programming environment? That you can't trust your own software and its dependencies--that YOU built?

Re: Deno 1.27

#50

Post by randomguy0 »

JLCarveth wrote: post #26
randomguy0 wrote: post #22

Earlier quoted context omitted.

Is this Jeopardy? Your question is essentially answered by his original comment.

Pardon? I am asking OP why he's annoyed that the post mentions VSCode. It's not normal to be annoyed at the mere mention of a text editor. You should work on 1. your reading comprehension, and 2. making relevant comments to the discussion at hand.

Yeah, sure. Maybe heed your own advice.
Post reply on HN