9 ms·
Burning out on Capistrano (Jamis Buck)
- catch23 18y agoAlthough lots of comments are about the Ruby language, I think this post can be applied to just about any open source project out there. It's always easier to complain to the maintainer than to try to fix the problem yourself and distribute the fix as a patch to others. Open source doesn't work well if there's only one person who fixes all the problems. I think it could also be a newbie developer mentality. Newbie developers are more likely to use libraries that are completely plug-and-play; if something doesn't work right, they'll complain rather than try to fix it themselves.
- nir 18y agoI think this is related to Ruby in the sense that there aren't that many Ruby coders. The whole "scratch an itch" thing is a numbers game - maybe %1 of the people who have a problem would actually contribute a patch that fixes it, so the more people use a language/project the higher the chance the original author would get some outside help. As for newbie devs, I'm not sure I agree... as a non-newbie, I still like to get a solution that works. I might be able to dive into the code and fix it, but I don't want to do this - I prefer to focus on my app rather than figure out why certain libraries don't work. (For some reason this view seems to be common in Ruby. A prominent example was the web server - until Passenger came along (surprising everyone) you were supposed to figure out how to deploy with lighttpd, then mongrel - instead of simply working with Apache which most of the world already knew how to install, scale and tune.)
- mattmcknight 18y agoI think the reason it's a Ruby problem is the c - extensions to Ruby are hard to cross compile across platforms. Windows is a particular problem because the c compiler situation is not consistent. There are still a lot of people using Visual Studio 6 to compile this stuff.... As far as deployment goes, when you can run Windows services for the mongrels, do you even need capistrano? I've been doing Rails for years without it and don't feel like I need help deploying....
- nir 18y agoIsn't the C extension issue the same for other languages, eg Python or PHP? (I really don't know, I'm not that familiar with Ruby internals) I think this issue, like Capistrano's, would benefit from having more Ruby coders, which in itself might require a more newbie-friendly approach from the community. (BTW I hope it doesn't seem like I'm criticizing Jamis' choice - actually I think he's doing the right thing in the current situation, just that if there were more Ruby coders around he might not be forced into choosing this path)
- catch23 18y agoThe C extension issue in Ruby is the same as Python afaik. There probably aren't as many windows developers using Ruby though.
- mpk 18y agoIt's also a problem with Windows itself. It really is a nasty environment for coding non-MS-based software on. If I want to support Windows I have to setup a (virtual) machine with a license code just to have any basic functionality. As someone who doesn't work with Windows anywhere, this is a huge hurdle. Then there's the hoops I'd have to jump through just to get a decent shell and a compiler ready. Oh, but the fun doesn't end there. Which version of Windows are we talking about? More than one? Ah, well, each of these will require its own machine (virtual or otherwise). With matching keys, of course. Supporting Windows is a pain and when it's not required for what I want to do, I'm simply not going to do it. Period. I have better things to do with my time. Letting people who want this code running on Windows do it themselves and having them submit patches upstream is a perfectly valid choice.
- Maascamp 18y agoWhat if I'm an anything else coder and I want to support Mac? Forget license, I need to buy a new machine. Linux is the only really painless platform to support if you're not using it.
- Niten 18y agoBut if you support any sort of *nix, then you quite possibly work on OS X already. If not, there's still probably minimal work to do. It's not like going from Unix to Windows, where you have an entirely different access control mechanism, system API, filesystem structure and path separator, etc.; it's just going from one Unix to another. So the author only has to accept a couple patches from his Mac-using colleagues, and then he's basically set for OS X. On the other hand, debugging a Unix app on Windows can become a full-time job, and may be more work than you can reasonably expect a few random patch contributors to accomplish.
- petercooper 18y agoI recently had an e-mail from a Windows developer in the Ruby community who pointed out how opaque many Ruby projects are regarding Windows. He works on porting a number of libraries - so he's definitely putting in some hard work - but has had issues with project owners not updating CHANGELOGs properly, deliberately breaking Windows support, etc. At Euruko (European Ruby conference) earlier this year, I raised the topic of Windows and.. most of the audience couldn't care less. They were mostly of the opinion that if Windows people wanted to use Ruby, they had to do the legwork. (FWIW, I'm an OS X user who doesn't care too much for Windows either, but I recognize there's a massive userbase there) Windows is in the third-world of operating systems when it comes to Ruby - so Jamis' standpoint is less than surprising.
- petercooper 18y agoFor what it's worth, these issues affect users of alternate implementations generally, such as JRuby.
- thwarted 18y agoNot updating changelogs is one thing that might be forgivable, but deliberately breaking things so that a specific platform isn't supported is pretty serious and a pretty serious alegation. Which projects are these, and how was Windows support broken?
- petercooper 18y agoAlas, I can't point fingers regarding things that I don't fully understand (I'm not a Windows developer or related to the projects claimed) - commentary is as good as I can do on the Windows side and I cannot quote e-mails without permission. One project that was mentioned, however, was DataMapper. However, once I've investigated the claims, have permission, and got more of a story together, I'll be posting on Ruby Inside about it. There may or may not be a story, of course :)
- qhoxie 18y agoOuch, are you speaking about the 0.9.8 update? I have on fairly good confidence that there was nothing deliberate, but I'd be interested to hear what has been said on your end.
- jeckel 18y agoPeople who receive free software really have no right to complain about it, if it isn't working as they want it to. They didn't pay dime for it. Either donate money to the project or scratch your own itch. It's not the job the the original developer to spend all of his/her time fixing other people's problems.
- silencio 18y agoIt's really surprising how many people don't understand this. I hang out in a support channel for an open source app, and people are downright offended when I tell them that whatever feature they want they'll have to implement themselves because all the people capable of working on the project are uninterested or too busy to do anything, and there's a longer list of more important fixes/features that are wanted. Not just a "oh, I understand", but an outright "what the fuck? I don't know how to code", "this 'community' is BS", "what a frigid bitch..." and more. All because I told them that the app was open source so they should consider doing it themselves. (Funnily enough, there's a competing app that is not open source or free, and they're still not doing a great job of updating the app and adding requested features for paid customers either..) Anyway, my two cents is that people shouldn't expect donations to make the developer(s) scratch their itches. A donation is a donation. Maybe some devs and projects would be more willing to look into things for you after one, but unless they explicitly have such a policy, I wouldn't expect it to happen.
- extension 18y agoThis is a terrible attitude and one that I'm fairly certain is not shared by the best open source developers. If you publish some code and go around claiming it does this and that, you are absolutely responsible for making good on those claims. Your reputation is at stake. How much you are getting paid is irrelevant. Besides, there are plenty of indirect ways to profit from making free software. Also, there are implicit claims in every piece of software that doesn't say otherwise, namely that it is secure, won't trash your data, follows best practices, is not full of bugs, etc. If you want to publish "as is" software, that's fine, but it should be made explicity clear to what degree you stand behind the quality of your code. Users have no business complaining because you won't add some feature they came up with or your pre-release version isn't solid. But it is quite reasonable to complain if an open source project does not live up to its own pretenses.
- dcurtis 18y agoI have an honest question: Why does anyone want Ruby to run on Windows? The cost of switching to Ubuntu and running Ruby there is probably way, way cheaper than rewriting all the libraries to work on Windows. I don't understand why this is even an issue.
- derefr 18y agoI want to write actual executable client software for home users, rather than servers. Specifically, I want to write a game. I want to do it in Ruby. However, all the "home users" that will play it, use Windows.
- cglee 18y agoCan't you develop it on *nix and run it on the JRE via JRuby?
- run4yourlives 18y agoBecause for ruby, asking a developer to convert not only to your language, but his whole platform as well is going to seriously hinder your adoption rates. Not caring about adoption rates is another story altogether.
- nir 18y agoYou know, not to flame, but this attitude is exactly why Ruby isn't where it could be. I love Ruby, do most of my work in it now and haven't owned a Windows machine since 2001, but if Ruby's answer to Windows users is "just switch to Ubuntu" it's not surprising they decide to just choose another language.
- fendale 18y agoMany developers have no choice but to use windows thanks to corporate policy ... I am not saying that is a good thing, but its the way it is (at least where I work). I resorted to doing Rails dev using Emacs + Putty, which was easier than developing the app on windows!
- ddemchuk 18y agoEven better, run andLinux inside of Windows I can't give up Photoshop for the type of work I do and I can't afford a macbook yet so I just installed andLinux and have all of the abilities of Rails and Linux while still using Windows. All you really need for Rails is the command line, I use Intype in Windows for my editor and I am cruising. andLinux only uses about 100mb of a RAM at any given time so it's barely noticeable when it's running in the background.
- gojomo 18y agoIsn't it kind of obnoxious how Google requires a login to read public group archives? (Or am I mising a way to read these without logging in?)
- hopeless 18y agoI don't think RoR is that bad on Windows. I've used InstantRails on Windows quite successfully for over a year now with only occasional problems with plugins (like Paperclip, though it's fine now). It seems the incompatibilities come from things like capistrano which are quite close to the metal. And that seems reasonable to me. However, expecting new users of your language/framework to delve into the internals just to make their basic app work isn't going to happen. Maybe it should, but it isn't.
- charlesju 18y agoI don't understand why people on windows just install Wubi. It dual-boots into Ubuntu (a MUCH better OS anyways) and the whole database is stored as a file so you don't have to fiddle around with hard drive partitioning. Or you can just pop VMWare on your computer and have linux running in no time flat. If you're using Windows to develop for RoR, you're just lazy and you don't deserve to be supported.