Here\u2019s a look at some of the significant highlights<\/p>\n
TurboLinks 3<\/h2>\n
![\"TurboLinks](\"https:\/\/www.bacancytechnology.com\/blog\/wp-content\/uploads\/2015\/12\/railsturbolinks.jpg\")
<\/p>\n
Here, DHH again reaffirmed his love for TurboLinks and their inclusion in Rails 5.<\/p>\n
TurboLinks is a process for making an application even faster by making use of JavaScript to replace portions of content instead of again reloading an entire page. However, TurboLinks may also make an application a bit heavier on client side JavaScript that could sometimes results in slowdowns and unresponsiveness. This is an actual reason, why some of the developers have actually struggled to get the performance improves as promised by the TurboLinks.<\/p>\n
TurboLinks have always been an essential part, since version 4; however version 5 is looking to take advantage of the more advanced TurboLinks 3. This simplifies the process and makes advanced use of middleware and HTML5 custom data attributes.<\/p>\n
If you are somewhat familiar with the functionality of TurboLinks in your application, no need to fret at all! Usually, things are not changing considerably. TurboLinks 3 is going to be a good evolutionary step towards better speed and superior rendering.<\/p>\n
Action Cable<\/h2>\n
The most significant news at Rails Conf was the introduction of premier Action Cable<\/a>. Action Cable is a significant feature used to extend Rails with the use of WebSockets to include realtime messages passing functionality.<\/p>\n However, WebSockets is not a completely new concept and after lots of difficulties Rails has been finally fraught. Thus, it\u2019s a welcome addition for people who clearly not want to mess with the workarounds.<\/p>\n Action Cable is still in the very beginning of development and there is likely to be more information on it is expected as a part of Rails 5. However, considering the amount of projects required in real time interaction, Action Cable seems to a standard advantage to Rails developers.<\/p>\n Love for CoffeeScript by DHH has also been reaffirmed here. Baked into Rails in version 3, CoffeeScript is designed as the default JavaScript while using the Rails. Thus, CoffeeScript has become “must use” for Rails developers, specifically for devs that work on a large number of projects.<\/p>\n It\u2019s been two versions; CoffeeScript has come into existence, still is the default and it has got a wider acceptance. For many, the fear of \u201cMustUse\u201d has not been panned out and for others, tried CoffeeScript and enjoyed it.<\/p>\n One essential thing that can be sure of is: CoffeeScript is the default JavaScript flavour in Rails; this won\u2019t possibly be going away.<\/p>\n Rails 5 only supports the version 2.2.1 and higher. As Ruby is progressing as a language, backwards compatibility is required to be sacrificed regarding new functions. The older version of Rails won\u2019t be supported indefinitely. Ruby on Rails is no different. However, Rails is actually making the sensible decision of only encouraging the most preferred version, starting with 2. 2. 1 and including all stable releases after.<\/p>\n As a result, it won\u2019t be possible that someone making use of Ruby1.9.3 would want to move to Rails 5. There are also possibilities that they will stick to a lower version until some other external factors force an upgrade along with the refactoring of the code. However, for some dev shops this won\u2019t be going to be happening for years, which is perfectly understandable.<\/p>\n For a lot, this is somewhat a barrier to Rails 5. With regard to other people, it is an opportunity to improve an application which may be in need of some love.<\/p>\n Due to latest version of Ruby in Rails 5, now Rails applications will have less memory consumption<\/p>\n Rails 5 will only support Ruby 2.2.2 or better<\/p>\n If you happen to run your Rails application on top of MySQL 5.7.8 then your database have a new native JSON data type.<\/p>\n Example:<\/p>\n Or method in ActiveRecord::Relation<\/p>\n Finally ActiveRecord::Relation is getting #or method, this will allow us to write queries with ActiveRecord DSL as follows:<\/p>\n Example:<\/p>\n Summary<\/p>\n Ruby on Rails is completely upon us.<\/p>\n It seems as though we have a lot to look forward: Turbolinks update for improved rendering, Action Cable for improved real-time message handling, more CoffeeScript as well as moving forward with the Ruby ecosystem.<\/p>\n ========================================================================<\/p>\n Here at Bacancy Technology, we have in-depth knowledge and extensive experience of RoR developers. Being active RoR community members, we are always there to provide Rails Upgrade Service<\/a>.<\/p>\nCoffeeScript<\/h2>\n
![\"coffee](\"https:\/\/www.bacancytechnology.com\/blog\/wp-content\/uploads\/2015\/12\/coffee-script.png\")
<\/p>\nRuby Version Support<\/h2>\n
![\"Ruby](\"https:\/\/www.bacancytechnology.com\/blog\/wp-content\/uploads\/2015\/12\/ruby.png\")
<\/p>\nMySQL ActiveRecord adapter gets JSON support<\/h2>\n
![\"My](\"https:\/\/www.bacancytechnology.com\/blog\/wp-content\/uploads\/2015\/12\/MySql-sql.jpg\")
<\/p>\n
\nt.json :settings
\nend<\/figure>\n
\n\\# => SELECT * FROM books WHERE (status = 1) OR (status = 3)<\/figure>\n