RailsConf and DHH part ways – The new stack


This week’s example of a blog post that could have been an email comes from the creator of Ruby on Rails, David Heinemeier Hansson, also known as DHH. In a blog post titled “No RailsConf”, DHH spends nearly a thousand words explaining how “2021 has been an amazing year for Ruby on Rails”, and all he has personally done for the project, before sharing a brief email from RailsConf organizers detailing their decision “to start sharing the keynote stage with other contributors”.

Obviously, this is not an idea DHP likes. “It’s such a shame that this is the world we find ourselves in now,” he wrote. “One so deeply divided by politics and ideology that we can’t even share the love of Ruby on Rails together at a conference without needing to settle scores.”

Although there is no mention in the blog post of the exact accounts being settled, you might recall one thing that happened last year when Basecamp tried to prevent employees to discuss workplace politics and that a third of them left the company in response.

While some are ready to find the way out alongside DHH, the most overwhelming response is, “don’t let the door knock you where the good Lord has divided you.” Or, as they say on the internet these days, “well, well, if it’s not the consequences of my own actions.”

A particular Twitter thread made the rounds from the DHH blog, featuring Ruby Lead Brandon Weaver comparing the current situation with DHH to that with Scala.

In the thread, writes that the Scala community experienced a schism after allowing a “slavery apologist and known racist to speak” at LambdaConf in 2016, and that “the type of train of thought that DHH is going down leads to this path very quickly, and I already see language that I would expect from these circles popping up in his blog posts.

For his part, DHH, and although he has posted a blog post on the subject, he seems somewhat indifferent to the whole affair, saying he is “confident that we can eventually circumvent the fractured politicization that has infiltrated into our debates”.

“I don’t think that’s what most programmers or most companies want,” he continues. “But it’s a perilous time to reveal preferences, so I fully understand why many choose to duck instead.”

Whether or not DHH will be invited back next year remains to be seen, but if the response on Twitter is any indication, it seems many are fine without his speech after more than 15 years.

This week in programming

  • AWS Lambda Gets a .NET 6 Runtime: AWS introduced a .NET 6 runtime for AWS Lambda, which means developers can now use the .NET 6 runtime to build AWS Lambda functions on x86 and Arm/Graviton2 processors. Although .NET 6 has many new features, AWS writes that there are also new features added to the .NET Lambda experience that developers can use to improve diagnostics and performance and use new coding patterns. Additionally, AWS offers the Lambda runtime client as an open source project, providing what it says is “a consistent and seamless Lambda runtime client experience across all environments, whether managed runtime , container images, or using the Lambda runtime client for custom .NET runtimes.For more details on migrating existing .NET Lambda functions to the new .NET 6 runtime, go to the blog post or read the Lambda Developer’s Guide.
  • Knative (Finally) Joins CNCF: The wait is finally over as Knative joins the Cloud Native Computing Foundation (CNCF) as a serverless incubation project this week. Knative’s potential addition to the CNCF has been something long in the works, and was once declared out of the realm of possibility. But as IBM now writes, “By accepting Knative as an incubation project, the CNCF gains a project that extends, simplifies, and improves the Kubernetes platform for serverless and event-driven workloads. a win-win combination. Beyond the standard congratulatory platitudes, IBM’s blog post on the subject offers its own take on Knative’s journey as an incubation project, as well as what features IBM is currently involved in improvement, such as Knative’s performance, asynchronous calls, and Knative’s direction operator. If you want to learn more, beyond the blog post, IBM invites readers to “attend (and /or submit a talk by March 8)” at the first KnativeCon at KubeCon Europe in Valencia, Spain in May 2022.
  • The Story of Everything Go: Golang’s weekly newsletter has highlighted what it calls a “treasure of a resource” and “a conservation feat” with Go: a documentary, a list of “issues, discussions, proposals, CLs, and interviews of the Go development process, which is intended to provide a comprehensive reference of the history of Go.” Indeed, complete is also an apt description, as it provides a complete timeline of feature additions, language design and more. Want to know all about adding Generics? This is definitely a good place to start. And if nothing else, head over and check out the fun facts section. For example, you can go see the first Go commit in… 1972?!
  • Mozilla’s Developer Network (MDN) is getting an overhaul: Five years have passed since MDN’s last overhaul, and now the timer can be reset, as the site underwent another overhaul this week. From a new homepage that they say focuses on “basic concepts of community and simplicity” to “redesigned article pages for improved navigation,” Mozilla says the new MDN has ” ambitious plans to leverage our new tools to explore improved navigation, generated standards and support summaries, and integrated MDN documentation where developers need it most: in their IDE, navigation, etc. Beyond what it’s already done, Mozilla also says “MDN Plus” is coming soon, which will offer “a premium subscription service based on feedback we’ve received from web developers who want to customize their MDN experience” – with features like notifications, article collections, and an offline experience on MDN.
  • The error of the SPAs? Finally, we direct you to a blog post claiming Single Page Applications (SPAs) were a mistake, which reached the upper echelons of Hacker News this week. In the blog post, JavaScript developer Chris Ferdinandi asserts that while “there are a few narrow examples where SPAs make sense and are the right choice”, in general, “SPAs as a trend of the industry or “best practice” were [a] error.” Ferdinandi followed the next day with another article, this time detailing how to create AMPs as fast as SPAs. For more on this topic, you can also check out our own recent coverage of htmx and the ZPS debate compared to MPAs.


About Author

Comments are closed.