Welcome to Kansas City! This is your advisor Godfrey. Since you are new here, it must be a bit overwhelming for you. Don’t worry, I’m here to help you do your job. Let’s get to it!
Rails 5.0.0.beta4 was released this week. Based on the increasing version numbers, I speculate the core team is working towards a 5.0.0.RC1 release and eventually a 5.0.0 final release. I recommend you try out the beta release on our apps.
According to sources close to the development, 34 contributors were seen submitting patches to the Rails code base this week. From what I can tell, this appears to be a good sign.
Our plans to import colors from Oz have worked – I am proud to say Kansas is no longer black and white. I recommend that you install the Guidebook app ahead of the conference. You might also want to sign up for the workshops too – see the official welcome email in your inbox for details.
We are not interested in recycling the dishwater or taking 30-second showers. Worse than that, some of the sponsors have planned parties for the attendees. How can we call ourselves a decent city if we can’t accommodate that?
Put some drink in your think, Mayor, and get us some water.
Despite already accommodating well over a thousand attendees, our polls have shown the majority of Rails users will not be able to attend the conference.
To prevent a public outcry, I advised the conference organizers to record all talks and make them available on this website after the conference.
They are planning to live stream the keynotes as well, although I heard the secret URL won’t be up until next Wednesday. I can hear the sound of F5 buttons cracking up from here.
In a series of experiments to research Swearing as a response to pain, a local scientist has discovered some new methods to manipulate time by accident. As a result of this new discovery, these core extension methods will be available in Active Support 5.
Also new to Active Support, Rails users will soon be able to express themselves in these newfound vocabularies.
A scientific study to end the decade-old debate in the programming community has concluded in a surprising twist. The report declared that faster code does seem to perform better, after all.
As a follow up to the research, this contributor was the first to apply the new optimization technique to
Array#split. The work has resulted in some performance gains, contrary to everyone’s expectations.
A group of linguists gathered in town to discuss the merits of semicolons. During a panel discussion, they have reached consensus that typos can indeed reduce readability.
Coincidentally, this week the Rails Guides have received a flurry of changes that improved their readability.
My recommendation? We should sit down and fix the typos in our city bylaws some day.
It is well-known in the computer science community that concurrency is hard. This patch that just landed on Rails master is the perfect example to illustrate why – in an attempt to fix a bug in Active Support’s
ShareLock class, the patch was briefly misidentified as Sherlock Holmes, causing a brief delay and a race condition.
Recently, an audit discovered that Rails sometimes loads the database schema twice. According to a survey, most Rails users do not find this necessary, leading to the “feature” being removed from master this week.
I have an unfortunate piece of news for you, Mayor. The JRuby builds have been temporarily flagged as allowed to fail on Rails’ CI servers. If you know anyone who works with JRuby, we could use some help identifying and fixing the root causes here.
Despite promising results from last week, the researchers involved have backtracked their claims on the performance benefits associated with this change. Based on my negative lookahead, I believe this issue will remain a source of huge debate among the experts in the foreseeable future.
That concludes my report for this week. There were plenty of other things going on, so feel free to jump in and check them out yourself.
See you next week at RailsConf!