News for hackers. Stuff that matters.
Re:Shopify's path to Rails 3 by xal on Tuesday November 16, 2010 @02:39PM (#1911298)
Cool that you managed to upgrade to 1.9.2. The encoding issues have us scared. We do have a few special purpose webapps that run 1.9.2 because of very high performance requirements.
Re:Shopify's path to Rails 3 by aaronblohowiak on Tuesday November 16, 2010 @06:58PM (#1912279)
Why aren't you on jruby if you have serious performance requirements? A sufficiently warmed-up jvm will outpace 1.9.2
Re:Shopify's path to Rails 3 by xal on Tuesday November 16, 2010 @07:10PM (#1912321)
with shopify's code size jruby needs 2gb of memory per process and we found that it spends almost all the time in GC.
Re:Shopify's path to Rails 3 by aaronblohowiak on Wednesday November 17, 2010 @02:18AM (#1913278)
which version of jruby? is 2gb per process an issue if you can run it multithreaded?
Re:Shopify's path to Rails 3 by ludicast on Tuesday November 16, 2010 @03:01PM (#1911388)
The encoding issues bit me in a few places (especially with paperclip), and I have some hacky initializers running that monkeypatch a few libraries to behave well enough.
Re:Shopify's path to Rails 3 by jcapote on Tuesday November 16, 2010 @03:05PM (#1911405)
I'm knee deep in encoding hell right, I'd love to hear more about how you patched it to work with 1.9.2
Re:Shopify's path to Rails 3 by edwardog on Tuesday November 16, 2010 @03:48PM (#1911584)
You can fix most encoding problems with doing

  Encoding.default_internal = Encoding.default_external = "UTF-8"
but as JEG states in http://blog.grayproductions.net/articles/ruby_19s_three_defa..., this throws warnings and may still not fix things.

Encoding issues rank up there with Array.to_s pains when moving to 1.9

Re:Shopify's path to Rails 3 by wvanbergen on Wednesday November 17, 2010 @11:13AM (#1914663)
My favorite issue in 1.9.2: "." is no longer included on the $LOAD_PATH.
Re:Shopify's path to Rails 3 by jcapote on Tuesday November 16, 2010 @04:11PM (#1911685)
Ha! Glad to know I'm not the only one hitting the Array.to_s surprise!