Will My efforts go wasted, if i invest in Merb 1.0.6 Now...

[MyMerb]

Hello,

I am sorry for my newbie question. Today i find myself at a stage
where i am confused a bit. For many reasons, i started investing my
time and efforts in learning Merb, despite very books are available
and less information is available.

But... I loved Merb. and Now Merb becomes Rails 3.0.

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...?

I am willing to work with Merb for ever, but i do not want my efforts
to go in dustbin after few months. I have already invested my time in
" MERB " collecting details from everywhere.

Pl. take care of me and guide me in the right direction, so i can move
confidently ahead.

I am expecting answers from Yehuda, Matt and other experts, who can
really understand my problem.

Thanks

[Julian Leviston]

As always, you're better off learning both frameworks, but not at the
same time. Learn one first, then the other... you'll be a better
programmer because of it.

From
Julian.

[Yehuda Katz]

MyMerb:

If you want to learn Merb for modularity and power that is not currently present in Rails, stick with Merb. We'll provide a good upgrade path to Rails3 (and feel free to contact me personally to keep me honest on that promise), and you'll have a leg-up when the same power makes its way into Rails. While Rails3 will still be very similar to Rails2 for current Rails users, it will look a lot like Merb for those users who are currently drawn to Merb.

Wondering how we'll pull of that magic trick? Stay tuned!

-- Yehuda

--
Yehuda Katz
Developer | Engine Yard
(ph) 718.877.1325

[Samo Korosec]

On 25 Dez., 09:38, "Yehuda Katz" <wyc...@gmail.com> wrote:
>
> Wondering how we'll pull of that magic trick? Stay tuned!

Method chaining? :oP

Samo

[Michael Klishin]

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

[Samo Korosec]

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 <michael.s.klis...@gmail.com>
wrote:

[Michael Klishin]

On 25.12.2008, at 22:25, Samo Korosec 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

Yet, some people develop
virtual machines and operating systems in their spare time. And some
consider learning a damn small web framework in Ruby "a time consuming
thing".

Come on Ruby web developers, learn something non-Ruby already and you
will find, web development is the same it used to be 10 years ago:
learning merb means you already know most important things about
rails, django, pylons and variety of Perl frameworks.

MK

[Brian LeRoux]

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.

[Yehuda Katz]

Just to be clear, I think antares is being his usual self: telling people how to be awesome hackers. We absolutely share your concerns about transition and I have addressed them several times.

We will be starting work on a public test suite for ActionPack very very shortly. Feel free to follow along as we go :)

-- Yehuda

[Matt Aimonetti]

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 <brian....@gmail.com> wrote:

[Samo Korosec]

I know, I was just trying to explain the motivations behind some of
the nervousness.

I'll just continue with merb for the next 6 months or so, and set
aside some time for a possible migration later on and I don't expect
it will be a big one. Worst case I stay with merb, which is fine
enough for my needs as it is. :-P

[Matt Aimonetti]

Samo: fair enough.   However I strongly believe that in 6 to 9 months, you will really want to migrate to Rails 3.0 to get all the stuff we promised will be in Merb 2.0

One thing I believe most merbists will want is better perfs and better slices. Even though I can't promise anything yet, but with the focus on Rack, refactoring and the two teams working on modularity and performance, I really expect Rails 3.0 to be super attractive to all the Merb developers :)

- Matt

[Jon Hancock]

all I want is for merb 1.0.x to be refined and get the bugs out.
I don't have much love for slices or any other form of plugin.
I just want a simple, consistent, extremely well-tested API.

I cannot think of anything in merb 2.0 that I was holding my breath
for.

Jon

On Dec 26, 6:21 am, "Matt Aimonetti" <mattaimone...@gmail.com> wrote:
> Samo: fair enough.   However I strongly believe that in 6 to 9 months, you
> will really want to migrate to Rails 3.0 to get all the stuff we promised
> will be in Merb 2.0
>
> One thing I believe most merbists will want is better perfs and better
> slices. Even though I can't promise anything yet, but with the focus on
> Rack, refactoring and the two teams working on modularity and performance, I
> really expect Rails 3.0 to be super attractive to all the Merb developers :)
>
> - Matt
>

[Matt Aimonetti]

Merb 1.0.7 should be released this week with merb_sequel 1.0

-Matt

Sent from my iPhone