their problem was using weird and heavy frameworks.
i wouldn't consider djangob for anything other than a heavily cached content site.
seems like it's a company that just plow through problems. i bet whatever the problem is in go they will find only next week.
python 2.7 and 3 have a marvelous, but not very well documented, multiprocessor module. it gives you more performance for that the cython and other shenanigans.
but i guess using the existing tool right doesn't give promotions.
... yeah I'm making a lot of assumptions about then but that's just because I'm salty today. they should still learn to use python multiprocessing module. :)
i wouldn't consider djangob for anything other than a heavily cached content site.
seems like it's a company that just plow through problems. i bet whatever the problem is in go they will find only next week.
python 2.7 and 3 have a marvelous, but not very well documented, multiprocessor module. it gives you more performance for that the cython and other shenanigans.
but i guess using the existing tool right doesn't give promotions.
... yeah I'm making a lot of assumptions about then but that's just because I'm salty today. they should still learn to use python multiprocessing module. :)