It's funny how Microsoft conducted the "tests" on Chrome [1] & Firefox [2] and discreetly leave out Safari. Safari is by far a winner when it comes to efficiency. So hats off to MS for their "informative" & "thorough" test(s).
[1] has been known for draining battery, so no surprises there.
[2] which for a couple of releases has become even more unusable. On my MBP (2014, i5, 8GB), takes over 4+ seconds for the bar to activate. Hopefully with the introduction of E10S [3], next releases will be much more perfomant.
>It's funny how Microsoft conducted the "tests" on Chrome [1] & Firefox [2] and discreetly leave out Safari. Safari is by far a winner when it comes to efficiency. So hats off to MS for their "informative" & "thorough" test(s).
Safari also doesn't run (anymore) on Windows platforms that Microsoft targets, so it's irrelevant to their point.
Safari doesn't run on Windows (anymore, and it wasn't efficient). Edge doesn't run on OS X.
I think it was fair. They showed browsers on Windows. I just wish more people would realize just how bad Chrome is at power efficiency so that Goigle might pretend to care.
Cookies can be/are used for extensive tracking (even when you're not techically on the site). The EU requires websites that use cookies to display conformation message on how cookies will be used to track the user.
The infamous "cookie" law isn't limited to Cookies. JWT, local storage and co all fall under the same law that will force you to put a disclaimer on your webpages. There is absolutely no difference between the 2 in that regard. The fact that you think otherwise is a serious legal risk for your business if you have one.
the EU requires websites that use _any_ kind of local storage to display a conformation message on how the storage will be used to track the user. It is not specific to cookies.
They have a provided a FAQ page about Free Dyno Hour [1]
Previously you get 540 dyno hours (18 hours/day), now it's 550. If you provide a valid credit card, you'll get 1000 dyno hours (you will NOT be charged unless you EXPLICITLY switch to a paid plan)
None in my [Mac]book. If you're running on OSX, open WhatsApp web on Safari, allow notification & pin the tab. Same outcome but resource efficient (compared to an Electron app).
Couldn't agree more. I'm a lead web developer at a company and whenever I'm asked to interview a potential employee I give em' a short coding task. Internet access is allowed. The only restriction I give em' is not to clear their search history.
If the candidate knows the problem he/she is facing and can formulate good query to look for a solution; that's a ++
- shows an example using mutation observer API and fails to mention it only works on IE 11+
- follows the widely accepted format of "rant about some popular framework/library/language by mimicking a tiny portion of it"
- uses shock factor to get the reader's attention
> React, Virtual DOM, Webpack, TypeScript, JSX…
HOLD ON! Let’s pause for a second here and think.
YES, you don't always need a framework/library BUT if you want to build something maintainable & scalable, it's better to opt for battle tested approaches (which is especially true when it comes to the web, having browser quirks)
Double tapping the home button makes the top of the screen reachable
That being said, I too still use iPhone 5S & I don't think I'll make the switch, 4K video & 2nd generation Touch ID are nice but I WANT 3D Touch. I understand why they're not there yet --- they had to shove some of the battery on the 6S to fit in the 3D hardware.
EDIT: seems they stuck with the first generation Touch ID? (6S and SE) [1]
Yeah, but the process to using "reachability" in my experience is always something like: reach for the button because I can totally make it, accidental palm-press on the bottom-opposite corner, undo mistake, try again with different hand angle, do it again, undo it again, then remember about reachability shortcut, double touch home button, reach button.
1. Vue uses the actual DOM not virtual DOM like react
2. BOTH react and Vue can be learnt in a day
3. BOTH can seem daunting when you're making production app (Vuex, redux, webpack, Vue-router, react-router...)
So, I don't not agree with 'learning curve' that's thrown at React. Both Vue and React are amazing. If you want to use them properly, you as a developer has to spend the time to learn.
> 1. Vue uses the actual DOM not virtual DOM like react
Facebook really should have named the Virtual DOM something different to avoid this confusion. The "Virtual DOM" is not an alternative to the DOM (which would be impossible), it is just a string diffing algorithm to minimize the number of DOM mutations required.
[1] has been known for draining battery, so no surprises there.
[2] which for a couple of releases has become even more unusable. On my MBP (2014, i5, 8GB), takes over 4+ seconds for the bar to activate. Hopefully with the introduction of E10S [3], next releases will be much more perfomant.
[3] https://wiki.mozilla.org/E10s
EDIT: I did not know Safari is no more on Windows. So in that case Edge is the winner for Windows.