You just link to a basic example that uses CORS at some point, then a link to the MDN docs on CORS. If by educational, you mean I get to read that, then I guess?
I far prefer OP's article here, since it walks through why the various CORS headers are needed, and the results of each stage.
No need to be a jerk about it.
haha! how about your write your own post on #CORS rather than keep on piling up here ...
I provided context for CORS in action on one of the frequently used online sites for devs & data scientists, with a brief example any dev can try on Observable HQ || glitch.
If you'd rather read long CORS specs recaps & clone a github repo with that simple nodeJS index.js example, I'll leave it up to you.
I don't get why you think you're being "piled up on". You started by insulting the article on Twitter, then linking that tweet here, effectively insulting it again.
You aren't the victim, you're being called out for being a jerk.
My advice is to look closely at what you did, apologize and do better going forward.
Kevin, go write your ideal post on CORS. You could use 1 :)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.