Ruby performance woes
in [Lisp]
|
Prev: comp.lang.lisp charter
Next: Casio Collection Men's GOLD LABEL Edifice Watch - Replica Watch Fake
From: Brian Adkins on 23 Apr 2008 08:35 On Apr 22, 10:51 pm, Ken Tilton <kennytil...(a)optonline.net> wrote: > Brian Adkins wrote: > > On Apr 22, 3:52 pm, Ken Tilton <kennytil...(a)optonline.net> wrote: > > >>Scott Burson wrote: > > >>>Just came across this... > > >>>http://www.regdeveloper.co.uk/2008/04/21/bray_ruby_rails/ > > >>>You'd think there would be some way for Lisp to fill this gap. > > >>http://gitorious.org/projects/hunchncells > > > "Yet another web-framework. This one uses cells and XMLHttpRequest to > > create dynamically updating models on the server that update their > > state on the client. > > > The dynamically updating bit isn't working yet but hopefully we'll > > have it working by the time anyone notices this." > > > Too late. > > Not for my killfile. But thanks for noticing! No need to get all sensitive. I just thought it was odd that your proposal for a web framework to "fill the gap" was a framework whose reason for existence seems to be the ability to "create dynamically updating models on the server that update their state on the client", and that's the part that's not working which begs the question ...
From: Andy Chambers on 23 Apr 2008 08:47 On Apr 23, 2:29 am, Brian Adkins <lojicdot...(a)gmail.com> wrote: > On Apr 22, 3:52 pm, Ken Tilton <kennytil...(a)optonline.net> wrote: > > > Scott Burson wrote: > > > Just came across this... > > > > http://www.regdeveloper.co.uk/2008/04/21/bray_ruby_rails/ > > > > You'd think there would be some way for Lisp to fill this gap. > > >http://gitorious.org/projects/hunchncells > > "Yet another web-framework. This one uses cells and XMLHttpRequest to > create dynamically updating models on the server that update their > state on the client. > > The dynamically updating bit isn't working yet but hopefully we'll > have it working by the time anyone notices this." > > Too late. Actually it is working now. I'll go and update that bit of the description now. -- Andy
From: Robert Uhl on 23 Apr 2008 11:31 Sean T Allen <sean(a)monkeysnatchbanana.com> writes: > > given the emphasis in the ruby community on beautiful looking code, i > can also see problems for lisp there. Have you _seen_ Ruby code? It looks like what one would expect if Perl caught syphilis. It's painfully ugly. I'll grant that Lisp parens aren't pretty either, but once they disappear Lisp is awfully easy on the eyes. -- Robert Uhl <http://public.xdi.org/=ruhl> But never forget that the original Dilbert strips were nature studies. --Shmuel Metz
From: Didier Verna on 23 Apr 2008 11:41 Robert Uhl <eadmund42(a)NOSPAMgmail.com> wrote: > Have you _seen_ Ruby code? It looks like what one would expect if Perl > caught syphilis. It's painfully ugly. I'll grant that Lisp parens > aren't pretty either, but once they disappear Lisp is awfully easy on > the eyes. I guess the uglyness in Ruby also disappear for people programming Ruby all day long. The same goes for offside-rule based languages like Haskell or Python. You can't really make an argument out of that. You have to get used to a language before starting to complain about it. But I agree; Ruby code is ugly ;-) -- 5th European Lisp Workshop at ECOOP 2008, July 7: http://elw.bknr.net/2008/ Didier Verna, didier(a)lrde.epita.fr, http://www.lrde.epita.fr/~didier EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (0)1 44 08 01 85 94276 Le Kremlin-Bic�tre, France Fax.+33 (0)1 53 14 59 22 didier(a)xemacs.org
From: Sean T Allen on 23 Apr 2008 12:06
On 2008-04-23 11:31:17 -0400, Robert Uhl <eadmund42(a)NOSPAMgmail.com> said: > Sean T Allen <sean(a)monkeysnatchbanana.com> writes: >> >> given the emphasis in the ruby community on beautiful looking code, i >> can also see problems for lisp there. > > Have you _seen_ Ruby code? It looks like what one would expect if Perl > caught syphilis. It's painfully ugly. I'll grant that Lisp parens > aren't pretty either, but once they disappear Lisp is awfully easy on > the eyes. I've programmed a ton of it. The people who use it think that it is very beautiful. Your asthetic aside, it would be an issue as very few people find lisp and ruby asthetically pleasing to look at. Usually its one or the other. Case in point, you. Or all the people who mention how ugly lisp is when it comes up on the ruby mailing lists. |