31–40 of 65 posts
"We're located in downtown San Francisco and have a sick office overlooking Market St." hope sick office is a typo, must be slick office
Also US colloquial for very awesome, good, etc. Just like 'sweet'. http://www.urbandictionary.com/define.php?term=sick
It's hard to know all the details but it seems like most other video providers* scale by using http caching [max age + etags] with a CDN. Language performance isn't really the bottleneck remote calls are much slower :/ I have never hosted/written a django app, do people typically run a request in a thread in django? I thought python had a GIL just like Ruby (1.9+). I wouldn't recommend using something like rails to s…
Depends on the handler, mod_wsgi allows for m:n (mixing threads and processes) for instance.
> I thought python had a GIL just like Ruby (1.9+).
That's correct, but any C IO (such as DB queries) will generally release the GIL, which allows other threads to run.
(technically, CPython has a GIL, Python-the-language does not mandate it and neither Jython nor IronPython use a GIL. Pypy also has a gil currently, but Armin has started exploring STM to see if it would be a good replacement)
I wonder what the motivation is. RoR is more mature and it otherwise is a fairly lateral port in terms of features and speed. Both are dynamically typed and tremendously slow compared to the right .net or JVM stack. That would be my main criteria for stack selection in a project of this magnitude.
Really? Really?!?
https://rails.lighthouseapp.com/projects/8994/tickets/1203
Marking a bug as "wontfix" because the developers of the RoR platform are arrogant enough to say, and I quote, "[...] figure out what other software is putting that version in your environment and stop it from doing so" is now called mature?
The dialogue on this bug alone was enough for me to put RoR in my rear-view mirror and not look back.
Which would you rather use: a tool which demands it is the only tool on your system which can set environment variables (RoR), or a tool which plays well with others (Django)?
I switch from Rails to Django a while ago. On a feature base the two frameworks are equals. I explained it in depth in this video http://vimeo.com/31083901 ( It's in Italian,mf.Du you speak it?! :-) ). Basicaly I turn on django beacuse I prefer Python to Ruby: again the two languages starts from the same assumptions ( Guido also told that ) it's just my personal taste. Also django do things THE WAY I like more. For e…
You mean "turned to".
I wonder what the motivation is. RoR is more mature and it otherwise is a fairly lateral port in terms of features and speed. Both are dynamically typed and tremendously slow compared to the right .net or JVM stack. That would be my main criteria for stack selection in a project of this magnitude.
> RoR is more mature [...] Really? Really?!? https://rails.lighthouseapp.com/projects/8994/tickets/1203 Marking a bug as "wontfix" because the developers of the RoR platform are arrogant enough to say, and I quote, "[...] figure out what other software is putting that version in your environment and stop it from doing so" is now called mature? The dialogue on this bug alone was enough for me to put RoR in my rear-vie…
They just need to rename the environment variable into something like RAILS_VERSION instead, as suggested by several commenters in that issue. Such a simple fix, I don't understand why they won't do that.
I wonder what the motivation is. RoR is more mature and it otherwise is a fairly lateral port in terms of features and speed. Both are dynamically typed and tremendously slow compared to the right .net or JVM stack. That would be my main criteria for stack selection in a project of this magnitude.
> RoR is more mature [...] Really? Really?!? https://rails.lighthouseapp.com/projects/8994/tickets/1203 Marking a bug as "wontfix" because the developers of the RoR platform are arrogant enough to say, and I quote, "[...] figure out what other software is putting that version in your environment and stop it from doing so" is now called mature? The dialogue on this bug alone was enough for me to put RoR in my rear-vie…
Earlier quoted context omitted.
> RoR is more mature [...] Really? Really?!? https://rails.lighthouseapp.com/projects/8994/tickets/1203 Marking a bug as "wontfix" because the developers of the RoR platform are arrogant enough to say, and I quote, "[...] figure out what other software is putting that version in your environment and stop it from doing so" is now called mature? The dialogue on this bug alone was enough for me to put RoR in my rear-vie…
Wow, completely agree. They just need to rename the environment variable into something like RAILS_VERSION instead, as suggested by several commenters in that issue. Such a simple fix, I don't understand why they won't do that.
1) VERSION is a horrible name for a non-transient environment variable. It's fine if you're just using it on a per command basis (as rails does with 'rake db:migrate VERSION=123') but some app has stuck a ridiculously generic word into a global namespace. 2) (trivial) RAILS_VERSION would make no sense because it's the migration number you want to set your database too.
Any non-transient variable that you need to set should be specific enough to not conflict with other apps using the same namespace.
If anyone should go fixing things it's the fool who permanently stuck a variable called VERSION in their users global environment hash.
I agree that there is a problem and that it is affecting rails users. But, if for example some whacko was running around slapping all rails users with large fish would it be the rails dev teams responsibility to stop him? No.
No development team should have to tailor their app to compensate for the stupidity of one ignorant developer who couldn't think about the ecosystem that we all have to share. The only exception to this is when the idiot developer got a job building your OS...
Earlier quoted context omitted.
They could gain in productivity and ease of support
You're implying that python is more productive than ruby? I've never heard that claim before.
One possible reason for this change is that Justin.tv has long used Twisted ( http://twistedmatrix.com/trac/ ) for their network engine, and Twisted is written in Python. I'm not sure if they're still using Twisted, but if they are there might be some advantages to using Python for their web layer as well.
I doubt just reusing the twisted code inside the django app makes much sense for that reason (nor does the other way round).