サクサク読めて、アプリ限定の機能も多数！
トップへ戻る
大そうじへの備え
blog.engineyard.com
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? This was the impetus for a good deal of discussion the past few months. It seem
Redirecting... Click here if you are not redirected.
The world of JavaScript development can be frustrating and exciting. Every day, new libraries and modules are published, and it can feel overwhelming to try to keep up. On the other hand, all of this change has its benefits. As a community, we’re heading more and more toward an ecosystem that’s easier to work in and reason about. We keep getting new candy, and it makes our lives better! One JavaSc
DevCoach A developer coaching platform to improve productivity and code quality. FogBugz An easy-to-use software project management tool designed with an agile-first mindset.
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.
Engine Yard has always been dedicated to providing the best possible platform for your production applications. With thousands of deployed applications and happy customers supported by our platform, our success speaks for itself. The leading edge of technology is not static for long, though. To support our customer’s rising adoption of container based solutions, we are pleased to announce that Eng
If you’re like me, you love to code because it is a creative process. In another life, I am a musician. I’ve always loved music because it represents a synthesis of the concreteness of math and the ambiguity of language. Programming is the same way. But despite the creative potential of programming, I often find myself spending days working out the kinks of HTTP requests or dealing with SSL certif
Before we get started, let’s address the elephant in the room. Rails is great. It really is what you need for large scale production applications most of the time. It has history. And if you got started in Ruby working on the web, chances are Rails is what you are most familiar with. All these things are a fair argument for Rails as the framework of choice for many projects. The point of this arti
Testing is a vital part of any development process. Whether a project’s authors are hoping for scalability, fewer bugs, or just code that stands the test of time, a solid test suite is essential. It’s all well and good writing tests, but how do you know that you’ve tested the code that matters? Did you cover the most important components? Did you test the sad path? The edge cases? What about the z
Some might say 2014 has been a year of programming related death. TDD is dead. Agile is dead. The Framework is dead. If this keeps up, all of programming should be dead by about December 31st. Earlier this year I was lucky enough to attend a small conference in Southern france known as Ruby Lugdunum. In the late afternoon of the final day we retreated to a cafe and there was a panel discussion on
With the announcement of Rails 4.2 came some exciting news: Rails now has built-in support for executing jobs in the background using Active Job. The ability to schedule newsletters, follow-up emails, and database housekeeping tasks is vital to almost any production application. In the past, developers had to hand-roll this functionality, and configuration varied between different queueing service
We’ve heard it again and again, like a nagging schoolmaster: Keep your Rails controllers skinny. Yeah, yeah, we understand. But that’s often easier said than done—because things get complex. And we need to talk to other parts of our codebase or to external APIs to get the job done. Mailers. Stripe. External APIs. All that code starts to add up. Ah Tss Push It…Push It Down the Stack “Where should t
Note: This blog was originally published on our Japanese website in July 2014. It was recently translated for publication on our English site. At the third annual Ruby Business Forum held in Osaka, Japan this past summer Yukihiro “Matz” Matsumoto, the designer and developer of the Ruby progamming language, delivered the keynote, “How the internet is changing software and business using Ruby as an
In part one we looked at xhprof and how to install and run the profiler. In this installment, we will be looking at Xhgui — a UI for reviewing and comparing the data from xhprof. Using Xhgui Xhgui provides a number of features to help assess performance, both on single runs, as well as in aggregate — allowing you to pinpoint specific issues or spot trends. Glossary To effectively use Xhgui there a
What is Profiling? Profiling is measuring the relative performance of your application at the code-level. Profiling will capture things like CPU usage, memory usage, time and number of calls per function, as well as capturing a call graph. The act of profiling will impact performance. This differs from benchmarking, as benchmarking is performed externally and will measure the actual performance: w
The Arena The arena in which all these application servers will do battle is a basic test application I built that is available on GitHub. It’s a Sinatra app with some purely academic examples, not designed to do real, meaningful work, but instead to attempt a fair (or “fair enough”) set of tasks for each application server to process and repeat multiple times. /server This action spits out inform
An introduction to the gladiators My talk and research looked at four Ruby application servers: Passenger, one of the easiest to configure and very common Thin, an EventMachine-based server Unicorn, a very straight-forward app server for fast clients and responses Puma, a truly concurrent application server The application servers in question here were compared in several categories: Mode of Opera
The Engine Yard PaaS products are highly complex, and span thousands of servers to serve our customers. Ensuring that our applications run quickly and reliably requires a good understanding of concurrency and parallelization. This blog post is a recap of my journey down the rabbit hole of concurrency in an attempt to solve this problem in my own development efforts. Part II will be the continuatio
Note: This is the second in a two-part series that looks at what’s changing in Rails 4, and new features in Rails 4. Missed the first part? Check it out the first post Rails 4 changes. Rails 4 also includes some awesome new and useful features that I’m very excited about, and I suspect that you will be, too. ###Postgres H-Store ActiveRecord in Rails 4 will support the PostgreSQL hstore extension.
次のページ
このページを最初にブックマークしてみませんか？
『Engine Yard Blog』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
