r/programming • • Jan 29 '22

Node.js will include support for `fetch` in their next release

https://github.com/nodejs/node/pull/41749
1.3k Upvotes

171 comments sorted by

192

u/recitedStrawfox Jan 30 '22

The heavens have listened to our prayers!!!! Npm can finally rest in ease from the countless times I typed "npm i node-fetch".

49

u/addandsubtract Jan 30 '22

axios in shambles

8

u/Unnecro Jan 30 '22

Does node-fetch support interceptors as axios do?

5

u/recitedStrawfox Jan 30 '22

No idea. I only use it for simple GET requests.

304

u/earthboundkid Jan 29 '22

Wow. Node is new IE. Starting to catch up to Edge 12 though.

159

u/[deleted] Jan 29 '22

Yeah... It was very difficult for me to understand why you either need to use the ancient callback based http and https and handle "chunks", or import a third party library like axios to do something so basic, when there is a set of great, widely used, modern APIs out there for browser. I wrote a nodejs script a while ago and was surprised that was still the case in 2022.

And I think that's still the case for things like child_process, and many people want to have a Promise based version given what I saw on stackoverflow. This is just ridiculous.

62

u/knome Jan 29 '22

When something runs everywhere, it needs to stay compatible everywhere.

19

u/lenswipe Jan 30 '22

I don't think anyone is proposing that the http and https modules be taken away... Just that fetch be added.

25

u/jonny_eh Jan 30 '22

If the browser can evolve, Node should be able to evolve faster.

9

u/MINIMAN10001 Jan 30 '22

The browser can evolve because Chrome grew so big they could basically set the standards for everyone else.

10

u/scratcheee Jan 30 '22

browser evolution was happening before chrome (certainly before the chrome monopoly), the key turning point was when ie6 stopped being the majority of the market (and thus holding everyone back)

Chrome might have sped up standards movement by moving fast and being in front, but the browser ecosystem has thankfully already proven it can function without a monopoly, and even with chrome’s lead position, plenty of new standards are developed primarily by their competitors.

4

u/Food404 Jan 30 '22

But isn't node more of a versioned backend JS in contrast to what web browser JS has to deal with? Besides, adding fetch doesn't mean they need to immediately remove other HTTP request features

1

u/jl2352 Jan 30 '22

Adding fetch support wouldn't break any compatibility.

1

u/xmsxms Jan 30 '22

Adding APIs doesn't break compatibility, just changing existing ones. If there is a system that is broken by the adding of APIs, it would have already been broken and fixed multiple times as new APIs are added regularly.

1

u/earthboundkid Jan 30 '22

Okay, but Node doesn’t stay compatible, so that’s the not what’s going on.

0

u/[deleted] Jan 29 '22

[deleted]

6

u/jadecristal Jan 30 '22

Like, double-plus with things like nvm around?

-14

u/knome Jan 29 '22

They're wanting to use stuff released two years ago in the browser.

That will net you a lot of folks these days, way more than back in the early 2000s when most of them were manually updating or punting off microsoft updates, but you'll still catch folks on limited platforms or just older ones.

Maybe you don't mind excluding those that lag technologically, but a project meant to run across all of the browsers should probably avoid making that decision for its users.

0

u/[deleted] Jan 29 '22

[deleted]

-11

u/knome Jan 29 '22 edited Jan 30 '22

the date in this comment is incorrect

According to MDN Edge only got it in version 14, which was 2020. I didn't check the others because I figured microsoft would be lagging for getting anything implemented.

Browser is what the original poster I responded to mentioned, so I assumed they were complaining about how stuff like webkit transpiles everything down to a nice common demominator before slapping it out over the wire.

Seemed they meant "javascript ecostem" rather than node proper.

27

u/ifonefox Jan 29 '22

According to MDN Edge only got it in version 14, which was 2020

Edge 14 came out in 2016. If you hover over the version number in MDN's compatibility table, it will tell you when that version came out. Safari is the latest browser to get it, and that was in 2017.

12

u/knome Jan 30 '22

+ /u/ClutchHunter

Ah, fair enough. That's what I get for trusting a highlight from a google search for "edge 14 release". Apparently the date was from wikipedia and actually referred to the Edge+chromium release rather than version 14.

Jeez, google. Can't you guys write a semi-decent fully conscious indexer to feed me incidental tidbits?

4

u/[deleted] Jan 29 '22

caniuse and this blog post suggest Edge 14 came out in 2016. I may be confusing it with how they versioned the engine, it's hard to tell.

Did they mention that? I'm misreading or perhaps you got threads crossed? :)

1

u/keeganspeck Jan 30 '22

You mean Webpack, not WebKit, right? And fetch was available in Chrome 42... 7 years ago, 2 months before Edge even existed.

-1

u/Ratstail91 Jan 29 '22

Wait, there's am alternative to fetch? Lol

11

u/[deleted] Jan 29 '22

XMLHttpRequest glug

That's probably what you'll see in a fetch polyfill.

8

u/ShortFuse Jan 29 '22

Really, it's just for the NodeJS Streams, where you'd want to not use fetch. We have WhatWG streams (body.getReader()) in NodeJS now, but performance is much worse. Proxying is also much easier because a Webserver's response type matches the NodeJS client request response type (IncomingMessage).

1

u/jadecristal Jan 30 '22

WhatWG 🠖 🔥

1

u/danbulant Jan 30 '22

That's why Deno exists.

-1

u/Jolly_Front_9580 Jan 30 '22

there is nothing wrong with importing Axios. Express is also something fundamental to the ecosystem and is not part of Node core.

8

u/[deleted] Jan 30 '22

The part that is wrong is called "adding one more third party library dependency" which increases installation time and size, increases bundle size and adds potential security risk. This kind of thought is exactly what's wrong with the JS ecosystem

4

u/[deleted] Jan 30 '22

fetch was actually a good add, but in general adding stuff to the standard library is not great either. it will end up eventually filled with obsolete crap if you got wild with that.

4

u/Jolly_Front_9580 Jan 30 '22

Yeah. A way the Spring team has addressed this is through modularizing their project dependencies. Their http async client is its own dependency, not part of Spring framework itself.

3

u/[deleted] Jan 30 '22

Sorry that's a bad argument. It all comes down to how you manage your standard library. Never heard of people saying that about C++ -- "why do they keep adding things to the standard! Why do they add auto, constexpr, decltype, smart pointers, lambda expressions etc, the old way of doing things is perfectly fine!"

1

u/Jolly_Front_9580 Jan 30 '22

Nobody is saying adding fetch is not a good idea. But having Axios is okay when you consider the very nature of the ecosystem (you can’t get anything started with just node core). And having a strong open source community that can deliver things faster then the core framework team is neve gonna be a disadvantage

0

u/[deleted] Jan 30 '22

You're surprised JS ecosystem is shit ? What are you, new to this ?

-2

u/constant_void Jan 29 '22 edited Jan 30 '22

git?

edit - I don't know why this is getting downvoted. git uses http/https chunking.

-22

u/kz393 Jan 29 '22

I like Promises more than async/await since I find it easier to interface with synchronous code.

11

u/za419 Jan 30 '22

Promises and async/await are literally the same thing, are you aware of that?

Async/await are just syntactic sugar to make a Promise look synchronous to the code around it. Its the same thing under the hood. You can see, and I have seen, code like const result = await new Promise(...)

What I assume you mean is you prefer to use the more callback-ish style with .then and friends. Which is fine, although I don't think most people would agree..

0

u/avwie Jan 30 '22

Are you comparing backend JS engine with a browser?

1

u/earthboundkid Jan 30 '22

Yes because the backend engine isn’t as good at evaluating JavaScript as the browser engine.

519

u/subfootlover Jan 29 '22

Stop trying to make fetch happen. It's not going to happen.

https://www.youtube.com/watch?v=Pubd-spHN-0

-9

u/davawen Jan 30 '22

why is everyone getting downvoted lol

9

u/Kissaki0 Jan 30 '22

Not everyone is getting downvoted. Those comment replies that added nothing of value got downvoted.

Thankfully, because I would rather not see 100 “me too” comments instead of 100 upvotes, or more off-topic comments that would make it hard to read and discuss on topic, or find the clever or interesting on-topic jokes.

-51

u/bigbobbyboy5 Jan 29 '22

take my upvote

-51

u/muchbravado Jan 30 '22

Oh wow came here to say this lol

9

u/jadecristal Jan 30 '22

We all did, now shut up and upvote parent. 🤣

-55

u/swyx Jan 30 '22

how original

-6

u/degaart Jan 30 '22

You must be fun at parties

-47

u/NiceTryAmanda Jan 30 '22

Honest request is it possible to get in on the downvote train?

-33

u/RunnyPlease Jan 30 '22

Only if I can join you.

54

u/confusionglutton Jan 30 '22

I just spent all of Thursday implementing an injection system so my library (internal work project) could switch between fetch and node-fetch as needed. Now you're telling me this can just be taken out in a few months? Kill me.

25

u/Varedis267 Jan 30 '22

Cross-fetch would have likely been your friend in this scenario.

4

u/FrancisStokes Jan 30 '22

Or isomorphic-fetch

9

u/Varedis267 Jan 30 '22

As with every node package there are a hundred to do the job, but isomorphic-fetch hasn't been updated for over a year whereas cross-fetch is in very active development

3

u/FrancisStokes Jan 30 '22

I've found, through experience, that time since last update isn't a particularly useful or telling metric. Some packages implement a fixed API and don't need to change often.

It's not always the case, but I don't find it to be compelling in and of itself.

2

u/Varedis267 Jan 30 '22

Whilst true sometimes, when paired with 40+ issues and people reporting security issues, it's probably not the case. I wasn't advocating that time since last update was the only thing to look at. Not updated in 2 years and 1 open issue is probably better than updated in 5 days with 200 open issues if they have the same number of downloads. However, not updated in 2 years with 200 open issues is a different story.

Sometimes it takes a bit of research to get a more rounded picture.

5

u/[deleted] Jan 30 '22

whereas cross-fetch is in very active development

....so it just have a lot of bugs that need fixing ?

6

u/Varedis267 Jan 30 '22

Fixing issues that people find vs ignoring a growing list of issues, not implementing patches for vulnerable packages and letting peoples PRs go stale, I know which one I would take. Feel free to make your own decision though

2

u/_tskj_ Jan 30 '22

How can such a simple package need constant development?

2

u/Varedis267 Jan 30 '22

Security issues always crop up on packages that should be fixed

11

u/jl2352 Jan 30 '22

In fairness it looks like this is added under an experimental flag initially (I only read the top of the PR).

I'd argue you should be running real world projects on the LTS version of Node, which is version 16. Which I'd expect won't get fetch. You should wait until the next LTS version of Node before using it.

So that work isn't all wasted.

1

u/falconfetus8 Jan 31 '22

Hey, at least you only lost one day!

-17

u/duckducklo Jan 30 '22

Might've should've used Deno which already implements fetch and other modern web api's

10

u/confusionglutton Jan 30 '22

Deno

We're stuck on node for "large company compliance" reasons

3

u/cbzoiav Jan 30 '22

Large company compliance reasons usually have you a major LTS version back as well so you may get a bit more life out of your injection code!

75

u/VisibleEpidermis Jan 30 '22

Can someone explain what this is? Not a frontend dev.

101

u/[deleted] Jan 30 '22

I'm a front end dev and probably saying this imprecisely, but basically Javascript in the browser has a native "fetch" api for fetching some response from a url.

Node does not have this built in, so there is a commonly installed third party package called node-fetch to provide that functionality.

Looks like native fetch is finally coming to Node.

7

u/duckducklo Jan 30 '22

Deno, an alternative to Node, already implements fetch and many other standard web api's. Deno is the modern choice and if you haven't used it, you should look into it. Article for more info: https://blog.logrocket.com/what-is-deno/

2

u/santsi Jan 31 '22

I've abandoned Node/Express in favour of FastAPI. It's just superior in every way I can think of.

1

u/duckducklo Jan 31 '22

could u explain

1

u/dragneelfps Jan 30 '22

Deno looks meh. Importing from url sounds great but impractical in usage. The only thing I liked is the sandbox. I hope something similar is adopted by node.

0

u/[deleted] Jan 30 '22

[deleted]

9

u/yamalight Jan 30 '22

It is very much production ready (and has been for a while). The only issue - when compared to node - is the (size of) ecosystem (since it's not compatible with existing node modules out-of-the-box)

1

u/renatoathaydes Jan 30 '22

It's not fully compatible yet, but the roadmap for this year seems to have made correcting that a priority and there's already a compat mode that seems to be only missing a few edge cases to be fully compatible.

1

u/duckducklo Jan 31 '22

And for anyone reading this, keep in mind, every great thing starts with a small following. You can choose to be part of the greatness early, or stay behind and join when everyone else does.

0

u/[deleted] Jan 30 '22

[deleted]

2

u/maest Jan 30 '22

Is he wrong, though?

33

u/remuladgryta Jan 30 '22

When it comes to asynchronous code, the JS ecosystem has been moving away from callback based APIs and towards promise based ones. fetch is the promise-based replacement for (the poorly named, as it is neither limited to XML nor to HTTP) XMLHttpRequest and has been supported by browsers since ~2015-2017.

3

u/4dk5f5g Jan 30 '22

2015? It was in ie6 in 2006 and in gecko in 2000! I totally had to look that up, not something I knew off the top of my head, but yeah I was using it way before 2015.

7

u/Worth_Trust_3825 Jan 30 '22

You can thank microsoft for that one./

20

u/jl2352 Jan 30 '22

Browsers have an old way to make HTTP requests. XMLHttpRequest. For various reasons it's pretty shit to use.

Browsers added fetch, which is a much nicer and more modern way to make requests. It's a pretty sweet API. fetch only works within the browser.

JavaScript developers like to write code that can run on both the browser, and on Node. As fetch is only available in the browser, any code uses it cannot run on Node. Instead we import a library that wraps fetch, and offers it for us.

tl;dr; Node adding fetch support makes life simpler.

1

u/stronghup Jan 30 '22

It makes sense why should a program or module which doesn't touch the browser's GUI/DOM -API at all not run also outside the browser.

8

u/jl2352 Jan 30 '22

If it doesn't touch any DOM APIs, then yes it should run outside of the browser just fine.

The problem is people do want to use those APIs on Node. The main example is SSR (server side rendering).

What is SSR ... you know how JS frameworks are kind of shit because they load up client side? You have this big loading page when you visit a site? You ask yourself 'why don't they just send back a regular HTML page?' SSR solves all of that.

SSR only works if your code can run on Node and the browser. If the API is missing on Node, then that is a problem you need to deal with (although it's pretty simple to solve).

SSR aside. It also makes life simpler if you have only need to learn one API. Rather than two APIs.

1

u/stronghup Jan 31 '22

Yes it would make development much smoother if the same code would work on both Node.js and the browser at least most of the time.

The situation is not much different from trying to have all browsers execute the same js-code with the same results.

It seems the Node.js team are now taking this issue seriously as evidenced by the inclusion of fetch in Node.js. I hope they will continue along this axis. We need one platform to rule them all :-)

I'm vaguely aware that there is such a thing as 'Headless Chrome". Could that be part of the solution?

5

u/amroamroamro Jan 30 '22 edited Jan 30 '22

One of the features that defined Web 2.0 was AJAX and asynchronous XHR calls using the XMLHttpRequest API.

Ever since ES6, fetch was introduced as an alternative to achieve the same thing but using promises instead of callbacks.

6

u/mnilailt Jan 30 '22

This is a back end feature

3

u/[deleted] Jan 30 '22

fetch is an HTTP request API that is simpler than the older XMLHttpRequest API and is defined by the ECMAScript standard. "javascript" refers to implementations of the ECMAScript standard. many implementations exist and implement things differently. nodejs is a backend runtime with its own implementation of javascript which does not include fetch

4

u/IceSentry Jan 30 '22

This is about nodejs which is not a frontend framework.

-1

u/addandsubtract Jan 30 '22

Not with that attitude. NextJS (and others) close the gap between frontend and backend pretty seamlessly. Granted, they already have a fetch implementation you can use on both sides – just not in tests *shakes fists violently*

1

u/IceSentry Jan 30 '22

You can close the gap, but nodejs is still a backend only runtime so asking explanation because they aren't frontend devs is showing a fundamental misunderstanding of a very common tech stack.

1

u/4dk5f5g Jan 30 '22

I read his comment more as "fetch looks to be a frontend thing, can you explain what it is as i do backend." So his question seems reasonable to me.

15

u/lenswipe Jan 30 '22

It's pretty bonkers that it doesn't already

4

u/jadbox Jan 30 '22

What Node version would this be slated for?

4

u/kuriboshoe Jan 30 '22

It’s experimental and hidden behind a flag
so I’d imagine it’ll be a couple major versions before it’s enabled by default

18

u/theunixman Jan 30 '22

Stop trying to make fetch happen, Gretchen.

17

u/campbellm Jan 29 '22

Do people not use axios?

18

u/Ratstail91 Jan 29 '22

I use node-fetch.

9

u/Somepotato Jan 30 '22

Its move to modules makes using it with TS a huge pain with other requirables

7

u/infecthead Jan 30 '22

Yea lol if you look at the version downloads on npm over 90% of people are still using v2, they absolutely fucked it

2

u/mailto_devnull Jan 30 '22

Use 2.x?

8

u/Somepotato Jan 30 '22

I do, but shouldn't have to.

5

u/Kissaki0 Jan 30 '22

The fetch API is a standard. Axios is a library.

Even if they are functionally equivalent, I would rather use a natively supported standard than introduce usage of a third party library - which even if used broadly is not necessarily ecosystem consensus either.

2

u/Nefari0uss Jan 30 '22

I see no reason to use Axios when fetch works perfectly fine.

7

u/kz393 Jan 29 '22

Because you need to use an external package.

One thing that prevents me from using Node for scripting instead of Python is the fact that I have to use the notoriously slow NPM.

15

u/[deleted] Jan 29 '22

I don't think python either have easy to use / fetch api like interface for HTTP requests. Anyways I hate and use both languages. I saw that usually something like requests or other libraries used with python

9

u/caagr98 Jan 30 '22

Python does have urllib.request, but it sees little use these days. Most people use Requests or httpx.

1

u/jl2352 Jan 30 '22

Is the speed of NPM really a problem to prevent you using the Node at all? If it is, why not use Yarn, which for various reasons is much faster?

1

u/_Pho_ Jan 30 '22

If I don’t have to. I don’t use it for front end, fex

1

u/derraidor Jan 30 '22

axios and its ilk don't support http2/alpn on node. Axiso in the browser also relies on XHR, so hopefully with this implementation they can align towards fetch everywhere.

-5

u/[deleted] Jan 29 '22

I've used axios for an experimental project, but I've never used it for anything since and definitely not in production. I don't use JavaScript as a backend language though, if that makes a difference

13

u/campbellm Jan 29 '22

Last company I was in used it for production. Found no issues with it, and easier (IMO) than the (again, IMO) bizarre double-Promise fetch API. People like different things though.

21

u/samjmckenzie Jan 29 '22 edited Jan 30 '22

It's not bizarre, it's logical. When the response is ready (first await), the headers are available to you. Then, in most cases, you're going to want the body, at which point you use the second await to wait for the body to be read. So it's more logical in the sense that it maps better with the way the HTTP protocol actually works. And of course, the fact that it uses modern interfaces such as ReadableStream make it nicer to work with and manipulate or read data in a more logical and efficient manner.

Unless you needs backwards compatibility, there is no reason to be using a package like axios. You will be sending unnecessary bytes to the client and including a package that has a great modern substitute built-in to the browser.

2

u/[deleted] Jan 29 '22

Why is a non-blocking API bizarre?

11

u/ClassicPart Jan 29 '22

They may be referring to the fact that the methods to consume a body from a Fetch response themselves return Promises, leading to oddities such as const x = await (await fetch(..)).json()); or const x = await fetch(...).then(x => x.json())

It makes sense that consuming the response body returns a Promise, but it does lead to that odd call chain.

15

u/[deleted] Jan 29 '22

Right, but the alternative is blocking until the entire response body has been received, which is far more bizarre in an asynchronous API.

3

u/jl2352 Jan 30 '22

Right, but the alternative is blocking until the entire response body has been received, which is far more bizarre in an asynchronous API.

In practice when people use fetch, they will want the full body of the request before they do anything else.

This leads to code like ...

const response = await fetch('http://example.com')
const responseBody = await response.json()

... where the body is waiting until the body is fully available. The second await brings very little to the table. The only saving is that the JSON.parse is done asynchronously, and browsers can do this pretty quickly already.

Combining these into a single await doesn't stop this being asynchronous. However I don't think it really matters. The difference is pretty minor.

4

u/[deleted] Jan 30 '22

The difference is pretty significant if you take streaming use cases into account. Needlessly buffering the entire response makes that impossible.

-2

u/campbellm Jan 30 '22

It's not the promise, it's the 2 of them. Maybe there are use cases, and maybe they are many and I've just not had them, but I have never once needed to make a request and just get the headers and not the body, so having to .then() twice just is weird.

But that's me, reasonable people can disagree.

9

u/ultimatewhipoflove Jan 30 '22

There are absolutely use cases for it though, you can get rate limiting info from the headers depending on the api. If you know you need to make another api call after that you can use this info to throttle before you attempt your next api call.

Another example would be pagination, pagination data is often in the headers so reading the headers, lets you extract the pagination info without needing for the body to come back first.

0

u/[deleted] Jan 29 '22

[deleted]

21

u/campbellm Jan 29 '22

Plenty of places where axios doesn’t work as universally as it advertises.

Curious what it doesn't do that it says it does. Never ran into any issues with it but I'm not a heavy, nor lots of edge-case, user.

1

u/moash_storm_blessed Jan 30 '22

Service workers only have fetch API support.

0

u/[deleted] Jan 29 '22

[deleted]

6

u/davvblack Jan 29 '22

it kinda sounds like the edge runtime isn't really node, it's just node-like.

2

u/[deleted] Jan 30 '22 edited Jan 30 '22

Isn't fetch a bad abstraction for server-side use? It's made for the Web - it has CORS, service workers, and other Web-specific features.

2

u/stronghup Jan 30 '22 edited Jan 30 '22

This is great news. After this on top of my wish-list for Node.js is some kind of simplified DOM-facade. I would like to develop browser applications on Node.js. It would be simply simpler to have a single development environment for both server-side and the GUI. Why because after all browser is the only way to write a GUI for a Node.js program.

There is such a thing as "server-side rendering" of HTML. It would be great if the program that produces such a rendering could also be tested on the server to check that it produces valid HTML and even for the JS-calls embedded into the HTML to work.

7

u/muchbravado Jan 30 '22

Ugh stop trying to make fetch happen

3

u/AIDS-RAT Jan 30 '22

laughs in Deno

-3

u/duckducklo Jan 30 '22

Fellow Deno enjoyer

1

u/ceoro9 Jan 30 '22

finally, it's there. Bye bye axios and node-fetch

1

u/mr_garbaggio Jan 30 '22

Great, just what I needed... 8 years ago

1

u/morefoodmore Jan 30 '22

about time

1

u/audion00ba Jan 30 '22

So sad to see so many people care about technology from 1970.

1

u/[deleted] Jan 30 '22

Wow. node.js really is the platform of the future. What will they think of next?

1

u/gellesa Jan 30 '22

About goddamn time!

-5

u/codysnider Jan 29 '22

Laughs in Go

8

u/argv_minus_one Jan 30 '22

Laughs in pretty much any other language including browser JavaScript

But not including C. Everything is hard in C.

0

u/codysnider Jan 30 '22

It's one of those cry-laughs with C.

-3

u/DOOManiac Jan 30 '22

I don’t even know Node.js and I know this is a big deal.

-8

u/Ratstail91 Jan 29 '22

That's so fetch.

0

u/shevy-ruby Jan 30 '22

I see lots of fun-messages coming up originating from node again!

People thought left-pad was the king. I bet it will get more exciting in the future in this regard. \o/

-6

u/Kpunk1 Jan 30 '22

stop trying to make ‘fetch’ happen. mean girls.

-5

u/dossy Jan 30 '22

thanks for beating me to it.

-1

u/richardirons Jan 30 '22

Stop trying to make fetch happen.

-4

u/ChemicalRascal Jan 30 '22

Oh shit, we finally made fetch happen?

0

u/[deleted] Jan 29 '22

[deleted]

63

u/[deleted] Jan 29 '22

Still 2020 in my book

42

u/webby_mc_webberson Jan 30 '22

It's been march 2020 for a long time

21

u/unaligned_access Jan 29 '22

In my book it's 2020 too

7

u/TimPrograms Jan 29 '22

Holy shit just this week I've caught myself thinking "this podcast is only 2 years old." Because I know it came out in 2020, 2 years ago. But I was listening to an earlier episode and said "yeah this was when the podcast started 2 years ago... So 2018."

2

u/degaart Jan 30 '22

I'm still stuck in 1996. Guess I'm moving at the speed of light

3

u/skiabay Jan 30 '22

Yeah the versioning got all screwed awhile ago. I think we're at 2020.2 now

1

u/NOPsoMuch Jan 30 '22

2020 part 3

16

u/spook327 Jan 30 '22

March 700th, 2020.

1

u/[deleted] Jan 30 '22

"The day the world died"

0

u/[deleted] Jan 29 '22

[deleted]

18

u/vlakreeh Jan 29 '22

How would this make more vulnerabilities? If anything it'd get rid of many potential vulnerabilities by replacing a portion of the dep tree with an official node component

4

u/TomatoCo Jan 29 '22

"If I bring in more packages to make up for a weak standard library, I open myself to vulnerabilities. Simultaneously, if the standard library expands to make packages obsolete, I'm opening myself to more vulnerabilities."

I feel like there's a name for this paradox or fallacy.

1

u/caagr98 Jan 30 '22

More code means more potential for vulnerabilities, whether builtin or third party. Not much of a paradox.

0

u/[deleted] Jan 29 '22

[deleted]

30

u/Cosmic-Warper Jan 30 '22

this has nothing to do with the post

10

u/scooptyy Jan 30 '22

Lmao this poor company

-46

u/[deleted] Jan 29 '22

[removed] — view removed comment

39

u/KevinCarbonara Jan 29 '22

should of

👀

19

u/falconfetus8 Jan 30 '22

began multiplied

2

u/scooptyy Jan 30 '22

Lmao always one clown

-1

u/joshbuss Jan 30 '22

At least we finally overcame shockwave