4 ms·
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 perf
by xal 16y ago
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.
- ludicast 16y agoThe 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.
- jcapote 16y agoI'm knee deep in encoding hell right, I'd love to hear more about how you patched it to work with 1.9.2
- edwardog 16y agoYou 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_default_encodings 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
- jcapote 16y agoHa! Glad to know I'm not the only one hitting the Array.to_s surprise!
- wvanbergen 16y agoMy favorite issue in 1.9.2: "." is no longer included on the $LOAD_PATH.
- aaronblohowiak 16y agoWhy aren't you on jruby if you have serious performance requirements? A sufficiently warmed-up jvm will outpace 1.9.2
- xal 16y agowith shopify's code size jruby needs 2gb of memory per process and we found that it spends almost all the time in GC.
- aaronblohowiak 16y agowhich version of jruby? is 2gb per process an issue if you can run it multithreaded?