Kenn EjimaさんのGoogle+ Trends

反応が多かった投稿ランキング

Can't ag... : 2013-03-21 23:44:57 コメント 1件 共有 1人
Can't agree more.

---

My Problem W... : 2012-10-26 12:17:31 共有 1人
My Problem With Turbolinks I made a few snarky comments about Turbolinks recently and figured I should write down my thoughts more clearly. If you're not aware of Turbolinks,it captures all local links that look like HTML pages,makes an Ajax request for the content,and then replaces the body with the response's body. It does a few other clever things,like extracting and replacing the title,and executing scripts in the response. Overall,it's a clever way to get some increased speed while still using a traditional server-rendered-HTML architecture. Caveats Like any other solution,it comes with some caveats. Probably the most important one is that normal HTML-rendered pages have their own clean global scope every time a new page is rendered. This is not a mere quibble: a lot of existing JavaScript operates under the assumption of a clean scope,and a single DOMContentLoaded event. In a perfect world,popular JavaScript plugins would be architected to work well with a solution like Turbolinks,but the assumption of a clean global scope per server-rendered HTML page is baked into a lot of the JavaScript and jQuery libraries that people tend to use. It is possible to deal with problems like this on a case-by-case basis (see https://github.com/rails/turbolinks/issues/87,for example),but in my opinion,this is going to end up in a game of whack-a-mole as each new patch breaks other valid use-cases. At the end of the day,unless Turbolinks can perfectly emulate the browser's behavior,attempts to use Turbolinks with third-party JavaScript will either fail often or require an ever-growing library that handles more and more targeted edge-cases. jQuery Turbolinks (https://github.com/kossnocorp/jquery.turbolinks) is a good example of something that tries to make the solution more transparent,but introduces problems as it now triggers ready callbacks multiple times,and idempotence is not typically a requirement of ready handlers. I encourage you to review the open and closed issues on

---

写真などを投稿 : 2014-09-21 02:07:15 コメント 4件

---

写真などを投稿 : 2014-09-21 13:27:25

---

写真などを投稿 : 2014-09-21 13:24:38

---

写真などを投稿 : 2014-09-21 03:28:15

---

Octocatクッション... : 2013-10-13 14:14:47
Octocatクッションこわいw

---

Chrome: Easi... : 2012-11-17 02:33:09
Chrome: Easier Web App Debugging With Multi-User Profiles We often want to debug sites or web apps as more than just one user. Maybe specific accounts have different data profiles or your app supports multiple types of user account (eg. basic,admin,support). Quite often in the wild,we've seen developers either debugging these scenarios using separate Chrome Incognito windows or completely different browsers to debug different accounts. The good news is that all channels of Chrome support easily managing multiple user profiles (and windows) via a convenient drop-down menu in the title bar. I'm sure most of you know about this,but hopefully this will serve as a reminder. To add a new user: * Click on the menu in your browser toolbar and select Settings. * In the "Users" tab,click the [Add new user] button. * When the confirmation dialog appears,select a picture and enter a name for the new user. Click [Create]. * A new window for the user should appear,with a picture you've chosen for the user in the top corner. Each user profile can also sync up with all the bookmarks,extensions,theme,and browser settings for it if you're signed in. This also makes it more straight-forward to switch between profiles with business Google Apps accounts and personal ones,but is great for getting more control over your window workflow. 

---

写真などを投稿 : 2014-09-21 13:26:07

---

写真などを投稿 : 2014-09-21 13:26:05

---

写真などを投稿 : 2014-09-21 13:23:20

---

写真などを投稿 : 2014-09-21 13:23:17

---

写真などを投稿 : 2014-09-21 13:21:57

---

写真などを投稿 : 2014-09-21 13:18:42

---

写真などを投稿 : 2014-09-21 13:17:03

---

写真などを投稿 : 2014-09-21 01:11:45

---