With time-dilation, from the point of view of those on board, it's actually possible to travel as far as Andromeda with constant 1g acceleration (decelerating at 1g half way), within a few decades. Of course, time back on earth would have gone by a few million years...
I'll quote the relevant bit, "Imagine for a moment that you are a happy little photon created by a star in another galaxy some 4 billion light years away. From my perspective here on Earth, it took you exactly 4 billion years to travel from that star till you reached my retina. From your perspective, one instant you were created and then the next, you are are bouncing off or being absorbed by my eyeball. You experienced no passage of time. Your birth and death happened instantaneously.
This is because time slows for you as your get closer to light speed, and at it, it completely stops. This is also another reason why nothing can go faster than light. It would be like slowing down a car to a stop, and then trying to go slower than completely stopped."
It's super interesting that the speed of light is exactly 282,xyz (can't remember) miles per second. What're the chances? I'm just unable to comprehend the idea that a fundamental universal constant could be an exact whole number amount of an arbitrary measurement unit like that. You'd think there'd be a few decimal points or something.
I lived and worked in Sydney for a year or so, and used iiNet while I was there. They had a mirror of free software, and also zero-rated most iTunes content. With most ISPs there having caps (mine was just 100GB), it was difficult to not see this as a benefit, but overall of course it's far from ideal.
The other problem was just terrible speeds; best I could get in a central district was ADSL2+, with about 16/0.8 mbit d/u, and that's not including the terrible latency issue you had to deal with for a whole host of US and EU based websites and services.
Then again, I'm back in London now with a 150/15 mbit d/u connection for under £30, no caps in sight.
The idea of legal tender not being recognised reminds me of a situation here in the UK.
The Bank of Scotland prints its own notes, but are rarely in circulation in the rest of the UK. Somehow it's mildly amusing passing over a Scottish fiver to an unsuspecting checkout assistant in London, and the ensuing suspicion.
When talking about AOT compilation, we generally tend to mean that the compiler produces a binary consisting of machine code at some unspecified time before the user attempts to run the application.
In the context of that blog post, there are two compilation steps: First emscripten would be used to produce JS. Then Mozilla's JS engine would compile that JS down to machine code at runtime.
They call the latter step with OdinMonkey AOT when they compile the entire thing at runtime, but before starting execution. But the way most people differentiate, this would still be considered JIT - it still depends on executing the compiler each time the application is started.
I'm not sure how you claim to be the authority on 'CS speak', but it's a sufficiently blurred line here, for reasons I clearly explained and which you seem unable to understand.
Ahead of time compilation is used to describe the process of generating machine code at compilation time, in a form that can be executed directly by a processor without any additional transformation process.
Actually, there is another open source project in the world that does that. It's called fontpath, I believe, and it reads OTF files directly. I'm considering switching to it, as the HTML5 Text API isn't hardware accelerated and a huge amount of the processing time is being spent in the fillText method.
ah so your the one fumbling with a credit card and holding every one up at the bar when I want to get a round in.
Personally I like having access to cash reduces the attack surface for me when compared to handing over my card for every transaction and DONT! get me started on NFC credit cards that can be debited with NO interactinon
It's a risk, but you can fix it on the backend, away from the end-user. If they were bitcoins then sure you need interaction for NFC. But credit cards are a closed system on the merchant side, any new identity pulling only NFC traffic would be very suspicious. NFC would always be an expected proportion of overall captures. So it's simple to defend against this attack without killing the feature.