Every year, there is a gathering of developers, looking toward the future of a framework that nearly 15 years ago brought Ruby to the web. That gathering is Rails Conf, and the 2018 edition is in Pittsburgh, Pennsylvania!
A few years ago there was a whole lot of hubbub in various spots about Ruby being dead. Here we are, three years later, and the same arguments are being bandied about. Ruby is a programming language built for happiness - that’s the underlying principle. Why would a community of happy individuals and teams let that die?
From the start, Rails was praised for being the easiest way to get Ruby on the web. Not only has it solidified itself as the easiest option, it’s become the best. Since then, many other options have arrived, but Rails is still the de facto framework for Ruby developers.
On June 30, 2016, Rails 5.0.0 was released. Since then, Ruby has spent more than 4,100 commits to make things simpler for users. Additionally, it’s released numerous iterations, including Rails 5.1.2, which was released on June 26, 2017.
Let’s talk about the elephant in the room: Rails is great and is exactly what’s needed for large-scale production applications. It has history—and if you got started in Ruby working on the web, chances are Rails is what you’re most familiar with. All these things are a fair argument for Rails as the framework of choice for many projects.
After a month hiatus, it’s time for your monthly dose of “Cloud in My Coffee”, the monthly video series from the Engine Yard Community Team. This video series features interviews with many of the people that make Engine Yard what it is every day. From the “C” level executives to those working the tickets on our Support Team, you’ll have the opportunity to get to know the Yardees around the world, all from the comfort of your seat, cup of coffee close at hand.
When working on a new language, framework, or toolset, we’re often working with an example that wants us to build a blog. While blogs are great and easy to build, they are a limited in scope, and it could be we’re looking to build a different sort of static site—one that isn’t a collection of posts arranged by date. So what’s the alternative?
As promised, it’s time for your monthly dose of “Cloud in My Coffee”, the monthly video series from the Engine Yard Community Team. This video series features interviews with many of the people that make Engine Yard what it is every day. From the “C” level executives to those working the tickets on our Support Team, you’ll have the opportunity to get to know the Yardees around the world, all from the comfort of your seat, cup of coffee close at hand.
A few weeks back, I took a brief look at alternate frameworks to Ruby, i.e. things that weren’t Rails. People seemed to like it. As a result of that post, several people got in touch to suggest a frameworks I may have overlooked. So I thought I’d do a follow up post and share those with you after having reviewed them.
There are many reasons you might be thinking about moving your Rails app to Engine Yard. Perhaps you grew beyond the capacity of what that service can offer? Perhaps the current service abandoned Rails as a supported part of their service? Perhaps you realized managing hardware yourself is taking time away from building a better application. Whatever the reason, you’ve reached the point where a move to Engine Yard is the right decision, and we’re here to help.
Looking for a way to kick off that first Monday of the month? Wondering what goes on internally at Engine Yard? Hoping to meet some shining new faces?