Hacker News Reader

Comment by functionform | Hacker News Reader

After everyone saw how it easy it was to write your own blog in Rails, everyone ... used Wordpress anyway.

The Rails use case was always truly limited. I still don't know any application that achieved maturity and stayed coded in Rails. For a while that was Twitter, but then they started moving stuff over the jvm.

Node will probably end up in a similar way, because at the end of the day no one wants to manage thousands of lines of Javascript (or any other language that doesn't enjoy the benefits of a statically typed ide).

View on HN

1) Meh on node. I don't really see the advantage of using node aside from specific and well defined performance requirements. It's ironic to be saying this coming from Rails, but it seems like Node's toolset is somewhat immature. Is there a good way to use plugins in Node? There must be. Anyhow, server side? Meh.

2) That said, Javascript isn't going away. We will all be managing thousands of lines of Javascript because… that's where applications are going - client side. Good luck convincing all the browser vendors to swap.

Anyhow, I know you're just trolling but you have to up your troll game - 98% of apps fall in between "toy demo" and "twitter".

In my experience with Ruby development (2 years), I have never, ever experienced a single issue caused by duck typing. Static typing is great for performance, but it has nothing to do with being able to maintain a project.

Have you worked with more than 5 developers on a rails project? I ask because all the problems I've had with dick typing appear around interfaces between code from 2 programmers, and 5 seems to be the threshold where communication starts to break down.

What kind of problems do you genuinely have with a dynamic language/duck typing?

Like, that you've actually experienced and said "You know, I'm not saying this just because I'm not used to it. This bit right here is a design flaw".

This is such a tired and boring argument by this point, but I'm willing to entertain it because duck typing is at the bottom of my list of worries.

The "Blog in 5 Minutes" demo was just that, a demo. It was a showcase of how easy it is to create simple CRUD apps in Rails as compared to competing frameworks (or DIY stuff) of that era. Even today, it remains a decent beginner's example that touches on many aspects of MVC.

I don't think you really believe a web development framework and a feature rich blogging product were actual competitors but are simply creating strawmen to support your view. Drop the crap.

Reply on news.ycombinator.com