Posts mit dem Label rails werden angezeigt. Alle Posts anzeigen
Posts mit dem Label rails werden angezeigt. Alle Posts anzeigen
Dienstag, August 29, 2006
Bruce Tate: The Toy (about the opportunities for Ruby on Rails)
In this article Bruce Tate explains the opportunities Ruby on Rails has to offer for the agile software development of dynamic web application.
Donnerstag, Juli 20, 2006
Articles on rapidred.com (written by Ruby on Rails experts)
This article series is intended to extend the reach of Java developers. By exposing a typical Java developer to techniques beyond the Java langauge, Crossing Borders helps can help any traditional Java programmer improve skills, expand his world view, or even know what else is available should it make sense to move away from Java for a given problem.
http://rapidred.com/content/list?category=resources
http://rapidred.com/content/list?category=resources
Labels:
agile programming,
java,
rails,
ruby
From Bruce Tate's "Paddle Like Hell"
Bruce Tate's not so serious ramblings:
http://blog.rapidred.com/
Bruce, usually coming from a Java background, now focus on rapid development with Ruby / Ruby on Rails. (Also check his previous blog http://weblogs.java.net/blog/batate/
http://blog.rapidred.com/
Bruce, usually coming from a Java background, now focus on rapid development with Ruby / Ruby on Rails. (Also check his previous blog http://weblogs.java.net/blog/batate/
Labels:
agile programming,
java,
rails,
ruby
Montag, Juli 17, 2006
Top 30 Ruby on Rails Tutorials from econsultant.com
Another comprehenseive list from econsultant.com. This time it is about Ruby on Rails:
http://www.econsultant.com/web-developer/ruby-rails-tutorials/
http://www.econsultant.com/web-developer/ruby-rails-tutorials/
Dienstag, März 14, 2006
Tonabnehmer
Der Tonabnehmer ist eine Audiokolumne zur agilen Softwareentwicklung und ein kleines Experiment im Podcasting von Frank Westphal.
Tonabnehmer
Tonabnehmer
Labels:
agile programming,
programming,
rails,
ruby,
web development
Donnerstag, März 09, 2006
Montag, März 06, 2006
Ruby on Rails in the Enterprise Toolbox
If you've followed the IT blogosphere even slightly over the past months, you've unavoidably heard of a "Web 2.0" web development framework named Ruby on Rails. Ruby on Rails (or, just Rails) is indeed an exciting development and definitely has earned a lot of the attention it's getting. Following the recent 1.0 release of Rails, this article is my feeble attempt to help you see through the hype and see Rails for what it's worth. Specifically, I'd like to pose the question, where does Ruby on Rails fit in the enterprise development landscape?
Ruby on Rails in the Enterprise Toolbox
Ruby on Rails in the Enterprise Toolbox
Labels:
programming,
rails,
web development
Sonntag, März 05, 2006
Ruby on Rails vs Python Web Frameworks
Interesting comparison between web development with Rails compared to Python. Also outlines the many advantages Ruby and Ruby on Rails have.
Zifus: Ruby on Rails vs Python Web Frameworks
Zifus: Ruby on Rails vs Python Web Frameworks
Labels:
programming,
rails,
ruby,
web development
Screencasts of Ruby on Rails
Creating a weblog in 15 minutes? Putting Flickr on Rails? You can wath it here:
Screencasts of Ruby on Rails
Screencasts of Ruby on Rails
Labels:
programming,
rails,
ruby,
web development
Freitag, März 03, 2006
Ruby on Rails: Scalability? Security?
Ruby on Rails may be flavour of the year, but is it secure? Will it scale?
Security vulnerabilities are logic errors. You can have just as many security violations in a Java program or a Perl program or something else.
So would he recommend Rails for a highly secure application like online banking?
Definitely. But what gets used is not necessarily decided on technical excellence but more: ‘I wouldn’t get fired for using Java.’ It’s a political concern more than it’s a technical concern. As for scalability, we didn't try to solve that problem with Rails, because it is already solved. How is Yahoo scaling? They’re doing billions of page views a day, and they’re using PHP. The thing about PHP, Perl, Python and Ruby is that they can all be architected in the same manner, which is this notion of not having session state in the application layer. You push that down to the database, or you push it down to a shared memory store. That gives you the freedom of adding new application servers at will. You have load balancers, then you have web servers, then you have load balancers, then you have application servers. Rails is intensely scalable in that fashion.
Read more
Security vulnerabilities are logic errors. You can have just as many security violations in a Java program or a Perl program or something else.
So would he recommend Rails for a highly secure application like online banking?
Definitely. But what gets used is not necessarily decided on technical excellence but more: ‘I wouldn’t get fired for using Java.’ It’s a political concern more than it’s a technical concern. As for scalability, we didn't try to solve that problem with Rails, because it is already solved. How is Yahoo scaling? They’re doing billions of page views a day, and they’re using PHP. The thing about PHP, Perl, Python and Ruby is that they can all be architected in the same manner, which is this notion of not having session state in the application layer. You push that down to the database, or you push it down to a shared memory store. That gives you the freedom of adding new application servers at will. You have load balancers, then you have web servers, then you have load balancers, then you have application servers. Rails is intensely scalable in that fashion.
Read more
Labels:
programming,
rails,
ruby,
web development
Enterprise Ruby On Rails |- Online book
This online book book will guide you through a real-world high-capacity and highly available platform.
Enterprise Ruby On Rails |:
Enterprise Ruby On Rails |:
Labels:
programming,
rails,
ruby,
web development
Ruby on Rails Usage: Demonstration video
This demo does pretty well demonstrate the ease of use of the RoR Framework
rails_take2_with_sound.mov (video/quicktime Object)
rails_take2_with_sound.mov (video/quicktime Object)
Labels:
programming,
rails,
ruby,
web development
Ruby on Rails Scalability: Some numbers...
Justin Gehtland is back with numbers to back up his original claim that “Rails is actually faster” for his application than the Java/Spring/Hibernate/JSTL stack powered version was. Through various benchmarks, he has found Rails to be roughly 15-30% faster than the old Java version. Interestingly enough, it seemed that Rails was especially better performing on deeper domain feature... .
Justin�Gehtland is back with numbers to back it up
Justin�Gehtland is back with numbers to back it up
Labels:
programming,
rails,
ruby,
web development
Interesting discussion on Ruby on Rails and Scalability
... can be found here:
The Joel on Software Discussion Group - What's all the fuss about Ruby On Rails?
This is a good point when discussing about scalability:
"Besides, arguments about scalability are a non-issue.
Ruby On Rails pushes most of the hard work onto the most proven of all scalable workhorses: the relational database.
Proponents of the Java stack may crow about the scalability of their frameworks, but on the frontline it is choking in complexity.
Long term, complexity is as important as performance.
True, Rails is yet to prove itself in terms of scalability, but Java still has some way to go.
Rails can do the simplicity, but can it manage the performance?
Java can do the performance, but can it manage the simplicity?
Remember that Java was once the slow, unproven contender itself. It won out against C because of reduced complexity, not because of increased performance."
The Joel on Software Discussion Group - What's all the fuss about Ruby On Rails?
This is a good point when discussing about scalability:
"Besides, arguments about scalability are a non-issue.
Ruby On Rails pushes most of the hard work onto the most proven of all scalable workhorses: the relational database.
Proponents of the Java stack may crow about the scalability of their frameworks, but on the frontline it is choking in complexity.
Long term, complexity is as important as performance.
True, Rails is yet to prove itself in terms of scalability, but Java still has some way to go.
Rails can do the simplicity, but can it manage the performance?
Java can do the performance, but can it manage the simplicity?
Remember that Java was once the slow, unproven contender itself. It won out against C because of reduced complexity, not because of increased performance."
Labels:
programming,
rails,
ruby,
web development
Abonnieren
Posts (Atom)