| Issue 29: | Please add ruby support | |
|
1806 people starred this issue.
Comments by non-members will not trigger notification emails to users who starred this issue. |
Back to list |
Sign in to add a comment
|
Would prefer also rails support and merb, but just ruby itself would be a great first step. |
||||||||||
,
Apr 08, 2008
http://rack.rubyforge.org/ may be something to look into, since it was modeled after WSGI, thus merb and ramaze and other frameworks that use rack could be implemented. |
|||||||||||
,
Apr 08, 2008
I think java and ruby will work. And with java, jruby is a perfectly acceptable ruby implementation. I would prefer CRuby, but it would be nice to have java also. Some of us are multi-lingual like that. |
|||||||||||
,
Apr 08, 2008
The problem isn't a parallel to WSGI, it's a parallel to PyPy. PyPy is what allows the sandboxing that prevents system access and lets Google meter CPU usage. Unless Ruby has something similar, Google would have to engineer it on their own, and that's quite an effort. |
|||||||||||
,
Apr 09, 2008
Guys, they're counting stars (the one in the top left-hand corner) not +1 comments, please stop spamming so that others have a chance to post useful information. |
|||||||||||
,
Apr 09, 2008
Like this http://heroku.com/ |
|||||||||||
,
Apr 10, 2008
If you want Ruby on Rails, why don't you try out the Morph Application Platform? www.morphexchange.com |
|||||||||||
,
Apr 10, 2008
Please stop plusing this, and just Star it. Same effect, but it doesn't clutter the comments. Thanks! Also, every time you comment with +1 you are spamming everyone, which isn't very nice, thanks! |
|||||||||||
,
Apr 10, 2008
Can the priority move higher than medium? |
|||||||||||
,
Apr 10, 2008
The way to increase the priority is to have more stars than Perl ;) that's probably a very naive answer though. Someone should write some good stuff about why Ruby won't suck if implemented on GAE and post it here. Or write code that improves Ruby's CGI libraries. It's unlikely that RoR would get inside the App Engine because it relies heavily on persistent processes to not be slow. |
|||||||||||
,
Apr 10, 2008
Please! Just star, don't comment! We're getting lots of spam! |
|||||||||||
,
Apr 10, 2008
Stolen from another thread: Just a friendly reminder... if you're about to post a comment that says "me too!" or "you've got my vote" or "+1"... please just star this issue and leave the comments-space clean. When you star the issue, your vote counts. Issues with a larger number of people starring the issue are likely going to get more attention. More comments, however, are just going to clutter the system and annoy those who have already starred the issue, possibly encouraging them to unstar the issue, lowering its perceived importance. Again, comments should be used to update progress on the issue itself, not for voting... please leave this to the star. Thanks. I apoligize for my earlier +1 :-P |
|||||||||||
,
Apr 10, 2008
Unstarring. I don't need an email every time someone has to declare to the world that he's an idiot. |
|||||||||||
,
Apr 10, 2008
(No comment was entered for this change.)
Labels: -Type-Defect Type-Feature
|
|||||||||||
,
Apr 10, 2008
Please stop commenting with just +1. If you're interested in this feature, click the star to the left of the name near the top. There are plenty of people who want to be notified if anything comes of this, but don't want to get an email with every "+1" that gets posted. Google Code's issue tracker interface is designed around prioritizing the number of people who have starred an issue, not the number of "+1" comments that get added. |
|||||||||||
,
Apr 10, 2008
Sandbox for Ruby - http://code.whytheluckystiff.net/sandbox/ |
|||||||||||
,
Apr 10, 2008
Saying "+1" is counter-productive. You're spamming everyone who's starred the issue, causing people to unstar this issue, which devalues the issue. Stop "+1" spamming. Star the issue. The star. Beside the name of the issue at the top of this page. Click that. These comments are for discussion of the issue itself. Comment threads are terrible voting mechanisms. (and, following my own advice, I'm shutting up) |
|||||||||||
,
Apr 10, 2008
What I would like to see is a way the community can help do things like port Ruby to this environment. I'm sure there are special needs so what I would propose is to allow some sort of limited C API or something that the language must use during runtime as well as some simple call-backs or signals to handle. With that in place, people could spend their own time porting languages of their choice. So please, add ruby support by adding an open harness for new languages that we can work on. |
|||||||||||
,
Apr 10, 2008
Instead of unstarring, perhaps add a filter to mailbox: subject:(Issue 29 in googleappengine: Please add ruby support) action: Skip Inbox |
|||||||||||
,
Apr 10, 2008
How do you star it without commenting? You... you click the star. The blue outline of a star next to the issue at the top of the page. Click it. It becomes yellow and filled in. Noone gets spammed. This isn't rocket surgery. |
|||||||||||
,
Apr 10, 2008
Ruby support would be pretty awesome, but as I understand your execution model for AppEngine you'd most likely have to wait for Rubinius to be farther along to get a VM that can be reasonably sandboxed. Perhaps some of that famous 20% time can be applied to that project to help Ruby support in AppEngine along? |
|||||||||||
,
Apr 10, 2008
+ 1 Rails + Merb + DataMapper should be included as well. Yes.... Google is the most trusted name and the best ever. I vote for google as well. Google should make this as fst as possible to break the hype MS is creating for IronRuby. As pr my knowledge... for many years MS just adpots the prpven technology. I am sure they will adopt this AppEngine too. Google should make thuis fast to leave MS years behind. |
|||||||||||
,
Apr 11, 2008
mats.ekblom, they're doing the same thing in every other ticket. The Google guys might decide to just close these tickets down because of all the spam :P |
|||||||||||
,
Apr 11, 2008
This +1 madness inspired me to write a blog post: http://www.ryantm.com/blog/2008/04/11/more-evidence-that-programmers-arent-smarter-than-other-people/ |
|||||||||||
,
Apr 14, 2008
** NO FLAMEWARS PLEASE! ** Every time you add a comment it sends out an EMAIL to everybody. Our inboxes are filled with hundreds of useless mails that says "+1". We are drowning in SPAM :-( >>>>>>> TO VOTE FOR RUBY - DO THIS INSTEAD <<<<<<<<<<<< 1) Look for the blue outline of a star next to Issue 29: at the top of this page. 2) Click on it. The star becomes yellow and filled in. 3) Now you have voted for ruby. Well done :-) N O T E : It is the number of stars that counts, not the comments! Once again: DO **NOT** ADD A COMMENT (unless you have something IMPORTANT to say). IT SENDS AN EMAIL TO EVERYBODY ELSE!! |
|||||||||||
,
Apr 14, 2008
I just mailed code@google.com with this feedback and suggest those of you annoyed by the '+1 spam' let them know what you think as well. Those of you considering posting yet another '+1' comment, please refer to the previous comment #479. Date: Sat, Apr 12, 2008 at 1:31 PM Subject: Please fix '+1' SPAM To: code@google.com Hi, Can you please check comments for '+1' using something like (/\+\s*1/) and warn users to make use of the built in 'starring' functionality, giving them a chance to avoid spamming everyone. Here's a good example, where almost a thousand people are spammed with every '+1' post: http://code.google.com/p/googleappengine/issues/detail?id=29 Thanks, Sam |
|||||||||||
,
Apr 14, 2008
Please voice your support for issue comment filtering by *starring* Issue 203 |
|||||||||||
,
Apr 15, 2008
+1 spam and some of the related anti-spam comments removed. I'll remove the rest of the anti-spam comments once things have settled. As others have stated, star the issue if you're interested in showing your support. +1 and "me too!" posts don't have any positive impact, and only serve to annoy other users. Those concerned with why their comments were removed are free to contact me privately. |
|||||||||||
,
Apr 18, 2008
Justin, interesting that you say they're using PyPy (for the CPU monitoring). Do you have any links to info about this - can't find any. |
|||||||||||
,
Apr 19, 2008
Python est un excellent langage mais avoir le choix rendra google app meilleur !! Saigon |
|||||||||||
,
May 07, 2008
May be of interest: http://hackety.org/2008/05/05/sneakingRubyThroughGoogleAppEngine.html |
|||||||||||
,
May 19, 2008
Please add support for Ruby and web app framework sitting on the top of Ruby like: Rails, Merb etc .... I think adding also additional stacks of languages will position Google to become a leader in that space ... Openess and flexibility ... Also adding support for various admin and deployment tools, managed by community etc. could positon Google to be good ASP hosting provider even for evil corp apps :) Great job Google people, thank you for various solutions ... Robert K |
|||||||||||
,
Jun 17, 2008
+1 |
|||||||||||
,
Jul 04, 2008
+1 |
|||||||||||
,
Jul 04, 2008
+1 |
|||||||||||
,
Jul 04, 2008
rsalvado+joshuashen+jaikogu = 3 ;) I'm waiting for people that disagree with this issue to post "-1" comments! :) #415 blog post is really funny! |
|||||||||||
,
Jul 17, 2008
definitely would love this, got some really good stuff to upload |
|||||||||||
,
Jul 23, 2008
Actually the Freaky Freaky Sandbox would work. It does allow everything that PyPy does. (http://code.whytheluckystiff.net/sandbox/) |
|||||||||||
,
Jul 25, 2008
Please add support for Ruby |
|||||||||||
,
Jul 25, 2008
Pls add support for ruby. Thx. |
|||||||||||
,
Jul 26, 2008
Ruby please :) |
|||||||||||
,
Jul 29, 2008
Hopefully Google is already planning on supporting PHP. They are probably in the process of making a GQL PHP API and locking down PHP like they did for Python. |
|||||||||||
,
Aug 01, 2008
another vote for ruby |
|||||||||||
,
Aug 05, 2008
yep, vote for ruby... |
|||||||||||
,
Aug 07, 2008
I love ruby! |
|||||||||||
,
Aug 09, 2008
I love ruby! |
|||||||||||
,
Aug 10, 2008
Ruby! Ruby! Ruby! Ruby! Ruby! |
|||||||||||
,
Aug 10, 2008
Ruby rulles :) |
|||||||||||
,
Aug 21, 2008
It would be great to see Ruby support in App Engine ;) |
|||||||||||
,
Aug 27, 2008
-1, stay on python and add features. no reason for other languages |
|||||||||||
,
Aug 27, 2008
No reason of pricks like you. |
|||||||||||
,
Aug 28, 2008
One more vote for Ruby |
|||||||||||
,
Aug 29, 2008
I believe that language diversity is the key to this success. Not necessarily just Ruby, I'm talking about other languages too. Not everybody knows python, and not everybody should have to. |
|||||||||||
,
Sep 04, 2008
+1 for Ruby. |
|||||||||||
,
Sep 04, 2008
I think it's well within Google's power to add new languages, without hurting Python features. |
|||||||||||
,
Sep 16, 2008
+ 1 for Ruby |
|||||||||||
,
Sep 25, 2008
(No comment was entered for this change.)
Status: Acknowledged
|
|||||||||||
,
Oct 06, 2008
(No comment was entered for this change.)
Labels: Component-Languages
|
|||||||||||
,
Oct 21, 2008
Okay, what does status: acknowledged mean? |
|||||||||||
,
Nov 18, 2008
+1 for Ruby. |
|||||||||||
,
Nov 19, 2008
+1 comment. count me in. ooops. how do i vote? kidding. ;) |
|||||||||||
,
Nov 19, 2008
Sorry, think it's time for another of these posts ** NO FLAMEWARS PLEASE! ** Every time you add a comment it sends out an EMAIL to everybody. Our inboxes are filled with hundreds of useless mails that says "+1". We are drowning in SPAM :-( >>>>>>> TO VOTE FOR RUBY - DO THIS INSTEAD <<<<<<<<<<<< 1) Look for the blue outline of a star next to Issue 29: at the top of this page. 2) Click on it. The star becomes yellow and filled in. 3) Now you have voted for ruby. Well done :-) N O T E : It is the number of stars that counts, not the comments! Once again: DO **NOT** ADD A COMMENT (unless you have something IMPORTANT to say). IT SENDS AN EMAIL TO EVERYBODY ELSE!! |
|||||||||||
,
Nov 20, 2008
+1 |
|||||||||||
,
Nov 21, 2008
+ for ruby, ftw! :) |
|||||||||||
,
Nov 21, 2008
+ for ruby ! and rails |
|||||||||||
,
Nov 24, 2008
+1 |
|||||||||||
,
Dec 03, 2008
+1 |
|||||||||||
,
Dec 03, 2008
+1, please! |
|||||||||||
,
Dec 09, 2008
+1 |
|||||||||||
,
Jan 05, 2009
Would love to go back to ruby & start developing apps. |
|||||||||||
,
Jan 12, 2009
+1 ,please! Hope for the support for ruby! |
|||||||||||
,
Jan 16, 2009
* |
|||||||||||
,
Jan 27, 2009
please add ruby on rails |
|||||||||||
,
Feb 01, 2009
pls, pls, pls.... ruby+rails |
|||||||||||
,
Feb 25, 2009
ruby support is a must!! |
|||||||||||
,
Feb 25, 2009
Give me AppEngine for Ruby! Plz!! |
|||||||||||
,
Feb 25, 2009
And while we are at it: One "please click on the star and don't just write +1" message would suffice. @justin.fagnani With respect to sandboxing: Other than python, ruby has already __some__ support for that builtin -- see the -T command-line option. I personally would prefer java + jruby though. |
|||||||||||
,
Feb 26, 2009
Interesting library for google data on Ruby On Rails: http://code.google.com/intl/en/apis/gdata/articles/gdata_on_rails.html Seems that google have started to develop something for ruby/rails... Ah and please: + 1/0 for ruby ;) |
|||||||||||
,
Mar 15, 2009
add one from me |
|||||||||||
,
Mar 16, 2009
Issue 1152 has been merged into this issue. |
|||||||||||
,
Mar 16, 2009
Hint for people who are bored of +1-like comments. If you use Gmail, you can press M while a message is open, and mute the entire conversation. Bye bye comments. Please do that instead of un-starring this bug. |
|||||||||||
,
Mar 31, 2009
Ruby On Rails |
|||||||||||
,
Apr 05, 2009
Rack would be great. That would support Merb, Sinatra, and also home-made frameworks, and I think that's what Google is aiming for with Google App Engine (which is, for it to be customisable for developers). |
|||||||||||
,
Apr 08, 2009
What about JRuby ? Due to Java-Support you are able to use it right now. No need for native Ruby-Support anymore ? |
|||||||||||
,
Apr 08, 2009
See here for a few articles about JRuby on GAE by Ola Bini: http://olabini.com/blog/tag/gae/ |
|||||||||||
,
Apr 08, 2009
one more vote for ruby |
|||||||||||
,
Apr 11, 2009
one more vote for ruby, i love ruby so much. from China. |
|||||||||||
,
Apr 12, 2009
Ruby support would be a great thing. It's my favourite language ever. (And I have seen quite a lot of them come, stay and go.) |
|||||||||||
,
Apr 14, 2009
when ruby support ? |
|||||||||||
,
Apr 14, 2009
http://code.google.com/p/appengine-jruby/ http://olabini.com/blog/2009/04/jruby-on-rails-on-google-app-engine/ This is not native Ruby support, so it's probably slower than it should be. But it works. If you have time, please consider helping out. I wish I would. |
|||||||||||
,
Apr 15, 2009
Actually, JRuby is faster than MRI (the standard Ruby 1.8.x interpreter implemented in C) in most cases. I'd call this issue closed now that JRuby works. |
|||||||||||
,
Apr 15, 2009
ROR is my favorite! Hope I use it on appengine soon! |
|||||||||||
,
Apr 20, 2009
ghs.google.com has been blocked in some countries, which means that your users/clients in these countries are not able to access your GAE services with your own domain name. See http://code.google.com/p/googleappengine/issues/detail?id=1269 for more details. |
|||||||||||
,
May 12, 2009
yes,ruby supput is nc |
|||||||||||
,
May 13, 2009
Unfortunately, I do not think JRuby has 100% compatibility. Plus, Ruby 1.9.1 is much faster than JRuby. |
|||||||||||
,
May 22, 2009
Ruby support would be awesome. And also Rails please. |
|||||||||||
,
May 22, 2009
+1 on Ruby support - RoR/Sinatra would be excellent. |
|||||||||||
,
May 24, 2009
ditto for rails support! |
|||||||||||
,
May 24, 2009
Yes, ruby and frameworks would be great. Something that looks like Rack might integrate nicely with Rails, merb, sinatra, et. al. |
|||||||||||
,
May 26, 2009
Please add Ruby and RoR support |
|||||||||||
,
May 26, 2009
I like Ruby, though. |
|||||||||||
,
May 27, 2009
Yes!. RUBY! I need ruby ;) |
|||||||||||
,
May 28, 2009
I'd like to try Ruby. |
|||||||||||
,
May 31, 2009
Sinatra would be perfect for GAE.
Rails too. Unfortunately, even though Java has been added, JRuby does not have 100%
compatibility:
{:e => 'x', :a => 'e'}.collect{|k,v|puts "#{k.inspect} => #{v.inspect}"}
The code above works just fine in C Ruby, but does not work at all in JRuby.
|
|||||||||||
,
May 31, 2009
Devyn.Cairns: Odd, it seemed to work just fine when I ran it in JRuby a second ago, producing the exact same results as 1.8 and 1.9. |
|||||||||||
,
Jun 01, 2009
Hmm... It appears I was mistaken. But otherwise, C Ruby extensions do not work in JRuby, of course. So that makes many gems not work. Anyway, it would still be nice to have C Ruby. |
|||||||||||
,
Jun 01, 2009
C extensions would not work even if C Ruby were supported. |
|||||||||||
,
Jun 04, 2009
No, but I suppose you could send a request to Google for a gem to be installed. Then you could. Anyway, it doesn't really matter. But I really like the C Ruby implementation. I probably will just use JRuby, but I do hope that Google chooses to support Ruby. It's too bad they didn't choose to support Java first, because then the Python people would be forced to use Jython. |
|||||||||||
,
Aug 26, 2009
非常需要这个 |
|||||||||||
,
Aug 29, 2009
JRuby is better than the MRI, Google AppEngine already has support and it is quite easy: http://code.google.com/p/appengine-jruby/ |
|||||||||||
,
Sep 12, 2009
I definatly wouldn't mind ruby support Hell by the time it comes out i may actually be able to code rails effectively. |
|||||||||||
,
Oct 13, 2009
I think given jruby works on app engine now, you cant expect google to hack on the internals of MRI to get into a decent enough shape to run app engine on. |
|||||||||||
,
Oct 16, 2009
i want too |
|||||||||||
,
Oct 22, 2009
add it |
|||||||||||
,
Dec 01, 2009
ruby is a must |
|||||||||||
,
Dec 07, 2009
Ruby and Rails, pleeeeeease! |
|||||||||||
,
Dec 10, 2009
Rails 3 on App Engine: http://rails-primer.appspot.com/ |
|||||||||||
|
|
|||||||||||