From: Jon Date: 2010-02-28T05:13:11+09:00 Subject: [ruby-core:28365] Indentifying key MRI-on-Windows issues In an effort to begin summarizing key MRI-on-Windows open issues I'm starting this thread in hopes that those interested will respond with details on the key MRI issues they feel need resolution for Windows users. After review and consensus, we should put a summary list (similar to http://redmine.ruby-lang.org/wiki/ruby/SomeCoreFeaturesFor192) with the details for each issue in the tracker. My key concern is http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/24968 I'm not yet clear as to the root cause. For example, is this #ifdef "fixable" for Windows due to implementation specifics of MRI's IO, or is it a consequence of needing to handle Windows CRLF and not a weakness in the current implementation? Are *nix systems able to IO optimize for this case while Windows systems cannot? Is the reason this performance delta isn't seen in JRuby[1] is that the JVM's cross-platform IO handling always has to handle both cases and therefore can't fully optimize for one platform, i.e. - all pay the price? Others? Jon [1] http://archive.codehaus.org/lists/org.codehaus.jruby.user/msg/f04d2210908141546l15a1ff7bl4e494ebdca4ac588@mail.gmail.com usa, nobu, To ensure I fully understand, how do you prefer Windows-specific sightings/issues/bugs be reported? Should "sightings" be posted this ruby-core ML and only when you've agreed they are bugs should we open Redmine tracker issues? Or do you prefer all sightings and issues be opened as Redmine tracker bugs regardless of whether the sightings are first confirmed as bugs?