|
Socoder -> Python/Ruby -> Something about Ruby |
|
| Thu, 17 May 2007, 06:34 | |
Jayenkai
|
Recently I changed the script so you couldn't post new forum topics to section's you're not supposed to. In order to do this, it checks if there's other posts of the same type in that section. If not, it won't let you post. This has had the unfortunate side effect of disabling posting to unused areas! As such, the Ruby section is currently completely unusable! I only just noticed this when I added the Basic Basement. Sorry about that! But I guess no-one noticed anyway! This post is here to open up the Ruby area! -=-=- ''Load, Next List!'' 
|
| Thu, 17 May 2007, 07:11 | |
JL235
|
Yet another attempt to silence the coming wake of Ruby.
|
| Thu, 17 May 2007, 07:17 | |
|
Jayenkai
|
Aaah, but did you, Mr Ruby, even notice it was unpostable?
-=-=- ''Load, Next List!''
|
| Sat, 18 Dec 2010, 14:32 | |
|
dna |
I may take a good look at this Ruby language having just discovered that twitter is based completely upon Ruby. Slightly astounding. -=-=- DNA |
| Sat, 18 Dec 2010, 16:02 | |
|
JL235
|
Actually Twitter no longer uses Ruby exclusively. Their twitter queue system (which is the core to their service) is now built using Scala. Scala is a static language that runs on the JVM. In many ways it's designed to be a successor to Java itself (and in some benchmarks it outperforms Java on the JVM). |
| Sat, 18 Dec 2010, 16:12 | |
Stealth
|
I heard Ruby doesn't scale very well (or maybe it was RoR).
-=-=- Quit posting and try Google.
|
| Sat, 18 Dec 2010, 16:24 | |
|
JL235
|
I've heard that too, but the only concrete example I've seen is with Twitter where clearly they must be handling millions of tweets a day (at least). It's also just their queue system which they changed, I believe the rest of twitter still runs on top of RoR. Also anything stated 3 or more years ago about Ruby's speed should be taken with a big pinch of salt. Ruby 1.9 is at least 100s of times faster then the previous version, and is only about a year old. JRuby is also 100s to 1000s of times faster whilst again only being really usable for about 3 years. JRuby will also be significantly faster in 6 months to a year when Java 7 comes out as it adds JVM support for calling methods in dynamic languages. I believe JRuby already has support for using this bytecode, and the speed up is because it allows JRuby to remove a lot of the overhead it currently performs in order to allow a dynamic language to run on a statically typed runtime. |
|
|
| |||
|
| ||||