One paragraph into the article: > while also marvelling at the witless mansplainers Yeah, let’s make every discussion about gender, shall we? How about no?
51–60 of 74 posts
Re: <input type=“country” />
#52Earlier quoted context omitted.
And what do you do when China shows up and says "We're blocking your download servers unless you take Taiwan out of the `country` input"? Better to not centralize the failure points that political actors can put pressure on for what gets to be a country or not.
Wouldn't that be a choice of the browser implementation, likely derived from the locale not unlike time zones?
Re: <input type=“country” />
#53Stopped reading at "mansplainers".
> maybe I’m just fed up with dudes explaining basic shit to me every time I tweet.
Frankly I think she was in the wrong in this occasion. She offered an idea which has a number of obvious flaws then gets confrontational when people offer counterarguments (ok the terseness tweets don't help but that's a platform problem due to its limited character count).
However I say the above without knowing any past history of abuse she might have had on Twitter.
Re: <input type=“country” />
#54I'm mostly just impressed that HN allows brackets in the title...
Re: <input type=“country” />
#55The trouble of the developer having to create this list themselves is the reason I made http://devdata.io - so you could at least have an easy starting point for all this data that is basically just copy/paste.
Re: <input type=“country” />
#56Just do longitude and latitude. Show a map of the earth and let them drop a pin. There is no reasonable way to get the world to agree on a single list. I doubt you could get browser developers to agree on a single list. For example Apple listing Taiwan in Safari could get Apple kicked out of mainland China. There is simply too much politics here to be tenable.
I know what we should do! A dropdown with every possible latitude and longitude combination.
Re: <input type=“country” />
#57Re: <input type=“country” />
#58Earlier quoted context omitted.
How does this contribute to the discussion?
It was said in the original article, so I'd ask how that quip contributes to their own point beyond inviting this exact conversation. It's a very socially charged statement. Do you also expect people to overlook a quip about gun control laws while explaining how monads work in Haskell, or is that conversation off the table because you embedded it inside another topic?
The comment doesn’t add to the discussion about whether a country field would be useful or how it could be implemented at all.
But anyway did you read the twitter thread? The writer proposed standardizing a common function so everyone wouldn’t have to roll their own.
A number of guys responded with ‘here’s how to roll your own’ as if she wasn’t intelligent enough to do that herself (and completely missing the point of the tweet).
Do you have a better word for that behavior?
It wasn’t an offhand quip like your gun control example, it directly related to the tweet she was talking about.
And yes, I would think most people could read an article without freaking out that the two words ‘gun control’ were in there if they were off topic.
It seems sad to me that seeing one word in an article is enough to derail the entire conversation because some people don’t like it. It’s not like it was a call to violence or something like that.
Re: <input type=“country” />
#59Earlier quoted context omitted.
And then someone tries to use it for an app where you have to select which national football you play for.
Or anything involving legal system/jurisdiction or company registration (both of which are differ between countries within the UK). The UK and the Netherlands are both (according to ISO 3166-2 [0]) countries which contain other countries. [0] https://en.wikipedia.org/wiki/ISO_3166-2
The Kingdom of the Netherlands contains four countries, being The Netherlands, Aruba, Curaçao, and Sint Maarten. According to ISO 3166-2, there exists a country "The Netherlands" which contains the other three. Close, but not correct.