Hacker News Reader

I think it is unfair to single Ruby out here and call it a "flaw". What you are describing is just bad code/design that can exist in any language.

Also, as far as Ruby is concerned your class's external API is only made up of methods. There are no attributes, model.foo is always a method. Because of this your long running or resource intensive methods need to be documented or have clear names if you are exposing them as public API. In other words: Model.foo shouldn't take 30seconds, but maybe Model.download_foo will.

>What you are describing is just bad code/design that can exist in any language.

Actually the problem he is describing is a consequence of language design, not of architecture design.

In Javascript, if I write foo.bar, I know that it is accessing some field of the foo object, and that's it. Unfortunately we're going to get a bunch of stuff in ES6 that's going to change this, but the fact that we can have some invariants (especially in a dynamic language like Ruby) on property accessors is pretty important when trying to reason about performance.

The fact that Ruby only exposes methods is a language design decision that can enable some pretty bad architectural decisions.

Language features are about tradeoffs .For example, among other things, the calling syntax for ruby means that point-free functional programming is pretty much impossible (though there are possible language-level solutions for this). Depending on what you're looking for, that can be considered a flaw , because it deviates from your personal definition of the ideal programming environment.

It's interesting that you mention Javascript. There was recently a post on CoffeeScript that hit the frontpage, and one reference it linked was to a point of contention between CoffeeScript's developers and a library creator over whether CoffeeScript should introduce a nontrivial amount of wrapper code to support attribute setters and getters [1]. The library author made the following argument:

    For CoffeeKit specifically, the getters for all accessor 
    properties are totally without side effects. They are getters 
    because they have to wrap access through objective-c selectors. 
    I can't make them fields. I also can't in good conscience 
    make them all functions, requiring people to write:
    
    uikit.UIScreen.getMainScreen().getBounds()
    
    instead of:
    
    uikit.UIScreen.mainScreen.bounds
    
    yuck.

This, however, speaks directly to the point at hand: one could argue that a library creator in good conscience should make them all functions, since it would force library users to "reason about performance." It's tempting to remove extra syntax whenever possible, but sometimes verbosity can reduce technical debt insofar as it encourages developers to think about performance.

Ruby on Rails definitely leans towards reducing verbosity, but it has such a good ecosystem that even though I'd like a platform that makes things a bit more apparent about what things have/don't have side effects, it's still the best option for many projects that need to be created fast and maintained into the future. I'm looking forward to ES6 generators in Node.js, since they promise to create an ecosystem that avoids "callback hell" but still make it explicit where, in each level of code, expensive operations might occur [2].

[1] https://blog.toshokelectric.com/why-im-ditching-coffeescript... [2] http://zef.me/6096/callback-free-harmonious-node-js

I don't get it. They're both methods. There's no such thing as "attributes" in Ruby.

Sorry, perhaps I wasn't clear enough. On an ActiveRecord model you will have attributes that are simple values in a table and you can have methods on an object that do stuff. They might both be methods, but the difference between getting a simple attribute and doing a calculation can be incredibly huge once you have models related to other models and calculations that span between them.

In my experience ActiveRecord doesn't handle that particularly well and programmers don't readily know/see the difference because they all look the same, especially in a view.

This has nothing to do with ruby. In any language you can have a method that returns an attribute or a method that calculates something.

> One of the biggest problems in ruby is that there is often no clear difference in code between a method and a variable.

The only even superficial ambiguity is between calls to methods on the current object and local variable references.

> For example, you can have a Model.foo method that seems harmless enough, except that actually calls other methods on other models to do some calculation that maybe two or three layers deep makes a call to an external service.

That's not a lack of clear difference in code between a method and a variable, since when its referenced in external code its unmistakably a method, not a variable reference (its quite awkward to reference an object's variables from outside in Ruby). Its that Ruby is doesn't have syntactic conventions which imply things about the implementation of methods (the way, e.g., C# has with properties, which are simply a gate way to call methods, though there are fairly strong -- though not universally observed, and therefore dangerous to rely on -- conventions about what the underlying getter and setter methods should and should not do.)

Personally, I think Ruby's way is the right way if you don't have strong and language (e.g., compiler) enforced guarantees.

Hm, would you also agree that it is a flaw of Haskell that there is no difference between a value and function with no arguments in Haskell?

The syntactical equality between a variable and a method call on self has the advantage to make things like this possible. E.g. if i have:

    foo = DataBase.lazy_load(:foo)
    do_something_with(foo)

can easily be refactored to

    def foo
      DataBase.lazy_load(:foo)
    end

    do_something_with(foo)

I think that to be a strong-point of the Ruby language, speaking about values and not about the technicalities. Also, every external access to a value has to happen through a Method.

Also, you are complaining about the Rails API more than anything else. E.g. in DataMapper, it was quite obvious that those attributes do hard work (e.g. coercion), because you had to explicitly define them in the first place.

There's no such thing as a function with no arguments in Haskell.

f :: () -> T is a function that still takes a (meaningless) value

g = map f list is just a value.

An (IO a), or even more so, a (State a) or (Reader a) very often seems exactly like a function with no arguments in any imperative language.

Thats what I meant, everything is a function and can be expressed as one, even most syntax (the literal 1 => Num a -> a)

Its all about abstraction.

If you're calling Model.foo or Model.bar, you don't care about the specific implementation, you just want foo or bar.

The calling code doesn't need to know how Model works.

This way you can refactor either ones into normal attributes down the road without changing any dependant code.

Perhaps, but the simple habit of Model.foo() (for methods) and Model.bar for data would make it easier to spot when one is an attribute and one is a method.

RubyMine at least will complain if you put the() after a method that doesn't need it. Coming from C# that lack of differentiation kind of irks me.

Any performance issues (which you brought up before the edit) should be entirely the concern of the class whose method is causing the issues. Anything on the outside shouldn't have to rely on syntactic clues to discover when something may be slower.

If I care to call person.eye_color, I don't care (as the caller) how Person implements eye_color (it may be a simple attribute or do some ridiculously slow color calculation) - if I need the color, I need the color. Now, that's not to say that performance doesn't matter, just that any performance concerns should be addressed in Person, not in trying discourage caller from calling eye_color and trying to get at that value some other way.

That seems to fit the definition of leaky abstraction (an implementation detail influencing whether how you use it). Leaky abstractions are all over.

That same logic would suggest that we should name our methods Model.foo_slow() and Model.bar_fast() because the execution speed is important and should be transparent to the caller.

In practice, Model.foo() ends up often being memoized so that all but the first call are practically equivalent to accessing an attribute.

This won't work because it is not refactor proof. What happens when your system changes and Model.bar needs to become a method that does computation.

Your suggestion violates the uniform access principle: http://en.wikipedia.org/wiki/Uniform_access_principle

You do care about the specific implementation for Model.foo if it could take 30 seconds to return a result.