index.md 2.6KB
title: Performances, apps et frameworks JS
Billet comportant les liens de veille technologique présentés aux étudiants dans le cadre d’une routine de mes cours.
Given the fact that mobile performance is a huge priority for Google, this label isn’t a trivial feature. If you care about performance, user experience, and SEO, then you should care about this potential game-changer.
Google’s experimental new “slow” label could revolutionize how we tackle web performance (cache)
Performances web et référencement, on en parlait lors du dernier cours justement.
How we experience content via connected devices – laptops, phones, tablets, wearables – is undergoing a dramatic change. The idea of an app as an independent destination is becoming less important, and the idea of an app as a publishing tool, with related notifications that contain content and actions, is becoming more important. This will change what we design, and change our product strategy.
Ainsi que sa suite (cache), articles très intéressants à rapprocher de ce que fait Pebble Time avec sa notion de timeline.
Nobody can try all the popular options, but everybody wishes for consolidation and more wood behind fewer frameworks. As such, a lot of developers have fallen into a pattern: avoid learning a new framework until it seems like one is finally ascending to the throne as the widely popular, exceptionally capable, “won’t get you fired” choice for building JavaScript frameworks.
Une explication possible de la diversité des frameworks JS et de la stratégie à adopter pour miser sur LE bon. Peut-être React ? Peut-être Riot ? Peut-être Mithril ? Peut-être un framework qui n’existe pas encore… le vôtre ?
Et sinon quand est-ce que l’on produit de l’utile ?