应该去成都
js remove 可行吗
makitup 不错的 定制度高
@qinfanpeng 要急时的 off client side validation 的事件 用 turbolinks 的碰到过同样的问题 就是这样解决胡
是的 topic.rb field :node_name 中的这个值为空了
和 41 楼 差不多的作息。
已经最大化缓存了,看了下源化码,不过 controller 中的 includes 可以不用了
Unfortunately, a fatal error has occurred. Please see the Bundler
troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
/Users/lv/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/site_ruby/2.0.0/rubygems/source.rb:135:in rescue in load_specs': Invalid spec cache file in /Users/lv/.gem/specs/ruby.sdutlinux.org%80/specs.4.8 (Gem::Exception)
from /Users/lv/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/site_ruby/2.0.0/rubygems/source.rb:127:in
load_specs'
from /Users/lv/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/site_ruby/2.0.0/rubygems/spec_fetcher.rb:225:in tuples_for'
from /Users/lv/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/site_ruby/2.0.0/rubygems/spec_fetcher.rb:199:in
block in available_specs'
from /Users/lv/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/site_ruby/2.0.0/rubygems/source_list.rb:55:in each'
from /Users/lv/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/site_ruby/2.0.0/rubygems/source_list.rb:55:in
each_source'
from /Users/lv/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/site_ruby/2.0.0/rubygems/spec_fetcher.rb:190:in available_specs'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/rubygems_integration.rb:453:in
fetch_all_remote_specs'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/fetcher.rb:261:in fetch_all_remote_specs'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/fetcher.rb:116:in
specs'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/source/rubygems.rb:227:in block in remote_specs'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/source/rubygems.rb:227:in
each'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/source/rubygems.rb:227:in remote_specs'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/source/rubygems.rb:162:in
fetch_specs'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/source/rubygems.rb:66:in specs'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/definition.rb:192:in
block (2 levels) in index'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/definition.rb:189:in each'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/definition.rb:189:in
block in index'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/index.rb:9:in build'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/definition.rb:185:in
index'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/definition.rb:179:in resolve'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/definition.rb:114:in
specs'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/definition.rb:109:in resolve_remotely!'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/installer.rb:83:in
run'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/installer.rb:14:in install'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/cli.rb:248:in
install'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/vendor/thor/task.rb:27:in run'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/vendor/thor/invocation.rb:120:in
invoke_task'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/vendor/thor.rb:344:in dispatch'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/vendor/thor/base.rb:434:in
start'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/bin/bundle:20:in block in <top (required)>'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/lib/bundler/friendly_errors.rb:3:in
with_friendly_errors'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/gems/bundler-1.3.2/bin/bundle:20:in <top (required)>'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/bin/bundle:23:in
load'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/bin/bundle:23:in <main>'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/bin/ruby_noexec_wrapper:14:in
eval'
from /Users/lv/.rvm/gems/ruby-2.0.0-p0/bin/ruby_noexec_wrapper:14:in `
报了好多错,官方和淘宝源没有问题
rails4 最大量缓存 就没有毕要 n+1 了,同意 n+1 的观点
期待 ruby-china rails4 的重构,使用那个 doll cache ,估记能控制到 40ms 以内吧
用 thin 2.0
@xdite 不过好像如果使用了 cache do 的话把一些数据库 (例如一些数据需要贪婪查义的) 的操作放到视图里面的话,一但缓存下来了,就不用再查询数据库了吧,应该又能提高页面的响应速度吧。这样的话是不是又应该放到视图里面来呢?
没有易用性 删除记录放在这难看死了
不知道 ruby-china 的缓存改成这样应该能提升不少响应速度吧,50ms 以内估记
#t=80m12s DHH 的
@camel Revised 的
javascript 难学呀
很想听听关于缓存方面的经验,还有网站上线后的各种数据监测,最好能结合 basecamp next 的http://37signals.com/svn/posts/3112-how-basecamp-next-got-to-be-so-damn-fast-without-using-much-client-side-ui 估记很多人也想做 fast 项目,在 rails 的默认体系下,结束后有 ppt 可以分享
@jokry 我测试的最快的 js 模板是 doU.js 300 多W http://jsperf.com/dom-vs-innerhtml-based-templating/73
@ywencn 优质的值的收藏的的真的不多
预览和用户自定义剪裁都是用 js 实现的
参考 thumbs_up
编译了一个还是要注册码
GET http://ruby.taobao.org/latest_specs.4.8.gz 302 Moved Temporarily GET http://gems.ruby-china.org/latest_specs.4.8.gz
connection reset after 1 requests, retrying 怎么回事