News for hackers. Stuff that matters.
Re:Rails Has Turned into Java by tmo9d on Wednesday February 20, 2013 @03:33PM (#5253141)
I added in a note, I think this is the multi-year result of not having a old, grey-haired standards committee around creating APIs. I made fun of Sun and Oracle for doing things like this for years, but after futzing around with Rails frameworks, integration, and edge-cases. I think I would have preferred to have people sitting around a conference call saying things like, "Hey Devise people, your authentication approach looks like a good standard, why don't we formalize it so we can make this stuff easier to integrate."

I know this makes me sound old. I own that.

Re:Rails Has Turned into Java by veemjeem on Wednesday February 20, 2013 @04:00PM (#5253326)
I think the nice thing about Rails is that the core committee tries to make the core framework slimmer by removing features and stuffing them into gems. It's nice that Rails keeps features out that might be considered "core" by others, like authentication. It allows new "core-like features" to be adapted by the community.
Re:Rails Has Turned into Java by nathanappere on Wednesday February 20, 2013 @03:59PM (#5253318)
What would be the point of making it a standard ? It's already one de-facto. I prefer to have other solutions not trying to be devise but rather solving auth problems in their own way. Also, the lack of documentation is often balanced by the great readability of the code (Which is extremely clean / straightforward for devise & omniauth & most of the strategies)
Re:Rails Has Turned into Java by kevinconroy on Wednesday February 20, 2013 @03:42PM (#5253204)
I, for one, welcome our W3C overlords.
Re:Rails Has Turned into Java by tmo9d on Wednesday February 20, 2013 @03:57PM (#5253301)
Oh c'mon it's much much worse than that. Oracle runs the JCP not the W3C.

And, yes, I admit it, I'm a jerk.