Comment by antisol | Hacker News Reader

Comment by antisol | Hacker News Reader

Parent Full thread

It seems someone hasn't been very thorough in their investigation.

Actually, this user has been posting in this thread for months - the earliest post I saw was in January. The user posted several times asking for updates as to whether this feature was planned or not, fairly politely it seems to me, and was totally ignored as far as I can see.

After repeatedly asking for updates and having no response whatsoever, it seems they became disillusioned. Which I think isn't unreasonable - it's my opinion that it's pretty rude for a maintainer to ignore reasonable questions put to them, and that it's quite reasonable to be offended when you are ignored in this way. You talk about "aggression", I say ignoring people is an act of aggression, and it seems to me that this user has simply responded in kind.

We could get into a discussion on whether a maintainer has any responsibility to respond to users asking questions, and then use that as a basis for deciding whether specific posts by this user were justified or not, but my point is that the picture you paint with your post is inaccurate and incomplete. At best.

No, I was very thorough: I saw every comment and pulled out the obscene, aggressive, offensive acrostic embedded in months of harassing tagging of the target of that acrostic because that recent pattern of behavior overshadows everything else. There's no excuse for that entry no matter how frustrated they get.

Vercel owes them nothing—and the specific employee OP chose as a target owes them even less—and this entitled behavior is a long-standing plague on open source that needs to be called out and soundly condemned. If they need the feature so desperately they can add it themselves (Vercel already said it's something they want to implement!) or switch frameworks.

This has been a plague for so long it nearly threatened the rails project. It also inspired a very interesting article https://dhh.dk/2012/rails-is-omakase.html about the maintainer that provides a framework of sorts for thinking about issues regarding open source entitlement

Thanks, I hadn't read that before and it's a great piece!

> If most things on the menu disgust you, what on earth are you still doing at the table? The door is right over there, try not to slam it on your way out.

Interesting, thanks for sharing.

...but did you notice how the entire scenario presented in this article is predicated on the person who made their suggestion actually getting a response?

"I'm sorry, but hotdogs don't really fit our sushi menu, and while you may not care for unagi, we picked it for a reason. But thanks for the suggestions!"

Totally reasonable response. Polite. Reasonable explanation. 10/10 response. Totally unreasonable to then start insisting that hot dogs be added.

The example scenario isn't "person asks the waiter for a hot dog; waiter just keeps walking past them, blanking them as if they don't even exist".

I would be curious to know why OP chose to post this today, 3 weeks after they said they were working on it. That's an interesting detail.

> The example scenario isn't "person asks the waiter for a hot dog; waiter just keeps walking past them, blanking them as if they don't even exist".

First: that scenario is actually still just fine when the establishment is a soup kitchen. When the people providing the service are providing it for free funded entirely out of their own pocket then no user of the free service is entitled to anything, ever.

Second: that isn't an accurate description of what happened, as you should know because you read the thread in full. What actually happened is that a maintainer responded to the issue back in January with a soft timeline. OP began harassing that maintainer less than halfway through the provided timeline.

When they got ignored for just over a week (which is, again, entirely reasonable especially given that a timeline was already offered) OP proceeded to write not one but three "FUCKUJimmy" acrostics further harassing the maintainer who had provided the initial timeline.

Then, on May 9, which is well within the initial estimate, the maintainer provided an update saying that the timeline had to be pushed back. OP's reaction to that was to try to bring the project hate on HN.

In what universe is any of this behavior by OP acceptable?

> a maintainer responded to the issue back in January with a soft timeline

It seems I missed that comment (https://github.com/vercel/next.js/discussions/64660#discussi...).

My apologies. There were a lot of comments.

I stand corrected, withdraw my support of OP's behaviour, and agree that it's not acceptable.

---

> no user of the service is entitled to anything, ever.

I say everyone is entitled to basic human decency and acknowledgement of their existence. I say that the waiter walking past and blanking them is rude and a dick move, and not "totally fine" at all. While you are correct that the user isn't entitled to the 10/10 polite response/explanation given in the article, they are entitled to some sort of basic human decency. The waiter blanking them and the waiter responding by calling them a cunt with no provocation are both aggression.

I also say that the "soup kitchen" analogy you gave doesn't really hold here - didn't you refer to that maintainer as "an employee"? So it's that person's job to respond to issues. Which entitles people asking them questions to a response. (Which, as I concede above, he did actually get)

But now we're debating philososophy, which I specifically didn't want to do. And I've conceded that in this instance your position on OP's behaviour is correct.

The reason is that I don't think it's a technical issue — in other words, it's the managers, not the engineers, who decide the priority here. Therefore, the right place to try to expedite this is somewhere more influential, like HN or Twitter, not GitHub.

I can anticipate that this won't be resolved for at least 3 months. Just be aware this issue has been around for over 2 years, and the last time someone promised to fix it was 6 months ago. Let's see.

If you want to expedite development of the feature that you want, you could always a) do it yourself or b) pay someone else to.

There might be other people who are also interested in this feature who would also be willing to chip in to a bounty. You might consider a platform like https://algora.io/bounties or https://bountyboard.dev/bounties :)

Reply on news.ycombinator.com