d********t
发帖数: 9628 | |
l*********s
发帖数: 5409 | 2 use java when you need the code to run fast; use python when you need to
write code fast. |
a***n
发帖数: 538 | 3 能用python的地方就不要用java。不过java的程序比较容易读懂。 |
d********t
发帖数: 9628 | 4 RE
【在 l*********s 的大作中提到】
: use java when you need the code to run fast; use python when you need to
: write code fast.
|
Y**G
发帖数: 1089 | 5 搭积木的时候，积木用Java来做，Python是胶水。
【在 d********t 的大作中提到】
: 比如什么情况下用什么好。谢谢!
|
r*g
发帖数: 3159 | 6 use python if you can;
use Java if you have to.
【在 d********t 的大作中提到】
: 比如什么情况下用什么好。谢谢!
|
r***y
发帖数: 4379 | 7 需要Java, groovy 是最好的胶水, 用 python 干嘛?
python 的缩进真的很蛋疼
【在 d********t 的大作中提到】
: 比如什么情况下用什么好。谢谢!
|
c***d
发帖数: 996 | 8 I am by no means java or python expert. However this is what I have seen
people doing:
1. use java if you have a lot of async operation
2. use java if you have a big team, long delivery and deployment cycle
3. use java if you do hadoop
4. use java if you mainly interface with xml data.
For anything else you can pretty much use python.
【在 d********t 的大作中提到】
: 比如什么情况下用什么好。谢谢!
|
l**********n
发帖数: 8443 | |
d********t
发帖数: 9628 | 10 啥是node?不会。
【在 l**********n 的大作中提到】
: 为什么不用node？
|
|
|
a***n
发帖数: 538 | 11 没觉得1和4 java有什么优势啊。
【在 c***d 的大作中提到】
: I am by no means java or python expert. However this is what I have seen
: people doing:
: 1. use java if you have a lot of async operation
: 2. use java if you have a big team, long delivery and deployment cycle
: 3. use java if you do hadoop
: 4. use java if you mainly interface with xml data.
: For anything else you can pretty much use python.
|
g*****g
发帖数: 34805 | 12 For most jobs, you don't decide what language to use. |
a***n
发帖数: 538 | 13
SOA以后，自由度还是挺大的。
【在 g*****g 的大作中提到】
: For most jobs, you don't decide what language to use.
|
z****e
发帖数: 54598 | 14 this is true
but for most python users
they dont even know what actually soa is
【在 a***n 的大作中提到】
:
: SOA以后，自由度还是挺大的。
|
W***o
发帖数: 6519 | 15 yep, what's SOA anyhow?
【在 z****e 的大作中提到】
: this is true
: but for most python users
: they dont even know what actually soa is
|
g*****g
发帖数: 34805 | 16 SOA only means different teams may choose to use different languages.
However, within a team, you probably have to stick to what's already there.
Your teammates ain't willing to understand/maintain your Python code if they
are more comfortable with Java, vice versa.
【在 a***n 的大作中提到】
:
: SOA以后，自由度还是挺大的。
|
n****1
发帖数: 1136 | 17 最好是包产到户, 每个service由一个人负责, 责任最明确, 也最自由.
.
they
【在 g*****g 的大作中提到】
: SOA only means different teams may choose to use different languages.
: However, within a team, you probably have to stick to what's already there.
: Your teammates ain't willing to understand/maintain your Python code if they
: are more comfortable with Java, vice versa.
|
z****e
发帖数: 54598 | 18 for software engineering projects
u have to code in structural and modular ways
which is pretty much like oo
for java, u HAVE TO think and do in this way
but for other language programmers
people will probably not bother to do that
and this freedom could be a huge problem which
may cause ur team including u, ur manager and ur subordinates
lose their jobs in future |
g*****g
发帖数: 34805 | 19 Personnel change all the time. You may want to make a simple change on a
service your teammate's responsible and you'd be slowed down if it's a
language you don't know well. While it's technically possible, the
management definitely want to minimize the risk for knowledge transfer.
Typically UI team, backend team, UI team are free to pick their own stack,
but within a team it's usually consistent.
【在 n****1 的大作中提到】
: 最好是包产到户, 每个service由一个人负责, 责任最明确, 也最自由.
:
: .
: they
|
d*******r
发帖数: 3299 | 20 那就是理论上SOA的话，可以一个人负责一个service，然后用自己喜欢的语言或者工具
了(当然别用太非主流的)，只要能处理人员离职的情况就行。
可不可以每个人负责一个service，但是另外有1~2个backup的人，要求此service的主
要负责人教会backup的人能理解和维护主要负责人的代码。
【在 g*****g 的大作中提到】
: Personnel change all the time. You may want to make a simple change on a
: service your teammate's responsible and you'd be slowed down if it's a
: language you don't know well. While it's technically possible, the
: management definitely want to minimize the risk for knowledge transfer.
: Typically UI team, backend team, UI team are free to pick their own stack,
: but within a team it's usually consistent.
|
|
|
q*c
发帖数: 9453 | 21
学习全新的语言， 特别是架构， 大队库， 等等等等dependency, 还要能 maintain,
debug, extend....
你觉得要多少时间？ 作为管理层如果让这样的事情大量发生， 就是愚蠢， 就是出钱
在帮社会培养人， 而不是为自己服务。
【在 d*******r 的大作中提到】
: 那就是理论上SOA的话，可以一个人负责一个service，然后用自己喜欢的语言或者工具
: 了(当然别用太非主流的)，只要能处理人员离职的情况就行。
: 可不可以每个人负责一个service，但是另外有1~2个backup的人，要求此service的主
: 要负责人教会backup的人能理解和维护主要负责人的代码。
|
b*******s
发帖数: 5216 | 22 这不就是亚麻10年前做的嘛
,
【在 q*c 的大作中提到】
:
: 学习全新的语言， 特别是架构， 大队库， 等等等等dependency, 还要能 maintain,
: debug, extend....
: 你觉得要多少时间？ 作为管理层如果让这样的事情大量发生， 就是愚蠢， 就是出钱
: 在帮社会培养人， 而不是为自己服务。
|
q*c
发帖数: 9453 | 23 呵呵， 我们以前组里面有个 senior, 就爱用 ruby. 别人都 java 他上 rails,
active scalf 之类的。
不久就被开了。 去了微软。
亚麻是 SOA, 但是可不许你胡乱用难以维护的自己的轮子。
【在 b*******s 的大作中提到】
: 这不就是亚麻10年前做的嘛
:
: ,
|
