There’s not really a vendor here since macOS is free. Linux isn’t exactly free from the need to choose well-supported hardware either, particularly of you need to run a more stable distro
macOS isn’t really free. It just “comes with” the hardware you just bought. You’re not supposed to download the OS unless you have qualifying hardware. A hackintosh rig does not qualify.
>And yes, it most definitely does load slower for me - I have nothing but a blank white page for several seconds.
This is quite obviously an error state, likely caused by an extension of yours. Have you tried using Amp in a fresh install of a different browser? Using different network settings?
It seems very likely that you are the reason amp doesn't work for you.
The issue is that for some reason amp usually seems to block the content from being displayed until the javascript loads, which strikes me as the exact opposite of what an "accelerated mobile page" should do (almost like it was designed by an advertising company wanting to discourage ad blockers...). You can bypass it by activating reader mode in your browser.
Not only that, but AMP pages are only potentially perceived as 'fast' when you access them through google's search. When you do that all the AMP links' assets are pre-loaded in the background so it seems fast when you click through. But AMP pages themselves are just the same speed as anything else or slower when access without google's monopoly position pre-load.
the original code, even before the float handling, was was a perf optimisation:
!!(~~i & 1);
Nobody wants to see that in code unless it has a name. Maybe isOdd(). Maybe we should put it on GitHub to save others time. Sure beats copy-pasting from StackOverflow.
Original:
Did you think of handling floats in your home built isOdd implementation? Thankfully Jon (EDIT: or one of his contributors - doesn't change the point) did. And they added tests.
The (flagged) article makes the staggering assumption that "we can't code" because we're not constantly reinventing the wheel. It talks about DRY being taken too far and talks about the functions being replaced as "one liners", when following a couple of links would show they're not. We can code, we're just coding on actual features, not rewriting the same poop.
It works with Firefox 60, Google however sometimes relies on Chrome quirks not specified in the standard which may not make it usable in Firefox. (Last I checked)
It does not, and Google does not yet even attempt to use WebAuthn. They're still using the (now legacy) U2F authentication mechanism, which firefox does not fully support. It works in some sites if you enable it in about:config, but not all. Like google.com.
Hmm, yeah, I was more aiming at "Firefox has working WebAuthn in the newest Version, Google just doesn't use it properly or at all", I should have expressed that better.
Running it locally is fine, but a hassle if I need to access my mail on someone else's hardware (or my phone). I think this is one of the main reasons Gmail is so popular.
Perhaps it's just their preferred platform. If it weren't for the expense I'd probably prefer it over Windows at least. At any rate, the readme does link to this article[1] if macOS isn't your thang.
Daemon by Daniel Suarez is kind of like that, except it turns out the AI is arguably good and not exactly an AI. It's an excellent book, with an excellent sequel.
Also, the font color on this blog is absolutely horrible.