# POST /comments with relationship or POST /articles/33/comments

**URL:** <https://discuss.jsonapi.org/t/post-comments-with-relationship-or-post-articles-33-comments/1020>\
**Category:** Uncategorized\
**Created:** [July 6, 2017, 1:56am UTC](https://discuss.jsonapi.org/t/post-comments-with-relationship-or-post-articles-33-comments/1020 "2017-07-06T01:56:25Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![michaelhibay](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/michaelhibay/32/405_2.png) [@michaelhibay](https://discuss.jsonapi.org/u/michaelhibay)\
**Post date:** [July 28, 2017, 5:32pm UTC](https://discuss.jsonapi.org/t/post-comments-with-relationship-or-post-articles-33-comments/1020/19 "2017-07-28T17:32:34Z")

</div>

There’s no need to carry this discussion in multiple threads. [I responded to the thread you created](http://discuss.jsonapi.org/t/posting-related-data/1054/3), and we can continue there.

> [@derrekbertrand](#):
>
> Until I have a measurably better suggestion, I won’t complain about it anymore. I don’t have numbers to back up any claim that I’d make, and all my complaints would be performance related.
> 
> I’ve been researching alternatives, and if I get around to benchmarking them I’ll post the results in a new thread.

I’d be interested in seeing those results. Despite what they reinforce in college, performance related issues which are outside the bounds of algorithmic complexity are generally best addressed when they show signs of being a problem. I regularly have to fight the urge of premature optimization, so I understand where you are coming from.

---

_[View the full topic](https://discuss.jsonapi.org/t/post-comments-with-relationship-or-post-articles-33-comments/1020)._