this post was submitted on 19 Aug 2024
26 points (96.4% liked)

Web Development

3454 readers
1 users here now

Welcome to the web development community! This is a place to post, discuss, get help about, etc. anything related to web development

What is web development?

Web development is the process of creating websites or web applications

Rules/Guidelines

Related Communities

Wormhole

Some webdev blogsNot sure what to post in here? Want some web development related things to read?

Heres a couple blogs that have web development related content

CreditsIcon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago
MODERATORS
snowe
erlingur
Ategon
26
Deno's Standard Library for JavaScript Finally Stabilized at v1 | 3min 5sec Video | Aug 8, 2024 (youtu.be)
submitted 4 months ago* (last edited 4 months ago) by ericjmorey to c/webdev
14 comments fedilink hide all child comments
 

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 are viewing a single comment's thread
view the rest of the comments
[–] spartanatreyu 3 points 4 months ago (1 children)

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.

[–] [email protected] 0 points 4 months ago (1 children)

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

[–] spartanatreyu 3 points 4 months ago

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.