739 karma · joined July 16, 2013
I googled "Trump". First five stories in carousel (wapo, bbc et all) are not AMP. I see only one AMP link in the first page results. Click on it, page loads. Swipe right/back button gets me to Google results (as expected). Is it because I'm on an iPhone and this is an Android thing?
You can see how this is confusing, here's a recent one just from today by Craig Federighi https://twitter.com/feross/status/871839072590979076
Not judging, but if high profile articles and browser vendors started addressing it correctly we wouldnt have any issues migrating, more syllables or not.
It suffers like you and I. That's the whole premise of this discussion.
You didn't answer my second question. Would you be willing to torture the above mentioned being?
Would it be ethical to torture a sentient being existing in your hardware, for fun?
Why do you believe ownership is decided based on residence? Do I own my pet dog? Is it ok to torture it?
I think you are grossly underestimating countless nuances of the ethicalities AI brings to the table.
If you want to try something install it and then remove it. That's the more conscious decision. I don't want to have to remember to save the module if I end up liking it, but I will remember to remove it when tearing it down from the codebase, and if I don't, nothing bad happens.
(Please correct me if the COMMIT column in the perf table includes the staging operations.)
This looks awesome. I just wish Facebook would also share some perf and time statistics on their own extensions for Mercurial, last time I checked their graphs were unitless.
I did not expect to argue in HN of all places whether it's OK or not to run the development mode of a library in production when it's so simple not to and the authors are trying so hard to prevent people from doing that.
Not sure how Next.js does it but you should probably try putting NODE_ENV=production in the "build" script in package.json like in "start"?
I had a quick glance over Next.js's docs and it looks like they should handle this automatically just by `next build`. ¯\_(ツ)_/¯
FWIW this topic would make for a great technical post/how-to.
I also seem to recall that Automattic does this with their front end (calypso) which handles wordpress.com
Purely out of interest what kind of hardware is incompatible between the two versions?
What's impressive is how people manage to spin this into an anti MS rant even when Microsoft is doing the right thing (stopping support for paleolithic software).
Are you afraid that programming skills deteriorate with age for some reason?
On (desktop) Safari hovering over a few sections causes the site to just randomly scroll to another section (e.g. Hovering any of the first 2 links of "Get in touch" goes a section back and the third one goes to the last hero section").
In mobile Safari (latest version) the website stops functioning after the first scroll until the end, the hero is the only thing that is viewable.
Lastly, the infinite scrolling loop doesn't work backwards (i.e. scrolling up) which gets a bit confusing.
There's something extremely fundamental in scrolling, it gets embedded in the user's cognition. I wonder what we need to do to raise awareness in finally stopping to meddle with it.
- Why is it built with React? - Why does it need to load so much JavaScript? - Why does it need to load a custom web font? (There's exactly zero text from what I see). - Why does it need a CSS grid framework?
There are a few solutions for Ruby, PHP and Python although I have no experience with them and how well they perform/work.