Blogs : Archives
|
|
| < (April fool) RIFE re-implemented in Ruby to boost productivity | OpenLaszlo 3.0b2, two weeks later > |
|
During the recent Rails slashdot post that refers to a blog post that once again manages to compare totally different application stacks and draw conclusions out of it, someone referenced the out-of-context micro code comparison that was done about Bla-bla List and casted once more a collection of unbacked criticisms. I tried to clarify a few points and guess what, someone else (I guess Matt McRay, but he wasn't man enough to use a real name) just nicely summarized all the criticisms that I got about Bla-bla List from Rails users. Somehow they seem to feel hurt by the fact that I tried to show Java developers that Java can be concise too without lots of setup and configuration files. This is the post with my in-lined answers. Since it'll probably get lost on slashdot and I want Java people to read them, I repeat it here. I love Java and the recent Rails buzz blows a lot of things totally out of proportion, I just want to blow back a bit: They saw it, Geert. And they were dully impressed, but you didn't really do what you said you'd do.
Yes I did exactly what I said I'd do and a lot more. I keep having to explain things over and over again to you Rails activists, but you seem to be unable to understand anything that is only just slightly different from the concepts that you use. 1. You used Lazlo. Your templates are 10x bigger than Tada lists. You may not count this, and that's great for you, but it's still code you have to maintain. If you were to add Tada's templates in with the count, the code count wouldn't go up nearly as much as Bla-Bla's would.
So you're saying that you actually manage to look elsewhere than the src/templates directory? You look in the web directory instead and call .lzx Laszlo files, templates. Even though they have nothing to do with templates? They are a SEPARATE application, and everything in Bla-bla List can be done without it. Oh, and btw, Ta-da Lists's template line count was not taken into account into the 600 lines, so stop whining. Rails' templates contain logic and loops, RIFE's not. I actually included those loops in the line-count instead of leaving them out. 2. You didn't implement Ta-da list. You implemented something kinda like Ta-da list optimized for RIFE. Were Ta-da list to be rewritten as a standalone app leveraging the current Rails (instead of being ripped out of Basecamp and used as a marketing tool for it)? 340 lines. Don't believe me? Check out taskTHIS! (and source*).
You guys continue to amaze me, so you write an even more simple to-do list with Rails that does some Ajax eye-candy and only does account management and list editing. Let's take a look about what's missing, will ya:
and you still manage to let it be a hefty 340 lines in your awesome concise framework? You just confirmed that you never take the time to check ANY of your statements and just troll on senselessly in the direction of whoever is leading you. SAD! Btw, I'd wouldn't call Bla-bla a RIFE-optimised application at all. Quite the contrary in fact, almost nothing is used of the important features of RIFE. The application is so simple that you never get to leverage any of the benefits since there's never any data flowing around. They are all single actions. I'd rather call Ta-da optimized for Rails since you have your List Act which does all the list handling automatically in the framework. We don't consider CRUD operations a core feature, but will soon release RIFE/crud as a separate package that addresses this without any code generation. Bla-bla List doesn't use any of that btw. 3. You have to maintain your configuration, but you fail to mention that massive size as well. In rails there is almost none.
Which configuration? This is what you call configuration? I hate to bring it to you, but that is not configuration. It's separation and declaration of the application's logic and data flow which brings an enormous collection of features that you wouldn't even understand since you marvel at your pityful one-dimensional controllers. Once more, you seem to be totally deluded since I DID COUNT the lines of that file in the final line count. I checked before with my friend Brian McCallister, who knows Rails quite well, to see if I should include it. I'm still not that sure I should have since the features it gives you are completely impossible to do with Rails. If you're interested in that, start using a real name, be a man and we'll have some extensive chat about that elsewhere. [*]Please don't make too many comments about the quality of that code, it's a demonstration. It is not as perfect as it could be, and that works for and against it. It probably could be smaller, it probably could be more bug free.
Oh, don't worry, I don't comment on your code with micro comparisons as Rails activists seem to love to do. I do comment on the fact that you only implemented 15% of the application and did none of the complicated stuff. /golfclap you just made a total jerk out of yourself. So yeah, Geert. You won a contest you yourself made, set the rules for, and gamed appropriately. You are now eliagable for a cookie.
Last time I checked, I didn't win the contest (since I came out 300 lines more). More even, I never did a contest since Ta-da's code is nowhere to be seen. All I did was show Java developers that Java can be concise and doesn't have to be totally convoluted. Which rules did I set?
Please stop wasting my and other people's time with accusations that are totally unfounded and unresearched. |
|||
Comments |
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
Add a new comment |
|||
| Comments on this blog entry have been closed. |
| < (April fool) RIFE re-implemented in Ruby to boost productivity | OpenLaszlo 3.0b2, two weeks later > |


