Live data from Hacker News

Rails 5.0.1 has been released

weblog.rubyonrails.org

41–50 of 57 posts

Re: Rails 5.0.1 has been released

#41
post #9

Earlier quoted context omitted.

> IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. That has been the reason I always avoid huge frameworks like RoR. If I was to hit a bug like this, I wouldn't know where to start debugging. How do people deal with obscure bugs in the framework with something like RoR?

> That has been the reason I always avoid > huge frameworks like RoR. For others it is the reason to use huge frameworks like RoR. Because alternative is to hunt obscure bugs in the framework you built yourself.

> Because alternative is to hunt obscure bugs in the framework you built yourself.

That's a false dichotomy, there are also smaller frameworks available.

Re: Rails 5.0.1 has been released

#42
post #39

Earlier quoted context omitted.

react-rails is really good.

react_on_rails is even better.

Not really. Depends completely on what you need. Not integrating with your existing asset pipeline isn't necessarily a plus depending on what your goals are.

There's also a weird amount of self promotion going on with that repo. Not sure what it is about that but it's kind of been a turn off to me.

Re: Rails 5.0.1 has been released

#43
post #9
post #6

TLDR: Definitely worth upgrading. Approximately hundreds of small bug fixes, across much of Rails. The fixes include some important ones for database types, time comparisons, thread issues, record reloading, etc. IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. Thanks to all the contributors for excellent work on this release.

> IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. That has been the reason I always avoid huge frameworks like RoR. If I was to hit a bug like this, I wouldn't know where to start debugging. How do people deal with obscure bugs in the framework with something like RoR?

Because small frameworks don't have bugs, right?

Re: Rails 5.0.1 has been released

#44

Slightly off-topic: is learning Rails still a good career choice? I'm not particularly keen on JavaScript on the server and I think I am slightly tired using .NET on a daily basis.

Where I'm from (Toronto, Canada), Rails development pays significantly more than any other stack and there is substantially more work available.

I'd love to DM you with some questions about Toronto. Can you ping me via my profile info?

Re: Rails 5.0.1 has been released

#45
post #36

Earlier quoted context omitted.

You start by boiling it down to an executable test case, for which there are templates here here: http://guides.rubyonrails.org/contributing_to_ruby_on_rails.... Then you share the test case in a bug report, and collaborate to fix it. Fixing it usually involves a source code dive. With Rails's reasonably well documented and reasonably well written codebase it's usually possible to grok the source and dependencies eve…

Interesting, my experience is the opposite: liberal use of ruby's dirty tricks often makes code hard to understand and thus debug.

i think different areas of Rails codebase vary here, some are pretty legible, some less so.

Re: Rails 5.0.1 has been released

#46

Slightly off-topic: is learning Rails still a good career choice? I'm not particularly keen on JavaScript on the server and I think I am slightly tired using .NET on a daily basis.

Where I'm from (Toronto, Canada), Rails development pays significantly more than any other stack and there is substantially more work available.

Same here, on the other side of the country.

Re: Rails 5.0.1 has been released

#47
post #36

Earlier quoted context omitted.

You start by boiling it down to an executable test case, for which there are templates here here: http://guides.rubyonrails.org/contributing_to_ruby_on_rails.... Then you share the test case in a bug report, and collaborate to fix it. Fixing it usually involves a source code dive. With Rails's reasonably well documented and reasonably well written codebase it's usually possible to grok the source and dependencies eve…

Interesting, my experience is the opposite: liberal use of ruby's dirty tricks often makes code hard to understand and thus debug.

Once you understand how it all works, I'll grant that that can take years, it doesn't take much time at all to debug upstream code. Just last night I was playing around with the jsonapi-resources gem, and found an issue that was keeping me from being able to dynamically generate resources. After realizing I couldn't work around the issue through more metaprogramming, I set about monkey-patching the code.

It got too late so I couldn't finish the job, but once I do, I'll get it working for my project, then package it up and make a pull request so I don't have to support it myself.

Ruby is definitely wizardry but it's accessible wizardry.

Re: Rails 5.0.1 has been released

#48

Slightly off-topic: is learning Rails still a good career choice? I'm not particularly keen on JavaScript on the server and I think I am slightly tired using .NET on a daily basis.

In Bangkok the demand for Rails developers is as strong as ever. With enough experience you will have no problem finding a job that pays better than other stacks. There are a number of companies like ours that'd be happy to help you with visa if you're willing to relocate. Happy to answer any questions! (contact info under my profile)

Re: Rails 5.0.1 has been released

#50
post #39

Earlier quoted context omitted.

react_on_rails is even better.

Not really. Depends completely on what you need. Not integrating with your existing asset pipeline isn't necessarily a plus depending on what your goals are. There's also a weird amount of self promotion going on with that repo. Not sure what it is about that but it's kind of been a turn off to me.

Its not so different from thoughtbot's repos, just a different personality.
Post reply on HN