davidbgk
/
larlet-fr-david
Observar 1
Favorito 0
Fork 0
Código Versões 0 Atividade
Repository with sources and generator of https://larlet.fr/david/ https://larlet.fr/david/
Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
123 Commits
1 Branch
Tag: 917b4dd3b1
Branches Tags
${ item.name }
Criar branch ${ searchTerm }
de 917b4dd3b1
${ noResults }
larlet-fr-david/david/stream/2015/07/01/index.md

index.md 1.2KB
Original Visão normal Histórico

Add initial content
4 anos atrás
​
​
​
​
​
​
 1234567 
  1. title: Sans serveur

  2. 

  3. > You probably had this feeling already, when you write server code only to proxy client’s demands for the DB and pass the results back. It feels stupid. It feels redundant. All these trends — isomorphic code, compile-to-js languages, node.js — come from a desire to run the same code in two places. That very goal is wrong. You don’t *want* to run same code in two places. You may *need* to, but only to deal with the consequences of bad (old) architecture. Running exactly the same validation twice wouldn’t make data more valid.

  4. > 

  5. > <cite>*[The Web After Tomorrow](http://tonsky.me/blog/the-web-after-tomorrow/)* ([cache](/david/cache/34a79c7f0c1b3e0e53579efdf9d26410/))</cite>

  6. 

  7. Clochix pense qu’il n’y a [pas de futur sans serveur](http://esquisses.clochix.net/2015/06/16/no-future/) ([cache](/david/cache/ff174bf843c4340fb6ace98cd876c571/)) représentatif d’un Web acentré. Et pourtant la proposition de Nikita Prokopov est alléchante, les flux et les besoins de données évoluent, les technologies commencent à être prêtes, l’opinion publique se réveille doucement. Et si le futur était au *acentered-first* ? Quels impacts en terme d’usages, de vie privée, de performances ?