Muz
2008/9/16 rarepleasures <em...@acgreen.co.uk>:
I'd love to see a fair comparison between frameworks in other
languages and typical ruby frameworks ( Rails/Whatever ). I've seen
just one django/rails comparison till date. None between
seaside/rails. I think there is plenty we can/should learn from the
framework world outside ruby.
Instead of doing a "Merb vs Rails" talk, it'd be rather interesting if
we get some django guys and do a "django v/s rails".
--
Cheers!
- Pratik
http://m.onkey.org
One the one hand, I'm 100% behind what Pratik says. I've not found
anything particularly novel in any of the other ruby frameworks. I
like the fact that there's more than just rails (IMO the best thing
Merb has done is reinvigorate Rails development), but for an
interesting talk we'd need to look much further than just ruby
frameworks. Maybe that would fall outside the scope of Ruby Manor?
Tom
>
> Honestly, I'm so sick and tired of hearing about "alternative" Ruby
> frameworks - They are all pretty much the same shit but in different
> packages, and with stupidly minor differences made just to look cooler
> in the rat race.
Please tell me there's something better than ActiveRecord out there!
Coming from C# / NHibernate and being a TDD-aholic, AR is driving me
insane.
I'd like to see a comparison of ORMs for ruby - that would float my
boat.
cheers,
Matt
----
http://blog.mattwynne.net
http://songkick.com
In case you wondered: The opinions expressed in this email are my own
and do not necessarily reflect the views of any former, current or
future employers of mine.
Here are a few bods in the UK who have Rails and Django experience:
http://www.google.co.uk/search?q=site%3Aworkingwithrails.com+United%2BKingdom+Django
Volunteers? :)
While you might be right, this is just an assertion, an a
controversial one at that! Maybe you could give a talk: "why there's
no point looking at other web frameworks beyond rails", to convince
everyone else? I'm quite serious.
> I'd love to see a fair comparison between frameworks in other
> languages and typical ruby frameworks ( Rails/Whatever ). I've seen
> just one django/rails comparison till date. None between
> seaside/rails. I think there is plenty we can/should learn from the
> framework world outside ruby
>>
>>
>>
>>>
>>>
>>>>
>>>
>>>
>>
I think your last point is the most interesting: I do wonder why you
are sure there's no innovation in other Ruby frameworks, but I'd
always be keen for someone to point out useful insights and techniques
from *any* source that I can use in my own code.
I'm far less interested in a Rails vs. Django talk, because I'm not
coming to Ruby Manor to choose a new web framework. I love Ruby, so
hearing 'Django/Seaside/Erlyweb is better at XYZ' isn't terribly
helpful unless there's also discussion about how we can bring those
benefits to a Ruby tool.
Hope that makes sense; it's not that i hate other languages, I'm just
keen to hear about Ruby.
James
So
+1
On James comments
> While you might be right, this is just an assertion, an a
> controversial one at that! Maybe you could give a talk: "why there's
> no point looking at other web frameworks beyond rails", to convince
> everyone else? I'm quite serious.
I've never given a single talk, ever. So while it's easier to write an
email, talk in person, I'm *really* scared of presenting to a large
audience. Apart from that, I'm not 100% sure if I'll be in London
during November. And also, I wouldn't say that there's "NO" point in
looking at other frameworks. I use Sinatra quite a bit and love it.
Same for custom Rack handlers.
> I think your last point is the most interesting: I do wonder why you
> are sure there's no innovation in other Ruby frameworks, but I'd
> always be keen for someone to point out useful insights and techniques
> from *any* source that I can use in my own code.
>
When I say there is no innovation, I am really talking about the
public facing interface of these frameworks ( Rails/Merb/Ramaze ) and
not how they do things under the hood. And if you have a quick glance
at http://ramaze.net/features and http://merbivore.com/features.html -
I think it's quite apparent that while they all may have minor
differences, there is nothing ground breaking going on there, if
compared to Rails.
> I'm far less interested in a Rails vs. Django talk, because I'm not
> coming to Ruby Manor to choose a new web framework. I love Ruby, so
> hearing 'Django/Seaside/Erlyweb is better at XYZ' isn't terribly
> helpful unless there's also discussion about how we can bring those
> benefits to a Ruby tool.
Of course. As I said in the first email "I think there is plenty we
can/should learn from the framework world outside ruby.". Probably, I
should have put more emphasis on that. I want to hear more about
comparisons and innovations in other language frameworks *only and
only* to bring the benefits to the ruby world.
I should also state that my idea is inspire by these two talks from DjangoCon :
http://www.youtube.com/watch?v=fipFKyW2FA4&
http://www.youtube.com/watch?v=i6Fr65PFqfk
( worth watching )
> Hope that makes sense; it's not that i hate other languages, I'm just
> keen to hear about Ruby.
Well, I'm more interested in hearing things I don't know about. It's
very likely that most of the people doing Merb/Ramaze, are also doing
Rails. And most of the people doing Rails, have played with Merb etc.
And this makes me very skeptical that I'll find out anything new from
attending a Merb v/s Rails talk.
> James
As someone who's only worked with rails so far, I'd love to know what
life is like on the outside.
Maybe you could work with someone else to prepare a talk and have them
give it? Ben Griffiths has already suggested this sort of
collaborative effort (albeit for different reasons) and I think it's a
great way for people to participate if they don't think they'll be
able to give a talk for whatever reason.
In your case it sounds like Tom is in agreement with you about wanting
to look to frameworks written in other languages, so maybe the two of
you could work on something covering that angle together? Or, if you
think there is some merit to James' suggestion about "why there's no
point..." it sounds like you've already put in a lot of the up-front
effort to evaluate the existing ruby web frameworks so you could pass
on your knowledge about them to someone else and create a talk around
that?
Muz