4 ms·
The title of this has Tailwind alternative in it. At this point around 100% of the comments are about the comparison to tailwind. However, open-props never men
by projectramo 4y ago
The title of this has Tailwind alternative in it. At this point around 100% of the comments are about the comparison to tailwind.
However, open-props never mentions tailwind. That simple mis-title has hijacked the convo.
- nindalf 4y agodang, please re-title this.
- oefrha 4y agoPosting "dang, please re-title this" doesn't do anything, you should email hn@ycombinator.com instead, as I just did. Dan or some other behind-the-scenes mod usually handle these quickly.
- plibither8 4y agoTrue, but also interesting. I'm sure dang and the mod team would have a special filter for comments mentioning "@dang" or something alike. Seems imperative and useful. Edit: ...and if they do, I think I just tagged them unnecessarily. xD
- dang 4y agoDoesn't make sense to retitle it now because the thread is so dominated by the editorialized title. I think we need to leave it. This is why the site guidelines contain the rule: "Please use the original title, unless it is misleading or linkbait; don't editorialize." https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html The [flagged] marker, btw, is because users flagged the submission, which they were correct to do.
- lelandfe 4y agoNor is it from the "Chrome Dev Team." This is just a side project of a Google engineer who is a part of that team[0] https://github.com/argyleink/open-props/graphs/contributors?from=2021-08-29&to=2022-09-13&type=c https://github.com/argyleink/open-props/graphs/contributors?... [0] Also, because it's not murky enough, "Chrome Dev" are the DevRel people (community outreach, web.dev articles, conferences, etc), not the "developers of Chrome." https://twitter.com/ChromiumDev https://twitter.com/ChromiumDev