Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rails 5.1.0 Beta 1

weblog.rubyonrails.org

Post reply on HN
Print view View original

31–40 of 78 posts

Re: Rails 5.1.0 Beta 1

#31

Post by timdorr »

stouset wrote: post #28
technion wrote: post #17

I don't like this "secret storage" system. Unauthenticated CBC mode, and doesn't actually set an IV (I'm assuming a hardcoded default comes into play).

This needs to be higher up. It's using Blowfish (a 64-bit block cipher), unauthenticated, in CBC mode. These should not be the defaults for a system designed and built in the past five years.

Looks like you opened up an issue, which is a good first step: https://github.com/rails/rails/issues/28135

Not sure how much of the Rails team browses HN comments, but an issue will certainly get their attention.

Re: Rails 5.1.0 Beta 1

#33

Post by evolve2k »

swilliams wrote: post #15

Is CoffeeScript still the default then? I see it referenced in the codebase still.

I'd imagine with ES6 all nicely wired up in this release that moving away from Coffee would be an obvious next step but was way to large to undertake in one release.

Re: Rails 5.1.0 Beta 1

#34

Post by CoachRufus87 »

donjh wrote: post #26
out_of_protocol wrote: post #6

Actually pretty major release. Hopping on javascript's crazy train. It was expected anyway, there are no way to ignore js-crazyness anymore (most of the frontend toolset exists only as js implementation). Also, Phoenix (ideological successor of rails) took this approach from the start

I think the JavaScript updates are great news, enough for me to finally dive into Rails.

Welcome!

Re: Rails 5.1.0 Beta 1

#35

Post by oomkiller »

out_of_protocol wrote: post #6

Actually pretty major release. Hopping on javascript's crazy train. It was expected anyway, there are no way to ignore js-crazyness anymore (most of the frontend toolset exists only as js implementation). Also, Phoenix (ideological successor of rails) took this approach from the start

Sure it's possible to ignore, via Turbolinks or similar. I have witnessed the shift back to the backend over the past year or two, including in the Phoenix community. With HTTP2 inbound and microsecond response times via Phoenix, the case for making your new app a SPA is harder to make, if you take an honest look at things. There are some benefits to be had with React Native, or Angular2 Dart + Flutter, but mobile apps are very difficult to justify, given the increased friction they cause to new users.

Re: Rails 5.1.0 Beta 1

#36

Post by ivrrimum »

sergiotapia wrote: post #14
out_of_protocol wrote: post #6

Actually pretty major release. Hopping on javascript's crazy train. It was expected anyway, there are no way to ignore js-crazyness anymore (most of the frontend toolset exists only as js implementation). Also, Phoenix (ideological successor of rails) took this approach from the start

You know I used to think it's craziness, but it really makes for a much experience writing ES6 as opposed to random-ass jquery and javascript sprinkled all over the place. I've grown to love it.

Debatable.. You can just use plain Typescript + jquery and still be "clean" without all the nonsense of react/angular.

P.S I have worked with both of those frameworks and like them, just sometimes they are too mutch.

Re: Rails 5.1.0 Beta 1

#37

Post by ivrrimum »

mark_sz wrote: post #20

In terms of integration with Javascript, RoR seems to be behind for example (PHP) Laravel.

After this update Rails is on the track. And even before, you could use gems to make the use of modern JS stuff. This update just made it faster/easier to start using it.

Re: Rails 5.1.0 Beta 1

#38

Post by yeskia »

elsurudo wrote: post #24
mark_sz wrote: post #20

In terms of integration with Javascript, RoR seems to be behind for example (PHP) Laravel.

After this integration with webpack, will it still be behind?

I wouldn't have thought so.

Laravel 5.4 shipped a month ago with browser integration testing and Webpack by default, now Rails has the same.

Re: Rails 5.1.0 Beta 1

#39

Post by allover »

oomkiller wrote: post #35
out_of_protocol wrote: post #6

Actually pretty major release. Hopping on javascript's crazy train. It was expected anyway, there are no way to ignore js-crazyness anymore (most of the frontend toolset exists only as js implementation). Also, Phoenix (ideological successor of rails) took this approach from the start

Sure it's possible to ignore, via Turbolinks or similar. I have witnessed the shift back to the backend over the past year or two, including in the Phoenix community. With HTTP2 inbound and microsecond response times via Phoenix, the case for making your new app a SPA is harder to make, if you take an honest look at things. There are some benefits to be had with React Native, or Angular2 Dart + Flutter, but mobile ap…

Hrm, can't really agree with the premise, I feel like the backend not being fast enough should never have been a significant reason to write an SPA.

Re: Rails 5.1.0 Beta 1

#40

Post by jrochkind1 »

why-el wrote: post #12
jrochkind1 wrote: post #10

I had heard that Capyabara-based tests were going to be incorporated in Rails. As the multi-threaded concurrent nature of these always makes things a pain, hard to get right, leading to much pain for devs with non-trivial test suites -- I was curious to see how they'd handle it, if there'd be an 'official' Rails solution, ideally backed by some deep Rails knowledge. I was surprised that they've chosen to use the 'sha…

What kind of race conditions are you talking about? I ran this setup for years, and just about the only thing that has been stable in the whole setup is ActiveRecord.

You ran the shared connection situation with no problems? Great, but I linked to examples of people who have had different experiences, you can follow the links to see. Like all race conditions, sometimes they appear and sometimes not, and it can depend on your particular app.

They are not surprising, because the concurrency guarantees of AR do not include sharing a connection object between threads, it is not meant to be thread-safe.

With postgres, the race conditions on sharing a connection between two concurrent threads sometimes look like "PG::Error: connection is closed" or "PG::UnableToSend: another command is already in progress", with mysql sometimes like "Mysql2::Error: This connection is in use by: #"

Post reply on HN