Deno's Standard Library for JavaScript Finally Stabilized at v1 | 3min 5sec Video | Aug 8, 2024
Deno's Standard Library for JavaScript Finally Stabilized at v1 | 3min 5sec Video | Aug 8, 2024
Video Description
Many programming languages have standard libraries. What about JavaScript? 🤔️
Deno's goal is to simplify programming, and part of that is to provide the JavaScript community with a carefully audited standard library (that works in Deno and Node) that offers utility functions for data manipulation, web-related logic, and more. We created the Deno Standard Library in 2021, and four years, 151 releases, and over 4k commits later, we're thrilled to finally announce that it's 30 modules are finally stabilized at v1.
Learn more about the Deno Standard Library
Read about our stabilization process for the library
You're viewing a single thread.
Oh wow, yet another standard library for JS 😂
What standard library?
JS has only had package/library hell
Kinda my point. And this is another garbage bag on the pile.
https://stdlib.io/ is just the most obvious thing to come to mind. Jeeze jQuery even sat on this chair.
Deno people are trying so fucking hard to be relevant. It's embarrassing. Bringing nothing to the table has been their MO from day 1.
stdlib.io is a data process/vis library, not a standard library.
jQuery was a DOM/Utility DX library (and also a compatibility layer before all browsers finally focussed on standards), not a standard library.
Deno people are trying so fucking hard to be relevant. It’s embarrassing. Bringing nothing to the table has been their MO from day 1.
Let's examine that.
Deno has always been:
(parapharing) "Hi, I'm the creator of Node and want to make it better but can't get everyone on board with the changes. So I'm going to create a new JS runtime. Node will need to implement these improvements to keep up or everyone will switch away from node. Either way, developers win."
We know it's been that way since he was a month into Deno's development in his famous talk: 10 Things I Regret About Node.js
Deno [...] Bringing nothing to the table [...]
Have a look through each of those 10 points he brought up, then compare that to node before, and node now. It's pretty clear he gave them the swift kick in the ass to start making those changes. We win. That's clearly a success.
Everyone who has ever heard of deno has read this irrelevant blog post. It was even stupid at the time he wrote it. People had long been containerizing their node payloads to solve most of his concerns and building ts-node into your js engine as a preprocessors was also beyond redundant. Everything is such a gimmick and people actually followed the marketing and went through years of unstable development for nothing. And now bun people are recycling the same hype approach to gain relevance
You keep saying "relevance", and now other things like "gimmick" and "marketing".
Why are you so focused on "relevance"?
They're completely unrelated to Deno.
Node had problems, ts-node had problems, Deno fixes those problems for developers.
Separately, Bun trades solving some problems for solving other problems.
Developers are free to choose between runtimes based on what problems they encounter.
Personally I use node for existing web projects and deno for data processing and to compile scripts into redistributable binaries.
Yet another? The only other one is Node's and that is trash.
The video mentions some "de facto" standard libraries like Lodash or Underscore. But there is also Bun which try to promote their standard library like their test runner, their HTTP server, etc..
I like Deno's approach, since they try to make their “Standard library” also available for other platform. But only few of them are compatible with Node.js.
For instance,
@std/cliis only available for Deno. So I'll stick with commander which is more standard for CLI tools, and it works with Deno, Bun & Node.js.Good info! Thanks!
I wonder if Deno will expand compatibility further
Node comes with a JS library? This thread is full of surprises.
Yeah in order to access native features that Node supports and you can't do on the web, like running processes and opening TCP connections.
That's not a standard library for JS. Those are builtin modules. A standard library should be available for inclusion in various consumers.
Well this isn't a standard library either then. But seeing as it is literally called that I'd say your unusually restrictive definition is nonsense.
