temo4ka

Safari serves a very important role of showing users how decidedly inadequate web experience is compared to native.

There is also ScrollMagic http://scrollmagic.io/

I first heard the notion from someone here on HN: instead of doing what you love, love what you do!

I wonder what would you say about accessibility standards of this website? :-)

I agree with you on this one, but I have hard time believing that between U.S. and Russian governments the former is more dangerous to its citizens than the latter.

Previous discussion:

https://news.ycombinator.com/item?id=7740336

Heh, I like how Richard Stallman begins his messages: https://lists.gnu.org/archive/html/emacs-devel/2015-10/msg00...

In the case of 10 Kb files those approaches won’t make any noticeable difference. But when you have large code bases consider how often changes would be made to them: in most cases it is sensible to split your files into two bundles — one for libraries or files that are not going to be updated any time soon, and the other for project-specific code, that is very likely to be tweaked in the course of the time following the release of the project. Thus you leverage caching and don't force the users to download the whole CSS or JS codebase every time you make some small adjustment.

I actually keep a Chrome Snippet for such cases.

    var getFont = function(url) {
        var link = document.createElement('link');
        link.rel='stylesheet';
        link.type='text/css';
        link.href = url;
        document.head.appendChild(link);
    }

    getFont('https://fonts.googleapis.com/css?family=Open+Sans|Roboto')

    var sheet = (function() {
        var style = document.createElement('style');
        document.head.appendChild(style);
        return style.sheet;
    })();

    sheet.insertRule('body { font: 400 16px/24px Roboto,sans-serif!important; -webkit-font-smoothing: antialiased; }', 0);

Looks like a place to practice mental arithmetic tricks, you know, like multiplication by 11:

  11 × 16 = 1(1+6)6
  34 × 11 = 3(3+4)4
  124 × 11 = 1(1+2)(2+4)4

Or multiplication table 10 through 20:

  14 × 17 = (14+7) × 10 + 7 × 4
  13 × 18 = (13+8) × 10 + 8 × 3

3. b) http://blog.keithcirkel.co.uk/how-to-use-npm-as-a-build-tool...

Doesn’t necessarily mean he’s a bad developer; there are many frontend devs who see their job as pure programming. Which it is not. For frontend developer, an important part of the job is to know what a good design is and what concepts underlie it. Yet it’s hard to gain such knowledge without either designing or working closely with designers.

This “app view” is natural, because it’s less about bookmarking, and more about sharing — one of the key concepts behind the Web.

You are of course right.

Users of software don’t care for the terms developers use to label their creations, “web app” or “web page” — it’s all the same to them. More importantly, they expect an identical behaviour from both. So when a web app can’t recreate its state from URL it’s breaking a fundamental web UI convention.

Another core UI convention that is often disregarded by web app developers is link click behaviour, i.e. you expect anything that performs a function of a link to behave as it normally would when you click on it with mouse’s middle button, or right click → context menu, or left click with modifier keys (cmd/ctrl, shift). Everyone got used to this and when the pattern is broken it is most annoying.

Frontend development has always been hell. Everyone who has done it professionally knows this.

Off topic: is anyone else annoyed by those background-fixed image sections? Because the height of the section is bigger than the height of the viewport while scrolling past those sections it appears for a moment that the page stopped responding; the effect is especially prominent on wide screens.

A complementary tip for Ctr+R is to tag long reusable commands with a comment in the end, e.g.,

find . -name "*.png" -print0 | xargs -0 -P8 pngquant --ext .png --force 256 #optimizepng

(if you’re using zsh, you have to enable INTERACTIVE_COMMENTS option first; just run set -k)

Who says they use IE for googling? :-)

I suspect browser doesn’t matter much here. Console yields a TypeError until Flash is enabled (whitelisted) for the page.