Application Holotypes: A Guide to Architecture Decisions - JASON Format
Analyzing the characteristics of real-world applications is difficult. We often make generalizations about applications we see in the wild, both anecdotal and statistical: "Single-Page Applications are slower than multipage" or "apps with low TTI loaded fast". However, the extent to which these generalizations hold for the performance and architectural characteristics we care about varies. I belie
Logic-less JSX | V1V2
Example situationHere is a design and its markup: <ul> <li><a href="url/animal/1">Dog</a> - 4 legs - Friendly</li> <li><a href="url/animal/2">Bird</a> - 2 legs</li> <li><a href="url/animal/3">Snake</a> - 0 legs - Unfriendly</li> <li><a href="url/animal/4">Centipede</a> - ? legs - Not enough data!</li> </ul> const data = [ { id: 1, name: 'Dog', legCount: 4, isFriendly: true }, { id: 2, name: 'Bird'
ongoing by Tim Bray · Post-REST
More or less all the big APIs are RESTful these days. Yeah, you can quibble about what “REST” means (and I will, a bit) but the assertion is broadly true. Is it going to stay that way forever? Seems unlikely. So, what’s next? What we talk about when we talk about “REST” · These days, it’s used colloquially to mean any API that is HTTP-based. In fact, the vast majority of them offer CRUD operations
Large-scale Vuex application structures
Me trying to handle state and structure in large applications When writing large-scale applications, managing the state of the frontend can be quite hard. For Vue.js applications, for example, there is a plugin called Vuex that offers state management in a really simple way , and suggests using the following application structure: Vuex recommended application structure If you are curious about an
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Atomic Architecture
How do sites such as FriendFeed and Flipboard scale out their social data-aggregators?
bitly/nsq · GitHub - A realtime distributed messaging platform
