Nothing. You can plug in four chargers, one in every port, and it will only draw power from one.
466 karma · joined March 24, 2012
[ my public key: https://keybase.io/tvararu; my proof: https://keybase.io/tvararu/sigs/jtl6VBrmo15IcT8bBNeKPwPuwMFmSvnnFgHOwd1VpUk ]
Source: https://whatdoesmysitecost.com/test/161007_QR_78c23294113b6c...
Keynote for iOS also serves as a very reliable and easy to set up presentation remote.
I suggest conducting an experiment: speak to your girlfriend (away from your phones) and establish a list of highly specific subjects/products. Then, bring these subjects up in conversation when near the phone(s). If what you're saying is true, they should start popping up in the Facebook ads.
[1] https://en.wikipedia.org/wiki/30_St_Mary_Axe
As further confirmation, it's cemented as one of the ten design principles behind GOV.UK: https://www.gov.uk/design-principles#tenth
Thank you for all your work!
That is some very unsound advice. I find it worthy of ridicule that it's being suggested as a possibility.
The upgrade path was very necessary to address the huge amount of breaking changes.
Thank you so much for the input, and thanks for helping build something I enjoyed using.
- Good experience, fairly regular releases, stability increasing with each one.
- Stagnation in releases, but app is in a fairly good working state.
- Out of the blue, big update comes in, application changes completely. For the worse, as it loses a bunch of features and is sporting a far less polished look and finish. I believe the new version is now an OS X native application as opposed to a webview.
- Frantic releases over the following weeks, killing some bugs but introducing more.
- Stagnation in releases, in its fairly broken state.
- This announcement.
From the outside, it looks like a case of an engineering team that decided it would rewrite the application from scratch in the native stack. Widely regarded as a bad idea. [1]
After numerous months spent burning money in refactoring and rebuilding features that already existed and worked, management pressure builds up, and they decide to release their "good enough" native version. After torturous weeks of back to back frantic releases to fix all of the complaints coming in, some factor or another (developer churn possibly) caused them to cease development and decide to sack the project altogether.
This is of course just speculation, a narrative I made up. That's how it looks like from the outside to me, but I'd like to hear from the developers inside, since I know they must be reading this thread.
I loved this application and I'm saddened to have to move away from it.
This is similar to the way that https://rubymonk.com/ for example shows you how to do `2.even?` but doesn't show you the equivalent method for checking if a number is odd.
Mods give you complete access to accomplish anything with the game world or interface, even morph it into a completely different game.
I'm on the Elm/FRP fence myself but your comment here reeks of turing tarpit:
"Beware of the Turing tar-pit in which everything is possible but nothing of interest is easy."
The tool I used, PhantomCSS, did allow for a threshold underneath which pixel differences would not get picked up, but I opted instead to run my tests locally in vagrant so that the environment would be closer to identical to CI.
So yes, platform noise is just one of the myriad of challenges you have to solve when implementing such tooling.
I'd like to nit here that visual regression test harnesses for web application development do exist. [1] [2] [3] Using something like Sauce Labs you could conceptually have these tests run on Windows machines in the cloud.
However, having implemented visual regression testing in the past in various projects, I can personally vouch that it's a huge waste of time. Your tools will break all the time, your tests will break all the time, and you'll generally have a bad time.
[1] https://github.com/chenglou/node-huxley [2] https://github.com/Huddle/PhantomCSS [3] https://github.com/bradgignac/janus
CSS in JS is about leveraging the (relatively sane) variable/procedure declaration and control flow semantics that are already available to you in JavaScript. How you deliver them to get the best possible performance is a wholly different problem.
[1]: https://github.com/kodyl/stilr [2]: https://github.com/robertknight/ts-style [3]: https://github.com/chenglou/RCSS
Brilliant.
The first device I tried (and apparently the one with the beefiest hardware) was an Alcatel One Touch Fire. My enthusiasm took a sharp turn downward from the moment I unlocked the device; accomplished by sliding the screen left to right, the animation was jerky, did not track my finger accurately, and skipped to the end when I let go of the screen halfway through the width of the screen.
One of the hosts was quick to point out that the lock screen interaction was actually custom programmed by Alcatel, and so is the rest of the user interface, at which point he pointed to try a different device running something closer to "stock Firefox OS."
I'm enthralled by the promise of helping the web win by creating a device category where the web is a first-class citizen, but I'm doubtful it will happen if manufacturers outsource their tasteless UI customizations to web dev interns.
Sunspider came out at roughly 1600ms, which places the mid-2013 Alcatel somewhere in the performance bracket of an iPhone 4 (mid-2010, flagship device). Despite the rough benchmarks, I ran some Famo.us demos and they were surprisingly usable, and I could easily get a physics-backed drag interaction to run smoothly inside the browser.
I'm waiting to try out a Firefox OS phone with cutting edge hardware.
We're already there. You can play, today, on your iPhone and/or Android device: GTA San Andreas, Bioshock and Star Wars Knights of the Old Republic. These are complete ports that spare no features from the originals.
However, I found that the experience is not what I sought it out to be. I realised that these are games that require focus, since they rely on immersion. The only situation in which I can actually sit down to play them for any meaningful amount of time is when I'm at home on a weekend; in which case, why not just use a console or my computer, with vastly superior input devices and display quality?
I see the symbols are just unicode, so you could use some CSS absolute positioning to create the different arrangements.
You don't need JavaScript for that.
div {
animation: seizure 16.6ms infinite alternate;
}
@keyframes seizure {
0% { background: black; }
100% { background: white; }
}