this post was submitted on 19 Aug 2024
26 points (96.4% liked)
Web Development
3443 readers
18 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
- Follow the programming.dev site rules
- Keep content related to web development
- If what you're posting relates to one of the related communities, crosspost it into there to help them grow
- If youre posting an article older than two years put the year it was made in brackets after the title
Related Communities
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Wormhole
Some webdev blogs
Not sure what to post in here? Want some web development related things to read?
Heres a couple blogs that have web development related content
- https://frontendfoc.us/ - [RSS]
- https://wesbos.com/blog
- https://davidwalsh.name/ - [RSS]
- https://www.nngroup.com/articles/
- https://sia.codes/posts/ - [RSS]
- https://www.smashingmagazine.com/ - [RSS]
- https://www.bennadel.com/ - [RSS]
- https://web.dev/ - [RSS]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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
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.