Robert, While I agree (and as you discovered later, I mentioned it was a platform problem), it is not logical to just blame Windows and leave it as is. The truth is, that is Window's reality, for better or worse. That is what exists, and to not acknowledge what exists and not prepare or do something about such reality is entirely irrational.
Shouldn't Ruby install itself in such a way that makes it work the way Window's works in reality? Yes, it should - even if it's Window's fault - if it wants more developers to use Ruby and to use Rails. It IS in their rational self-interest after all, is it not? I don't see the point in blaming Windows. Windows is the piece of crap it is... and if you want to do what is in your rational self-interest, the platform should still work on it. I guess rational self-interest and logic doesn't play a part in your world Robert, just some kind of OS fanboyism. Sheesh. Ken On Oct 7, 9:05 am, Robert Walker <[email protected]> wrote: > egervari wrote: > > I just installed it and it seems like everything goes smoothly... but > > I'm having one hurdle after another installing a new application. I've > > had to get various dlls for sqlite, mysql and msvcrt-ruby18, or things > > out-right crashed. > > This is a Windows problem not a Ruby on Rails problem. > > > I've had an error where rails though I didn't have rake installed... > > but the gem was installed. I had to remove a file called rake.gemspec > > and reinstall rake for everything to work. > > Again you're falsely blaming OS problems on Rails. > > > I don't mean this to sound bad, but for a framework that claims to > > "just work", it certainly has it's share of bugs or hurdles. Maybe > > it's just because I run windows 7 64-bit. I dunno :( > > If you use an operating system that "just works" then Rails will also > "just work" (generally speaking, of course). > > > These seem like platform issues to me, an area that Java really does > > have a leg up on. At least when you install java... it works :/ > > You are correct. It is a platform problem. The issue really is that > Windows is treated as a second class development platform within the > Ruby and Rails community. IMHO I believe this to be due to the simple > fact that the vast majority of the developers actually building Rails > are on some form of UNIX/Linux based OS. > > > I'll keep playing with it. I hope after these hurdles, everything will > > eventually just work. > > I actually do hope that things will eventually improve on Windows. Not > for myself since I have no interest in anything Windows, but for those > who either choose Windows or don't have a choice. > > However, having said that I would not recommend you holding your breath > waiting on the Rails core team to fix this. It's probably going to take > a community effort of Windows centric developers to fix this issue. That > is if there really is an issue needing fixed that hasn't already been > fixed. > > Problems get fixed through need. I'm quite sure that fixing Rails on > Windows is not a major need of the core team. > -- > Posted viahttp://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
