I believe this is a Google doc preview. On my iPad it had terrible scrolling performance, and the shortcut to scroll to the top of the page (tap the top edge of the screen) doesn't work :(
https://www.17lands.com/ collects your limited game win/loss stats, and it also records your turn-by-turn game history for both limited and constructed games. (I was a contributor)
If your threat model involves people hijacking your TV to spy on you, and one of these attackers managed to enter your home, you are already toast no matter what.
The "50% faster" stat is talking about latency, which is not really what subsea cables are about (massive bandwidth).
The more important figure is the attenuation at frequency bands used in telecommunication (C-band and L-band). According to the article, hollow core fibers are still much worse than solid core fibers (0.28 dB/km vs 0.14 dB/km).
In every Marvel movie I watched the Helicarrier was shot down before it could do anything useful. I imagine a real life version would suffer the same fate.
Yeah. When I started cooking I read a bunch of articles on theory of cooking, what utensils to use etc, but in the end I realized they are all counterproductive. The first few attempts at cooking are bound to fail, and spending hours and hours on preparation and decision paralysis makes the failures much more disheartening. It's much better to stick to a few simple recipes and just do what they say without questioning why. The analysis / innovation can come later.
Same here. The way the thing wobbles in the video doesn't inspire confidence. Although even if the monitor falls off I don't think it will hurt too badly.
Perhaps counterproductive is too strong a word, but there could definitely be problems in the short term. Programmers love to apply things they learned in their work, and taking a concept or pattern from language A and applying them to language B is a natural reaction. The most common culprits are monads and actors. Ergonomics (readability, cognitive cost, debugging, IDE support, etc) became afterthoughts in the midst of excitement, and the long term health of the codebase (and teammates) suffers.
I have made mistakes like that (introducing monads/future and making the team learn guava) and I still regret it. Its not to say futures are useless - there were a lot of async logic in the codebase and futures solve a real problem, but its not clear if the benefits outweigh the cost.
This kind of sentiment come up every so often on HN and I'm just sick of it. Sure, programmers should strive to improve their craft, just like professionals in every industry. But there are plenty of ways to improve yourself and learning a new language is hardly the most effective choice (and in fact could be counterproductive).
Whether you hire an outside consultant or not doesn’t matter. You have to pay the cost one way or another, either by your employees spending time learning the language + experimenting + making mistakes, or by going through some training and hopefully making less mistakes (not guaranteed).
Honestly this is the most stupid part. And I don't think College Board (or whoever made the site) didn't do any testing -- if that's the case the site should be way more broken. It's probably a problem of setting non-realistic test cases.