> Preach on about this bullshit when Ruby isn't primarily used for web > applications and when Ruby allows my system to reclaim memory, until > then lets leave the symbol argument bullshit out of this. Even if > they are constants they can lead to trouble if you just blindly state > they are better without explaining the dangers in a web application, > or people will repeat history, history people like me thought was > already common knowledge.
:) well it'd be interesting to know why you're frustrated out of Symbol concepts of Ruby ? I didn't say symbols are better than strings, in fact I asked that it's important to know for a developer that why and where they can be used! when did I say Ruby is best/primary used for web ? I use it in chip programming and it's been great so far :) It's an individual's choice to select a language/framework to achieve the solution to a problem, the main aim is to resolve a problem, now once decided to go with a language, one hast to know the limits and pros and cons of that language which certainly are there the way it's creators have made it to. If someone doesn't know how the class is being loaded once in memory clearly means there is huge lack of knowledge about how memory mappings going on there. And getting insights of symbols is a great way to get to know more about this. regards, Sur crimson9.com -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL79NE5QwbiPSu1FgfWk03Nc%2BKFYusbwVtMdwbddC1LcGuzwgA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
