3 ms·

Instagram (Facebook) ate it. Would be nice, by the way, if they could release the source code. Having such an example of a Flask app would be very useful for

Instagram (Facebook) ate it. Would be nice, by the way, if they could release the source code. Having such an example of a Flask app would be very useful for the community.

mburst 10y ago
I believe Instagram uses Django https://engineering.instagram.com/web-service-efficiency-at-instagram-with-python-4976d078e366 https://engineering.instagram.com/web-service-efficiency-at-... In any case it's still a pretty popular site/app on it's own. I don't see Facebook killing it anytime soon.
- cunotaco 10y ago
  No, I'm talking about Vine. They use Flask, and if they are not going to use the codebase any longer... Personally I like having a big codebase as an architectural reference when I'm trying to learn a new framework. The Patreon source code (Flask too) is public, by the way.
  - misiti3780 10y ago
    it is ? can you provide a link. it was hacked right ?
    - deleted 10y ago
      [deleted]
    - cunotaco 10y ago
      Yes it was hacked. Here's a list of the files: https://goo.gl/3K1VVF https://goo.gl/3K1VVF And you also have here a direct download of the full leak, including the database: https://archive.org/details/B93B1C2921EFF0846DA268968755D01B6E9698DA https://archive.org/details/B93B1C2921EFF0846DA268968755D01B...
- r3bl 10y ago
  I believe he was referring to Vine in the second part of his comment, not Instagram.
- gogopuppygogo 10y ago
  Here is a fun read on how Django came to be: http://www2.ljworld.com/news/2015/jul/09/happy-birthday-django/ http://www2.ljworld.com/news/2015/jul/09/happy-birthday-djan...
NightMKoder 10y ago
It wouldn't be that good of a reference. Full disclosure: I led the backend team at Vine a while back. Vine didn't use a lot of Flask. The main piece that was used was routing (i.e. @app.route). Everything else was custom. Even flask.g was replaced with something that can propagate context properly across greenlets (the method of concurrency we chose), without a lot of overhead. If you're curious, that piece eventually became https://github.com/mikekap/gbatchy https://github.com/mikekap/gbatchy though I can't say that's well supported now. The main takeaway from that codebase is: async needs to be part of the language. Having it be bolted on leads to...unpleasant hacks. I think Python 3.5+ is heading in the right direction there, but Vine was stuck in 2.7-land forevermore (mostly because we wanted to keep pypy compatibility even though pypy was never rolled out; not the best reason).
- cunotaco 10y ago
  Thank you for the insight, it really is appreciated.

Instagram (Facebook) ate it. Would be nice, by the way, if they could release the source code. Having such an example of a Flask app would be very useful for the community.

mburst 10y ago

I believe Instagram uses Django https://engineering.instagram.com/web-service-efficiency-at-instagram-with-python-4976d078e366 https://engineering.instagram.com/web-service-efficiency-at-... In any case it's still a pretty popular site/app on it's own. I don't see Facebook killing it anytime soon.

cunotaco 10y ago
No, I'm talking about Vine. They use Flask, and if they are not going to use the codebase any longer... Personally I like having a big codebase as an architectural reference when I'm trying to learn a new framework. The Patreon source code (Flask too) is public, by the way.
- misiti3780 10y ago
  it is ? can you provide a link. it was hacked right ?
  - deleted 10y ago
    [deleted]
  - cunotaco 10y ago
    Yes it was hacked. Here's a list of the files: https://goo.gl/3K1VVF https://goo.gl/3K1VVF And you also have here a direct download of the full leak, including the database: https://archive.org/details/B93B1C2921EFF0846DA268968755D01B6E9698DA https://archive.org/details/B93B1C2921EFF0846DA268968755D01B...
r3bl 10y ago
I believe he was referring to Vine in the second part of his comment, not Instagram.
gogopuppygogo 10y ago
Here is a fun read on how Django came to be: http://www2.ljworld.com/news/2015/jul/09/happy-birthday-django/ http://www2.ljworld.com/news/2015/jul/09/happy-birthday-djan...

NightMKoder 10y ago

It wouldn't be that good of a reference. Full disclosure: I led the backend team at Vine a while back. Vine didn't use a lot of Flask. The main piece that was used was routing (i.e. @app.route). Everything else was custom. Even flask.g was replaced with something that can propagate context properly across greenlets (the method of concurrency we chose), without a lot of overhead. If you're curious, that piece eventually became https://github.com/mikekap/gbatchy https://github.com/mikekap/gbatchy though I can't say that's well supported now. The main takeaway from that codebase is: async needs to be part of the language. Having it be bolted on leads to...unpleasant hacks. I think Python 3.5+ is heading in the right direction there, but Vine was stuck in 2.7-land forevermore (mostly because we wanted to keep pypy compatibility even though pypy was never rolled out; not the best reason).

cunotaco 10y ago
Thank you for the insight, it really is appreciated.