I agree with Brian. Samo, you don't have to read the rails source code, and you actually probably should not until we are almost done :p Because of the new modularity and the public API, the code will be cleaner and easier to read.
You need to look at rails 3.0 as merb 2.0, merb 2.0 would have required a lot of work and major modifications to the code. You would have to read the new source code anyway, so you are not going to waste time. I think people have a hard time looking at rails 3.0 as something different that another rails 2.x, you trusted us until now, please keep us trusting us and you will see, you won't get screwed over. - Matt p.s: Merb 1.0.7 should be released soon On Thu, Dec 25, 2008 at 11:36 AM, Brian LeRoux <[email protected]>wrote: > > As a person who makes these sorts of tech decisions I far prefer a > rough measure of quality over fictional dates. Sure, goals are good -- > but test suites around a migration plan is going to be build my > confidence more than business truisms about community and make believe > timelines. > > > On Thu, Dec 25, 2008 at 11:25 AM, Samo Korosec <[email protected]> wrote: > > > > Just a sidenote: some people don't have the time to read the merb and > > Rails sourcecode 3-4 times over and there are certainly bosses who > > would not tolerate something like that at all. Some may be lucky to > > have an environment like that, but a lot of people don't. It's > > understandable that they want to save as much time as possible, > > especially if the learning has to be done partly in their spare time. > > > > I don't find it strange that people who want to use and propagate merb/ > > Rails are also cautious to not have it leave a bad impression in their > > organization. Starting with something and having to re-learn it afresh > > in 6 months is not something people look forward to and less something > > that would impress a manager who's commiting to merb starting now. > > > > I'd suggest the merb/Rails core team picks a rough date by which they > > will announce their merging plans and the suggested roadmaps and > > timeline that the users can use with their planning and refer to that > > whenever questions arise. > > > > Samo > > > > On 25 Dez., 18:20, Michael Klishin <[email protected]> > > wrote: > >> On 25.12.2008, at 9:54, MyMerb wrote: > >> > >> > What should i do now... Should start learning Rails books from scratch > >> > or stick to my Merb collection/Tutorials and spend more time to master > >> > it...? > >> > >> Same old song from same singer, MyMerb. You should *learn* and not > >> worry about stuff that does not matter. Rails 3 is almost half a year > >> away, maybe you will be working with something completely different by > >> then. > >> > >> In 6 months you can read the whole Rails and Merb sources 3-4 times > >> each, collect a bunch of questions and ask them a couple of times. Do > >> so and you will be a way better hacker than vast majority of people in > >> the industry. > >> > >> MK > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
