Headius: My Favorite Hotspot JVM Flags
parámetros de la bazofia de la máquina virtual del puto javahas_many :bugs, :through => :rails: Thread safety for your Rails
Long story short, Rails can now serve multiple requests in more than one ruby threads ( or native threads if you’re on JRuby ) parallelly. Charles Nutter has done a good job of explaining the details here. Should you give a flying fuck ? You totally should if : * You’re using JRuby * You’re bold enough to play around with bleeding edge Neverblock stuff * Your application has a lot of long running processes, which are not heavy on blocking IO ( this would be rare I imagine ) You totally should NOT if : * You’re using Event based mongrel, thin or any of the event based web server in production. Event based servers don’t use Threads, so it just doesn’t matter. * You CBA You may have heard a bunch of hype about how threads make everything 100x faster, this is far from the truth. Don’t believe everything the hype merchants want to sell you, test your application first and see if it helps.Unlimited Novelty: Twitter: blaming Ruby for their mistakes?
How many of Twitters issues caused by succumbing to NIH (Not Invented Here)
In-depth discussion of message queuing systems and systems architecture, with Twitter representatives speaking up in the comments thread.
Long, but very interesting analysis of ruby, message queue systems, and Twitter's use thereof
twitter and ruby
http://www.tervela.com/tmxJRuby on Rails on Google App Engine | Ola Bini: Programming Language Synchronicity
In this post I thought I’d go through the steps you need to take to get a JRuby on Rails application working on GAE/J, and also what kind of characteristics you should expect from your application.
JRuby on RailsをApp Engine上で動かす方法Bigcurl: Running Sinatra apps on Google AppEngine (Java)
http://github.com/bigcurl/sinatra/tree/masterRuby on Rails on Google App Engine: Welcome aboard
Now RoR is supported by Google App Engine. What are you waiting for!?Relevance Blog : Working With Multiple Ruby Versions Has Never Been This Easy
echo "source ~/ruby_switcher.sh" >> .bash_profile
ruby_switcher 여러 버전의 루비를 명령하나로 바꿔가면서 사용할 수 있다
Nice post and accompanying bash script to manage multiple versions of ruby.Rails Primer for Google App Engine with JRuby
把 google appengine 包的更簡化....
"rails primer for google app engine"TorqueBox: Home
TorqueBox is a new kind of Ruby application platform that integrates popular technologies such as Ruby-on-Rails, while extending the footprint of Ruby applications to include support for Job Scheduling, Task Queues, SOAP Handling, and Telecom. TorqueBox provides an all-in-one environment, built upon the latest, most powerful JBoss AS Java application server. Functionality such as clustering and cloud deployment is included right out-of-the-box.
TorqueBoxRuby Version Manager: Easily Use Multiple Ruby Versions At Once
they are blending the best of proper languages and markup languages. That there is no obfuscated code/bytecode (you ship Ruby to the "browser" app that will interpret it) is a good thing, it will dis
MaveRelevance Blog : Java.next: Common Ground
I have chosen four languages which together represent "Java.next": Clojure, Groovy, JRuby, and Scala. Notes on Functional programming
Annotated link http://www.diigo.com/bookmark/http%3A%2F%2Fblog.thinkrelevance.com%2F2008%2F8%2F4%2Fjava-next-common-ground
This sentence from the article says much: "In my experience, this style of coding tends to reduce the size of a codebase by an order of magnitude, while improving readability." Example from article: "...do not have to code defensively, using a slew of factories, patterns,...you can build a minimal solution and evolve it."
"Many people are looking for the "next big language." The next big language is already here, but it isn't a single language. It is the collection of ideas above (plus probably some I missed) as manifested in Java.next. -- Does the transition to Java.next deserve the name "big"? Absolutely. In my experience, the move from Java to Java.next is every bit as big as the previous tectonic shifts in the industry, both in learning curve and in productivity advantages once you make the transition."