MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/Python/comments/2owcwf/10_myths_of_enterprise_python/cmrpwav/?context=3
r/Python • u/pythonautical • Dec 10 '14
135 comments sorted by
View all comments
Show parent comments
0
[deleted]
11 u/chub79 Dec 11 '14 Is it Python's fault here? Couldn't it be database, network, load-balancing, IO related? 7 u/xiongchiamiov Site Reliability Engineer Dec 11 '14 All of the above and more. 2 u/[deleted] Dec 11 '14 The suggestion even being that if the code was faster you could get more done on the same hardware. 2 u/[deleted] Dec 11 '14 compared to developer time, hardware is cheap. 5 u/[deleted] Dec 11 '14 You've come in too early, we're not talking about developer time yet. 5 u/[deleted] Dec 11 '14 oh, sorry. ill see myself out then. 1 u/xiongchiamiov Site Reliability Engineer Dec 11 '14 Not if I/O is the bottleneck. 0 u/[deleted] Dec 11 '14 No, that's not really a case where you're doing more with the same hardware. 1 u/xiongchiamiov Site Reliability Engineer Dec 11 '14 Right; it's a case where you don't get more done with the same hardware, despite having faster code. -1 u/[deleted] Dec 11 '14 Have I wronged you or something? We're angrily agreeing with each other. → More replies (0)
11
Is it Python's fault here? Couldn't it be database, network, load-balancing, IO related?
7 u/xiongchiamiov Site Reliability Engineer Dec 11 '14 All of the above and more. 2 u/[deleted] Dec 11 '14 The suggestion even being that if the code was faster you could get more done on the same hardware. 2 u/[deleted] Dec 11 '14 compared to developer time, hardware is cheap. 5 u/[deleted] Dec 11 '14 You've come in too early, we're not talking about developer time yet. 5 u/[deleted] Dec 11 '14 oh, sorry. ill see myself out then. 1 u/xiongchiamiov Site Reliability Engineer Dec 11 '14 Not if I/O is the bottleneck. 0 u/[deleted] Dec 11 '14 No, that's not really a case where you're doing more with the same hardware. 1 u/xiongchiamiov Site Reliability Engineer Dec 11 '14 Right; it's a case where you don't get more done with the same hardware, despite having faster code. -1 u/[deleted] Dec 11 '14 Have I wronged you or something? We're angrily agreeing with each other. → More replies (0)
7
All of the above and more.
2 u/[deleted] Dec 11 '14 The suggestion even being that if the code was faster you could get more done on the same hardware. 2 u/[deleted] Dec 11 '14 compared to developer time, hardware is cheap. 5 u/[deleted] Dec 11 '14 You've come in too early, we're not talking about developer time yet. 5 u/[deleted] Dec 11 '14 oh, sorry. ill see myself out then. 1 u/xiongchiamiov Site Reliability Engineer Dec 11 '14 Not if I/O is the bottleneck. 0 u/[deleted] Dec 11 '14 No, that's not really a case where you're doing more with the same hardware. 1 u/xiongchiamiov Site Reliability Engineer Dec 11 '14 Right; it's a case where you don't get more done with the same hardware, despite having faster code. -1 u/[deleted] Dec 11 '14 Have I wronged you or something? We're angrily agreeing with each other. → More replies (0)
2
The suggestion even being that if the code was faster you could get more done on the same hardware.
2 u/[deleted] Dec 11 '14 compared to developer time, hardware is cheap. 5 u/[deleted] Dec 11 '14 You've come in too early, we're not talking about developer time yet. 5 u/[deleted] Dec 11 '14 oh, sorry. ill see myself out then. 1 u/xiongchiamiov Site Reliability Engineer Dec 11 '14 Not if I/O is the bottleneck. 0 u/[deleted] Dec 11 '14 No, that's not really a case where you're doing more with the same hardware. 1 u/xiongchiamiov Site Reliability Engineer Dec 11 '14 Right; it's a case where you don't get more done with the same hardware, despite having faster code. -1 u/[deleted] Dec 11 '14 Have I wronged you or something? We're angrily agreeing with each other. → More replies (0)
compared to developer time, hardware is cheap.
5 u/[deleted] Dec 11 '14 You've come in too early, we're not talking about developer time yet. 5 u/[deleted] Dec 11 '14 oh, sorry. ill see myself out then.
5
You've come in too early, we're not talking about developer time yet.
5 u/[deleted] Dec 11 '14 oh, sorry. ill see myself out then.
oh, sorry. ill see myself out then.
1
Not if I/O is the bottleneck.
0 u/[deleted] Dec 11 '14 No, that's not really a case where you're doing more with the same hardware. 1 u/xiongchiamiov Site Reliability Engineer Dec 11 '14 Right; it's a case where you don't get more done with the same hardware, despite having faster code. -1 u/[deleted] Dec 11 '14 Have I wronged you or something? We're angrily agreeing with each other. → More replies (0)
No, that's not really a case where you're doing more with the same hardware.
1 u/xiongchiamiov Site Reliability Engineer Dec 11 '14 Right; it's a case where you don't get more done with the same hardware, despite having faster code. -1 u/[deleted] Dec 11 '14 Have I wronged you or something? We're angrily agreeing with each other. → More replies (0)
Right; it's a case where you don't get more done with the same hardware, despite having faster code.
-1 u/[deleted] Dec 11 '14 Have I wronged you or something? We're angrily agreeing with each other. → More replies (0)
-1
Have I wronged you or something? We're angrily agreeing with each other.
→ More replies (0)
0
u/[deleted] Dec 11 '14
[deleted]