Live data from Hacker News

Justin.tv porting their site from Rails to Django?

djangohire.com

21–30 of 65 posts

Re: Justin.tv porting their site from Rails to Django?

#21

"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

now I understand why natural language processing is tough, nuances, context and downvotes

Re: Justin.tv porting their site from Rails to Django?

#22

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…

Use C++, Fortran ,Lisp ,Scala what ever you want: just deliver good software.

Absolutely

Re: Justin.tv porting their site from Rails to Django?

#23
What is justin using for streaming these days? Wowza? Something they built themselves (I know they used a custom built python solution initially, but they moved to something else along the way). Are they using ffmpeg to transcode the high bitrate game streams to the lower bitrate streams for viewers with slower connections? It's been a long time since that high scalability article came out.

Re: Justin.tv porting their site from Rails to Django?

#24
post #13
post #11

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.

Really? I've heard both that claim and it's c.ounterclaim several times and come to the conclusion that it's an interesting yet ultimately futile discussion.

Re: Justin.tv porting their site from Rails to Django?

#26

Not sure if they will gain a lot of performance from this transition...according to shootout ( http://shootout.alioth.debian.org/u64q/which-programming-lan... ) python is only few % faster than ruby. Maybe they should consider porting their entire ecosystem to JVM as twitter did it.

performance of a web app is quite likely more dependent on factors other than the raw interpreter speed, e.g. straight rack apps could easily be five times faster than rails apps using the same interpreter.

Re: Justin.tv porting their site from Rails to Django?

#27

"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

You mean their office is "the shit"!

Re: Justin.tv porting their site from Rails to Django?

#28

"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 been used here in the UK too since as far as I can remember

Re: Justin.tv porting their site from Rails to Django?

#29
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.

Re: Justin.tv porting their site from Rails to Django?

#30

Not sure if they will gain a lot of performance from this transition...according to shootout ( http://shootout.alioth.debian.org/u64q/which-programming-lan... ) python is only few % faster than ruby. Maybe they should consider porting their entire ecosystem to JVM as twitter did it.

The thing about the programming language shootout is that the benchmarks are optimized to within an inch of their life, and in particular don't generate much garbage. This may have changed, but last time I checked (MRI) Ruby's garbage collector was _stunningly_ slow.
Post reply on HN