- 主题:Apple从Java转向Swift:硬件利用率降低 50%,内存减少 90%,吞
那倒是没有
【 在 jsdbart 的大作中提到: 】
: swift开发,要收钱才给你用来开发的吧?
--
FROM 120.244.14.103
啥叫硬件利用率降低50%?
【 在 bsxfun 的大作中提到: 】
: An internal Apple developer team revealed in a new case study that “Java’s memory management approach no longer aligns with our growing demands and efficiency goals.”
: The team is now looking for more efficient languages, and in this example chose Swift, achieving a claimed 50 percent reduction in hardware utilization, 90 percent less memory, and 40 percent more throughput.
: It is possible that another aspect of the port, a near 85 percent reduction in lines of code, was more significant than the memory management. The team identified aspects of Swift which resulted in cleaner and more concise code, including an emphasis on protocols (interfaces) rather than inheritance, the use of async and await for concurrency, and type safety which eliminates the need for null checks.
--
FROM 36.250.214.*
应该是同性能下硬件资源的使用率。
【 在 cn62 的大作中提到: 】
: 啥叫硬件利用率降低50%?
: protocols (interfaces) rather than inheritance, the use of async and await for concurrency, and type safety which eliminates the need for null checks.
--
FROM 129.145.50.*
内存减少这点靠谱
其他的……不太信啊
【 在 bsxfun 的大作中提到: 】
: An internal Apple developer team revealed in a new case study that “Java’s memory management approach no longer aligns with our growing demands and efficiency goals.”
: The team is now looking for more efficient languages, and in this example chose Swift, achieving a claimed 50 percent reduction in hardware utilization, 90 percent less memory, and 40 percent more throughput.
: It is possible that another aspect of the port, a near 85 percent reduction in lines of code, was more significant than the memory management. The team identified aspects of Swift which resulted in cleaner and more concise code, including an emphasis on p
: ...................
--
FROM 119.57.91.*
同感
说的糙点
看内存占用,cpu占用
再省掉java框架的一些适配代码,
没啥了
真做项目了,这些指标都要打折扣
- 来自 水木社区APP v3.5.7
【 在 lalula 的大作中提到: 】
: 内存减少这点靠谱
: 其他的……不太信啊
--
FROM 223.104.41.*
得 刚学了点Java,写了点程序,你跟我说这个。
难道又得学swift,学了能找到工作嘛
【 在 bsxfun 的大作中提到: 】
: An internal Apple developer team revealed in a new case study that “Java’s memory management approach no longer aligns with our growing demands and efficiency goals.”
: The team is now looking for more efficient languages, and in this example chose Swift, achieving a claimed 50 percent reduction in hardware utilization, 90 percent less memory, and 40 percent more throughput.
: It is possible that another aspect of the port, a near 85 percent reduction in lines of code, was more significant than the memory management. The team identified aspects of Swift which resulted in cleaner and more concise code, including an emphasis on protocols (interfaces) rather than inheritance, the use of async and await for concurrency, and type safety which eliminates the need for null checks.
--
FROM 36.63.114.*
Java为啥不行了?
--
FROM 120.244.2.*
老了,向后兼容性导致java承担了巨大的历史包袱,很多改进非常迟缓。
比如备受诟病的Java 对象模型,普通对象 (Object) 需存储对象头(16-24字节)+ 引用(4-8字节),导致小对象(如 Point、Complex)内存利用率极低,并且对象通过堆内存引用访问,导致CPU 缓存局部性差(频繁 cache miss)以及无法利用寄存器优化。
而JEP 401: Value Classes and Objects就是为了改进这个问题,搞了好几年了,貌似已经进入Preview阶段。
在比如另外一个容易把新手搞混的(尤其是从C#或者C++转过来的)Java泛型:擦除法实现,并且不支持基本类型。这个改动会涉及很多方面,比如JEP 218: Generics over Primitive Types以及上面的JEP 401都与此有关。
【 在 dawndawn001 的大作中提到: 】
: Java为啥不行了?
--
FROM 223.166.244.*
?
【 在 bsxfun 的大作中提到: 】
: 老了,向后兼容性导致java承担了巨大的历史包袱,很多改进非常迟缓。
: 比如备受诟病的Java 对象模型,普通对象 (Object) 需存储对象头(16-24字节)+ 引用(4-8字节),导致小对象(如 Point、Complex)内存利用率极低,并且对象通过堆内存引用访问,导致CPU 缓存局部性差(频繁 cache miss)以及无法利用寄存器优化。
: 而JEP 401: Value Classes and Objects就是为了改进这个问题,搞了好几年了,貌似已经进入Preview阶段。
: ...................
--
FROM 120.244.2.*