I'm surprised it's still being used (and a mod fixed the link now), but if you're curious, here's the discussion on 9m.no from 15 months ago: https://news.ycombinator.com/item?id=7783239 :)
I simply tried (and failed, it seems) to say that they are generally considered to be equivalent, and that it's okay to use “aa” when translating a name with “å”. Reasons for this could be not knowing how to write an ‘å’ (or Ł, đ, ç, ì, etc.) or simply not wanting to distract one's readers. I do not have an authoritative source.
It's acceptable (or at least “not wrong”) to use “aa” for å (and “oe” for ø/ö, “ae” for æ/ä).
While ‘å’ was made an official letter in Norwegian in 1917, it's still common to see “aa” spellings of names, and “aa” and “å” spellings are considered equivalent (fun when sorting, since ‘å’ is the last letter of the Norwegian alphabet).
An iOS device will only connect to known networks. By enabling “Ask to Join Networks” it will list networks and ask if you want to join any of them – but only if no known network is in range. This is actually less safe, in that you're just a button press away from “accessing random open networks” instead of having to go into the settings and choose a network – so it makes sense to have it default to off.
tl;rl: iOS will only join known networks – toggling this setting will make it easier to join networks when no known networks are in range.
… and advice/advise and prophecy/prophesy. For some reason, only the latter has kept the difference in spelling between the noun and the verb in American English.
> The advantage of this approach would be allowing function overloading (similarly to C++ or Java) informally without interfaces or type classes.
I might be misunderstanding something, but how does this allow function overloading more than ordinary let-polymorphism? Functions can already have a type like, say, ∀a.a→Int. It's also quite common to do type inference in two steps where the first pass creates type variables and a list of constraints. The set of constraints are then passed to a unification algorithm, see e.g. http://www.seas.upenn.edu/~cis552/lectures/stub/FunTypes.htm....
I had briefly used Scotty before, but never acid-state. All of this is just the result of a discussion at work where my position was “oh, come on! it's not that stupid!”, so I just chose something I though would let me get a test site up and running really quickly.
I would probably polish it a bit more if I knew it would get this much attention, but hey! – it works, and uses almost no resources on the cheapest Digital Ocean account.
Can anyone recommend an iPhone app for viewing maps and getting directions? The OSM wiki lists a lot of apps [1], but they seem to be of varying quality. I'd love to be able to use something that's close in functionality and simplicity of the Google Maps app.
The top comment has an interesting suggestion for why this is done:
[…] this is how people in local governments make money in Russia:
Step 1: have a $100,000 of tax money budget for fixing the pavement on street XYZ
Step 2: pay your nephew's 'construction company' $10,000 for the 'work' they did
Step 3: pocket $90,000 of tax money
Step 4: oh noes!! the road cracked AGAIN! not AGAIN!! oh well, guess gotta go fix it
Step 5: goto Step 1 Today 1:36am