HI Max, It's precisely because you're a nobody that makes you the ideal candidate for giving advice on how to shape the framework. You're actually a developer's best friend - whether they treat you as such or not, because you're FRESH.
They're really good suggestions you have. I hope they're taken on board. It'd make the framework much nicer, and actually much nicer than Rails is at the moment, too. I have to say that Merb *is* a framework (ie a set of code, but not a product), and while Rails attempts to grab people who have no experience in anything - let alone Ruby or web app development - Merb is definitely targeted at the slightly-more-mature and a slightly-more- discerning Ruby developer. Thanks for not giving up hope, though :) You'll find that persistence, and continually stripping back your assumptions are the best assets you could ever have (for instance, you thought you had Mongrel installed... I've spent countless hours on similar circular-tracing of an issue before I realise that one or more of my assumptions was fallacious: this is something that not just noobs do). These days I know enough to fairly quickly re-check my assumptions down to the lowest level I can. Julian. On 26/10/2008, at 6:21 PM, maxbaroi wrote: > In all likelihood these ideas aren't implemented because they're > terrible. Like I said in the beginning, I'm an ignorant nobody. But if > I do get an idea of something to add to an error message, I'll be sure > to post it here. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
