Live data from Hacker News

shkspr.mobi

41–50 of 74 posts

Re: <input type=“country” />

#41
post #6

Just 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.

This is roughly why the Linux timezone picker refers to cities instead of countries.

Re: <input type=“country” />

#42

Stopped reading at "mansplainers".

Yeah, I even read the Twitter thread looking for it.

Sorry to say, but everyone on the internet loves correcting each other and taking the most uncharitable interpretation of each other's posts.

Look no further than HN.

That they use "she" instead of "he" is actually a credit to the replying users insofar that they actually tried to get the gender correct before they launched into the usual assumption that everyone else on the internet is an idiot.

Re: <input type=“country” />

#44
post #15

Earlier quoted context omitted.

An input list of all current passport issuing countries would be useful. The Scotland problem doesn't arise as they don't issue passports (the UK does).

what about taiwan? what about taiwan if you're in china...?

According to https://en.wikipedia.org/wiki/Taiwan_passport , the issuing country code is:

TWN, the ISO country code for Republic of China, listed as "Taiwan, Province of China" in ISO 3166-1

Re: <input type=“country” />

#45
Regarding the place of birth issue, I have never used the country I was born with when some form asked for birthplace. Always used the present state, i.e. in what country is the place I was born at.

Is that not common? Would you expect someone to write down GDR, USSR, or even Constantinople? Or is it again the same issue that people want to use what they like?

Re: <input type=“country” />

#46
There was an excellent article[0] in Smashing Magazine several years ago that dealt with some of the complexities of country selectors.

For someone who lives in the UK, you never know whether a list will have United Kingdom, Great Britain or England in it (I've come across all three), and similar problems exist for countries that are known by more than one name (eg Netherlands vs Holland).

And some sites break sorting by pushing certain countries to the top of the list and breaking sorting completely.

There isn't a completely right answer, a standardised country selector might work in some (most) circumstances for most people, but what if my list needs Czechoslovakia or Zaïre? Then, a "simple" problem becomes much, much, much more complex.

[0] https://www.smashingmagazine.com/2011/11/redesigning-the-cou...

Re: <input type=“country” />

#47
post #2

I have my doubts as to whether a generic solution solves this. The author notes some issues, like using it for place of birth. Now you need a temporal list for "countries that existed in year XYZ". There are similar issues for shipping. Not everyone ships everywhere. If the list is abstract and unknown to me, how do I whitelist/blacklist? Am I supposed to know that Scotland exists in the list or not? What if it's for…

For shipping too, not just that every shipper ships to every country, but that shippers ship to different countries unequally: costs associated change or they only ship below certain weights or they require three dozen more customs forms to be signed (each in triplicate). Many of the shippers have rather complex APIs for that (give me the country list and shipping cost for this assumed package weight range), how would you try to replicate that in the browser?

Re: <input type=“country” />

#48
post #40

Stopped reading at "mansplainers".

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?

Re: <input type=“country” />

#49
post #24
post #2

I have my doubts as to whether a generic solution solves this. The author notes some issues, like using it for place of birth. Now you need a temporal list for "countries that existed in year XYZ". There are similar issues for shipping. Not everyone ships everywhere. If the list is abstract and unknown to me, how do I whitelist/blacklist? Am I supposed to know that Scotland exists in the list or not? What if it's for…

Someone on twitter suggested using the OS' own list of countries, working around the problem of the standard having to define what is/isn't a country. I think that's a reasonable solution.

Windows dropped having a list of countries in the 9x era because there were too many international issues and disputes. It's also why they dropped even trying to draw the shapes of time zones because that too was causing international border complaints.

Re: <input type=“country” />

#50
Nice idea, but she outlined more than enough reasons not to do it. Political (Israel-Palestine, China-Taiwan, Ukraine, etc).

In my limited experience with automating international shipping I seem to recall UPS treats Guam, Puerto Rico, and US Virgin islands as countries (and our local CRM treated them as states).

There are so many controls that HTML is missing - date pickers, menus, menu flyouts etc.

Post reply on HN