@YasuLab

shyouhei:

どうなんですかねえ。まあぶっちゃけ、この本にツッコミを入れることが容易な種族はいる。たとえば「プロセスがfork(2)するときにPOSIX semaphoreをsem_wait(3)してたらそのセマフォはどうなってまうの？」とかそういうの(実際書いてない)ね。けど、それって、そういうの目ざとく気がついてしまう人、はっきりいって対象読者じゃないというべきだろうなあ。LinuxとBSDのカーネルコミッターの皆さん、セプキャン講師陣の皆さん、未踏スーパークリエーターの皆さん、お疲れさまです。おまえらはお呼びじゃない。

…

gunosy:

初めまして。Gunosyのマーケティング担当の竹谷と申します。

※下部がきれてしまうというCSSマターの問題があったため同内容をはらせて頂いております。

http://bit.ly/10cRtX6

週末から、Gunosyに対する批判記事があり様々なユーザー様から質問を頂いているので簡単に所感を書かせて頂きたく思います。

ここまで大きな騒動になっているにも関わらず会社から何も出さないことは良くないと思いましたのでこの場を借りて所感を記載させて頂きます。

おそらく批判記事の内容を見ていると大きく分類して論点となるのは以下かと思います。

…

How 2.0 Changed Here are some highlights of the changes that jQuery 2.0 brings:

No more support for IE 6/7/8: Remember that this can also affect IE9 and even IE10 if they are used in their “Compatibility View” modes that emulate older versions. To prevent these newer IE versions from slipping back into prehistoric modes, we suggest you always use an X-UA-Compatible tag or HTTP header. If you can use the HTTP header it is slightly better for performance because it avoids a potential browser parser restart.

Reduced size: The final 2.0.0 file is 12 percent smaller than the 1.9.1 file, thanks to the elimination of patches that were only needed for IE 6, 7, and 8. We had hoped to remove even more code and increase performance, but older Android/WebKit 2.x browsers are now the weakest link. We’re carefully watching Android 2.x market share to determine when we can cross it off the support list, and don’t expect it to take very long.

Custom builds for even smaller files: This feature has been greatly refined and extended since its debut in jQuery 1.8. You can now exclude combinations of 12 different modules to create a custom version that is even smaller. A new minimal selector engine, basically a thin wrapper around the browser’s querySelectorAll API, lets you shrink the build to less than 10KB when minified and gzipped. See the README for instructions on how to create a custom build, and remember that any plugins you use will also need to stick to the subset you select.

jQuery 1.9 API equivalence: jQuery 2.0 is API-compatible with 1.9, which means that all of the changes documented in the jQuery 1.9 Upgrade Guide have been applied to jQuery 2.0 as well. If you haven’t yet upgraded to jQuery 1.9, you may want to try that first. Be sure to use the jQuery Migrate plugin.

The full record of changes can be found in the changelog below, and in the list of commits on GitHub.

rubykaigi:

We RubyKaigi 2013 Team are looking for lightning talks from the attendees/speakers/sponsors of RubyKaigi 2013. ANY TOPICS RELATED Ruby AND/OR RUBYISTS are welcomed!

It must be suitable for making announcement of your excellent product, your awesome community and your great idea worth to spread!

Submission Form is here: