21 comments

[ 11.7 ms ] story [ 576 ms ] thread
Why name something that involves code "Grasshopper" when there's been a popular product for 15 years called Grasshopper? [0]

It seems like some people just don't bother to do a basic search to see if their new product name is going to add confusion.

[0] https://en.wikipedia.org/wiki/Grasshopper_3D

Well, it is based on Locust so there's at least some rhyme or reason to the name.
The field it is used is very different. So why not?
Because it makes searching for info online much more complicated than it needs to be. Take Ubuntu Unity for instance, Unity is one of the most popular game engines out there and it also happens to run on Linux. When you do a search for Unity + Linux you get results for both things and it takes extra time sorting out the search results.
"Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting."

https://news.ycombinator.com/newsguidelines.html

I missed that in the guidelines. Good to know.
It's a relatively recent addition... sometime in the last 3 years I think :)

Edit: June 2020. Pretty close guess!

Edit 2: ah, but the bit about name collisions wasn't added until Dec 2021.

(comment deleted)
This seems like a bad rule. A lot of time gets wasted fixing trademark & branding collisions, fixing format incompatibilities, and fixing UX dark patterns that confuse users. People should be thinking about these issues, especially people building brands around their projects.
People are thinking about the issue, but HN has decided that it’s not the place to discuss it.

It’s like the anti politics rule. Politics is absolutely important but there are other forums to discuss it in.

HN isn't the comment section or feedback mechanism for 99% of the stories posted here; in fact, a large percentage of stories posted on HN are here without the knowledge of the author. So in addition to the fact that threads about presentation issues are attractive nuisances --- low-specificity issues that generate opinions from large numbers of HN commenters, often unlike (and competing with) the high-specificity topics of the stories themselves that we're actually here to discuss --- there's almost never any point to them. The original story authors aren't taking our feedback. We're just yelling at the clouds and making things worse for ourselves.
We use locust at work but I HIGHLY recommend wrk for a very robust yet simple load testing tool.

https://github.com/wg/wrk

And of course, this talk by Gil Tene is fantastic if you're interested in load testing stats https://www.youtube.com/watch?v=lJ8ydIuPFeU

Is there a well established python stack for load testing and profiling? Like, I would like to load test a python web application, then use some analysis tool to understand what part of the stack is eating the CPU cycles and/or RAM.
I love locust.io and looking at the features that this adds, I look forward to adding it to my toolbox.