Rails version 3.2.7 has been released
weblog.rubyonrails.org
Rails version 3.2.7 has been released
1–10 of 23 posts
Re: Rails version 3.2.7 has been released
#2I've basically given up on rails - and I wrote a 2.3.4 site - until it stabilizes a bit...
Re: Rails version 3.2.7 has been released
#3Don't call to_sym on untrusted input!
Re: Rails version 3.2.7 has been released
#4Don't call to_sym on untrusted input!
Oh wow. rb_intern() is a mess.
Re: Rails version 3.2.7 has been released
#5Is it just me or does it seem like everyone's stack is moving away from Rails? I mean, it's a great solution to many problems, I just feel that there's a lot more platforms that offer you even better customization and leave a far smaller footprint.
Re: Rails version 3.2.7 has been released
#6Re: Rails version 3.2.7 has been released
#7Is it just me or does it seem like everyone's stack is moving away from Rails? I mean, it's a great solution to many problems, I just feel that there's a lot more platforms that offer you even better customization and leave a far smaller footprint.
Nope, its just that other things are being hyped apart from rails.
Re: Rails version 3.2.7 has been released
#8Is it just me or does it seem like everyone's stack is moving away from Rails? I mean, it's a great solution to many problems, I just feel that there's a lot more platforms that offer you even better customization and leave a far smaller footprint.
It is going through the "small, cohesive" -> "full-featured!" -> "bloated" -> "modular" -> "too many abstractions" cycle.. in terms of overall adoption, I'm not sure. Many people like having all the "hard" problems solved for them.
People tend to talk about what's new and shiny because there is greater social reward for being the advocate of something new/better than there is to say "what we have is good enough and so I like using it!"
Re: Rails version 3.2.7 has been released
#9Earlier quoted context omitted.
Oh wow. rb_intern() is a mess.
is the badness in st_lookup or rb_enc_str_new ? I haven't traced the execution deep enough to see where things go south...
Oh wait, i get it. every symbolized string is added to the global symbol table, so you can basically make rails devour incredible amounts of memory by sending it new values. neat.