6 ms·

If you don't already know what CORS is, you're probably not a Web developer and don't need to know.

Waterluvian 5y ago
I think this is misguided reasoning. Everyone starts somewhere, and the hallmark of reasonably competent writing is a ramp-up. Whether it’s one sentence or one chapter. I think failing to define acronyms is a violation of just about any style guide out there. Communication is a majority of engineering so I think these things are very important.
hsbauauvhabzb 5y ago
To be fair, there are many web devs who have never needed to worry about cross origin resource sharing
- soniczentropy 5y ago
  How do you become one of those kind instead of smashing your face against CORS constantly
  - adminscoffee 5y ago
    i think the purpose of cors is to slowly make web devs go insane. but yeah, more coors less cors
  - hsbauauvhabzb 5y ago
    Legacy developers would be the biggest group.
- 5e92cb50239222b 5y ago
  Usually the same ones who then download plugins like https://addons.mozilla.org/en-US/firefox/addon/access-control-allow-origin/ https://addons.mozilla.org/en-US/firefox/addon/access-contro... because properly configuring the backend is ¨too complicated¨. Been there, done that.
  - hsbauauvhabzb 5y ago
    You can use the origin announce headers from Firefox to block cors also, unsure if that works with chrome. But I was referring to legacy code (or those whose SPA is stored on the same domain as API endpoints).
nuerow 5y ago
> If you don't already know what CORS is, you're probably not a Web developer and don't need to know. This is an appallingly poor and misguided take, and goes against the most basic rules of writing technical documents. Docs need to be clear, unambiguous, and self-contained. The very first time a acronym is presented, it must be after the full name is presented. It takes less than a sentence to do the right thing. There is no excuse.
mrweasel 5y ago
Sometimes OPS people get the job of fixing CORS for developers who don't understand how it works exactly. I work with a client who built a web app in... Vue, I think. For unknown reasons they decided that it would be better that the APIs they need to call to live on the same domain. At the same time, the developers decided that the API microservices should not return CORS headers. Instead it was left to operations to hack in CORS headers in the webserver/loadbalancer.

I think this is misguided reasoning. Everyone starts somewhere, and the hallmark of reasonably competent writing is a ramp-up. Whether it’s one sentence or one chapter. I think failing to define acronyms is a violation of just about any style guide out there. Communication is a majority of engineering so I think these things are very important.

hsbauauvhabzb 5y ago

To be fair, there are many web devs who have never needed to worry about cross origin resource sharing

soniczentropy 5y ago
How do you become one of those kind instead of smashing your face against CORS constantly
- adminscoffee 5y ago
  i think the purpose of cors is to slowly make web devs go insane. but yeah, more coors less cors
- hsbauauvhabzb 5y ago
  Legacy developers would be the biggest group.
5e92cb50239222b 5y ago
Usually the same ones who then download plugins like https://addons.mozilla.org/en-US/firefox/addon/access-control-allow-origin/ https://addons.mozilla.org/en-US/firefox/addon/access-contro... because properly configuring the backend is ¨too complicated¨. Been there, done that.
- hsbauauvhabzb 5y ago
  You can use the origin announce headers from Firefox to block cors also, unsure if that works with chrome. But I was referring to legacy code (or those whose SPA is stored on the same domain as API endpoints).

nuerow 5y ago

> If you don't already know what CORS is, you're probably not a Web developer and don't need to know. This is an appallingly poor and misguided take, and goes against the most basic rules of writing technical documents. Docs need to be clear, unambiguous, and self-contained. The very first time a acronym is presented, it must be after the full name is presented. It takes less than a sentence to do the right thing. There is no excuse.

mrweasel 5y ago

Sometimes OPS people get the job of fixing CORS for developers who don't understand how it works exactly. I work with a client who built a web app in... Vue, I think. For unknown reasons they decided that it would be better that the APIs they need to call to live on the same domain. At the same time, the developers decided that the API microservices should not return CORS headers. Instead it was left to operations to hack in CORS headers in the webserver/loadbalancer.