528 karma · joined April 29, 2014
In portrait mode, the text scrolls off the side of the screen so I have to continually pan back and forth to read an article. In landscape mode, a very thin column of text is used. It's as if the landscape res media query is being applied to portrait view and vice versa.
Edit - oh hmm looks like manually zooming out a bit in portrait will fit the whole article. Was sure that didn't used to be the case in earlier days. Maybe it got fixed!
Square Cash is not available in the UK for example. The US has a much larger choice. Unsure about other countries, sorry.
You would know this isn't "fake news" if you spent the time it took to write your post to visit the link instead.
Clearly a great opening line. If you write an open letter, try not sounding terrible in your letter.
But why do we have to play this game again?
Why haven't we learnt from previous mistakes?
I mean what do you expect? It's facebook. It was founded on dubious merit, the company will operate in the most grey it possibly can.
(Not wanting to anger the tech nerds here: various FB employees have released super interesting stuff back into the tech community such as the recent SSH CA auth article)
But c'mon. When you see anyone accused of foul play, facebook should be the least surprising of them all.
But if you want to link a colony on Mars to Earth's internet, you'll need something like this 'store and forward' style networking, rather than trying to rely on interactive two-way realtime-ish communication.
I assume there's plenty of scope for ES6 to improve and (hopefully?) surpass ES5 in performance in many, if not all, areas?
What would be causing the large slowdowns in ES6 here? Is this a case of having features that make JS nicer to code in, but giving up some performance? Or is this more down to immature compilers not yet optimising ES6 as substantially?