1,249 karma · joined December 22, 2014
I know that's a metaphor, but it got me thinking. Can someone more learned help me out: does air behave in a non-Newtonian manner at supersonic speed?
It’s harder to read code than to write it.
I continue to use that line to explain coding to non-coder friends. This article's author seems to understand that as well, but it's worth making explicit.
[1] https://www.joelonsoftware.com/2000/04/06/things-you-should-...
I like the look. Very clean. I like how fast it's responding; better than archive.org (though, obviously, they have different scaling problems).
"Your own internet archive" might be overselling it, as other commenters have pointed out; the "Your" feels a bit misleading. I think "Save a copy of any webpage." gives a better impression, which you use on the site itself.
The "Archive!" link probably shouldn't work if there's nothing in the URL box. It just gives me an archive link that errors. Example: [1]
Using it on news.YC as a test gave me errors with the CSS & JS [2]. This might be due to the fact that HN uses query parameters in their CSS and JS, which repeat in the tesoro URL, which you may not be parsing correctly.
Maybe have something in addition to an email link for submitting error reports like the above, just cause I'd be more likely to file a GitHub issue (even if the repo is empty) than send a stranger an email.
As other commenters have pointed out, archive.is also does this, and their longevity helps me feel confident that they'll still be around. Perhaps, if you wish to differentiate, offer some way for me to "own" the copy of the page, like downloading it or emailing it to myself or sharing it with another site (like Google Docs or Imgur) to leverage redundancy, or something like that. Just a thought.
All in all, nice Show HN.
EDIT: You also may want to adjust the header to work properly on mobile devices. Still though, nice job. Sorry if I'm sounding critical.
[1] https://archive.tesoro.io/320b55cc9b78e271c94716ee23554da8
[2] https://archive.tesoro.io/a7bf03e247224bc3b4e5a7c1f2ad42b1
[1] https://nickcraver.com/blog/2017/05/22/https-on-stack-overfl...
Counting unique declarations doesn't really tell me anything. CSS isn't simply a declarative language. CSS rules are ordered. Sometimes (and oftentimes within webapps) you need to repeat a declaration because you're using it to overwrite an earlier declaration but only when the second selector is valid. For example, it's very common to have lots of `display` declarations that turn on or off elements by overwriting earlier rules. Because of this, you're going to have lots of "repeat" declarations, but they're not repeated in their location within the order. With complex pages, you're going to wind up twisting yourself in knots trying to keep everything logically ordered if you also want to minimize declarations.
Additionally, from my naive understanding of browser engines, the performance cost of multiple rules applying to an element is greater than the cost of multiple declarations within a rule. Why minimize them?
But my largest concern is the mental overhead of trying to simplify rules in code. Co-locating declarations affecting a logical unit is extremely helpful. The tool we have to accomplish this is called a selector. Minimizing declarations increases selector count, which kind of defeats their purpose. Pre-processors can't solve this for you either, due to CSS rules being ordered. If all you're building is a static page then, sure, I can see minimizing declarations being some kind of goal. But CSS gets used for a lot more than static pages.
As other commenters have noted, if the author's concern is overly-large CSS files, run-length encoding alleviates a lot of that, at least if the declarations are in the same file (a reason to not use http2 as a silver bullet and use concatenation instead, if that's a concern).
EDITS: Added a couple sentences.
Nice service, lots of luck.
Specifically, the "GO TO THE HACKER NEWS DATASET" big blue button on that page. It kicks me over to a Google Cloud console link, which spins for a few seconds, and then brings up a "Welcome to BigQuery!" modal. The only thing I can do then is click "Create a Project", which then kicks me over to the generic console with a listing of all APIs.
Am I missing something?
[1] https://www.techempower.com/blog/2016/11/16/framework-benchm...
http://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHostin...
http://docs.aws.amazon.com/AmazonS3/latest/user-guide/static...
As an App/Integration, is your interaction with the GitHub interface itself limited to only those things that you can do via API calls, such as creating new issues? Or do you have some capacity to modify or add on to the existing interface?
Also, this should probably have a "[2016]" tag in the title.
Is this true? Have there been times when news was funded by other means than advertising?
A reference: http://english.stackexchange.com/a/68653
Edit: Think of the difference between "lack of safety" and "lack of proof of safety".
I know that I have personally opened search results to AMP pages that I would not normally have opened because I knew the price of doing so would be small. But, then again, I know what the AMP symbol means. How this affects normal users remains to be seen.
For some sites, I seek out the AMP URL explicitly. For example, adding "/amp" to the end of TechCrunch URLs change them from frustrating to usable.
A better, more recent story: https://www.bloomberg.com/view/articles/2016-01-04/millennia...
Edit: The earlier version of my comment was wrong.