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

OpenAI's response to the Axios developer tool compromise

openai.com

Post reply on HN
Print view View original

11–20 of 68 posts

Re: OpenAI's response to the Axios developer tool compromise

#11

Post by internetter »

danpalmer wrote: post #7
danscan wrote: post #4

Axios, like Express, is something I'm shocked to see used in any modern codebase. I loved both in the 2010s. In JS/TS-land there are much simpler and better options these days. Depending on Axios suggests the devs don't know how to use fetch. I can't think of another reason it would be a necessary dependency

If you want a fully built out network layer, with auth, logging, monitoring, policies, etc, then `fetch` doesn't really help. Axios and other libraries provide much more for building that sort of framework.

Any sufficiently competent typescript developer can build out an adhoc wrapper (that just inherits the type definition and passes along whatever it is passed after altering it however needed) in under a hour. It doesn't scale in the sense that you don't expose a configuration, but config as code is king.

(Source: have built out much more scuffed variants of this than the one I just described like https://github.com/boehs/ajar)

I guess a LLM can do as well. Although that's not something I'm quite ready to admit.

Re: OpenAI's response to the Axios developer tool compromise

#12

Post by internetter »

chvid wrote: post #10
danscan wrote: post #4

Axios, like Express, is something I'm shocked to see used in any modern codebase. I loved both in the 2010s. In JS/TS-land there are much simpler and better options these days. Depending on Axios suggests the devs don't know how to use fetch. I can't think of another reason it would be a necessary dependency

ChatGPT in general recommends axios over fetch. (At least it did about 2 months ago)

This is why people still need to know how to write code and why it is asinine to have an LLM write code without a human reading it. Good developers should know what good code looks like and push back when what they're fed is wrong.

Re: OpenAI's response to the Axios developer tool compromise

#13

Post by tommy_axle »

danscan wrote: post #4

Axios, like Express, is something I'm shocked to see used in any modern codebase. I loved both in the 2010s. In JS/TS-land there are much simpler and better options these days. Depending on Axios suggests the devs don't know how to use fetch. I can't think of another reason it would be a necessary dependency

I wouldn't go that far. Right tool for the job as always. Axios offers a lot over fetch for all but the simplest use cases plus you get to take advantage of the ecosystem. Need offline, axios-cache-interceptor already exists. Sure you can do all of those things with fetch but you need more to go with it taking you right back to just using axios. Also is no one annoyed that you can't replay fetch like the xhr? Same with express: solves a problem reliably.

Re: OpenAI's response to the Axios developer tool compromise

#14

Post by whattheheckheck »

internetter wrote: post #11
danpalmer wrote: post #7

Earlier quoted context omitted.

If you want a fully built out network layer, with auth, logging, monitoring, policies, etc, then `fetch` doesn't really help. Axios and other libraries provide much more for building that sort of framework.

Any sufficiently competent typescript developer can build out an adhoc wrapper (that just inherits the type definition and passes along whatever it is passed after altering it however needed) in under a hour. It doesn't scale in the sense that you don't expose a configuration, but config as code is king. (Source: have built out much more scuffed variants of this than the one I just described like https://github.com/b…

Keep developing it. Your taste and judgement matter

Re: OpenAI's response to the Axios developer tool compromise

#15

Post by ariwilson »

danscan wrote: post #4

Axios, like Express, is something I'm shocked to see used in any modern codebase. I loved both in the 2010s. In JS/TS-land there are much simpler and better options these days. Depending on Axios suggests the devs don't know how to use fetch. I can't think of another reason it would be a necessary dependency

What's wrong with Express?

Re: OpenAI's response to the Axios developer tool compromise

#16

Post by internetter »

ariwilson wrote: post #15
danscan wrote: post #4

Axios, like Express, is something I'm shocked to see used in any modern codebase. I loved both in the 2010s. In JS/TS-land there are much simpler and better options these days. Depending on Axios suggests the devs don't know how to use fetch. I can't think of another reason it would be a necessary dependency

What's wrong with Express?

Just slow and convoluted internals due to the accumulation of cruft over time

Re: OpenAI's response to the Axios developer tool compromise

#17

Post by 8n4vidtmkvmk »

internetter wrote: post #11
danpalmer wrote: post #7

Earlier quoted context omitted.

If you want a fully built out network layer, with auth, logging, monitoring, policies, etc, then `fetch` doesn't really help. Axios and other libraries provide much more for building that sort of framework.

Any sufficiently competent typescript developer can build out an adhoc wrapper (that just inherits the type definition and passes along whatever it is passed after altering it however needed) in under a hour. It doesn't scale in the sense that you don't expose a configuration, but config as code is king. (Source: have built out much more scuffed variants of this than the one I just described like https://github.com/b…

I've wrapped fetch a few times but i don't think I'd blame someone if they got tired of wrapping it and wanted a consistent interface across all the projects they work on.

Re: OpenAI's response to the Axios developer tool compromise

#18

Post by koolba »

danscan wrote: post #4

Axios, like Express, is something I'm shocked to see used in any modern codebase. I loved both in the 2010s. In JS/TS-land there are much simpler and better options these days. Depending on Axios suggests the devs don't know how to use fetch. I can't think of another reason it would be a necessary dependency

What’s wrong with express?

Re: OpenAI's response to the Axios developer tool compromise

#19

Post by seanp2k2 »

danscan wrote: post #4

Axios, like Express, is something I'm shocked to see used in any modern codebase. I loved both in the 2010s. In JS/TS-land there are much simpler and better options these days. Depending on Axios suggests the devs don't know how to use fetch. I can't think of another reason it would be a necessary dependency

jQuery is still useful too. May you never work in heathcare / government / defense where you need to support legacy browsers far past their expiration date.

Re: OpenAI's response to the Axios developer tool compromise

#20

Post by rozenmd »

ariwilson wrote: post #15
danscan wrote: post #4

Axios, like Express, is something I'm shocked to see used in any modern codebase. I loved both in the 2010s. In JS/TS-land there are much simpler and better options these days. Depending on Axios suggests the devs don't know how to use fetch. I can't think of another reason it would be a necessary dependency

What's wrong with Express?

Several newer alternatives that outperform it on Node, like Hono
Post reply on HN