AI Buying Macs? Why Apple Has Unexpectedly Become an 'AI Infrastructure Stock'
We explain why OpenAI has purchased tens of thousands of Mac Minis and Mac Studios, and what this means for our daily lives and the advancement of AI technology.
Tag: Computer
Effective Kotlin - 針對具有多個處理步驟的大型集合，優先使用 Sequence
摘要 立即求值（Eager evaluation）與延遲求值（Lazy evaluation）。順序很重要。像 listOf 這類 iterable 結構的結果，與 sequenceOf 的結果值是不一樣的。sequenceOf(1,2,3) .filter { print("F...
Effective Kotlin - 处理大型集合时，若有多个处理步骤，请优先使用 Sequence
总结：即时求值 (Eager evaluation) 与 延迟求值 (Lazy evaluation) 的区别。顺序很重要，listOf 等 iterable 结构的结果与 sequenceOf 的结果不同。sequenceOf(1,2,3) .filter { print("F...
Effective Kotlin - Prefer Sequence for big collections with more than one processing step
Summary Eager evaluation vs Lazy evaluation Order is important listOf 와 같은 iterable 형태의 구조의 결과와 sequenceOf 의 결과 값은 다릅니다. sequenceOf(1,2,3) .filter { print("F...
Effective Kotlin - 複数の処理ステップがある大きなコレクションにはSequenceを推奨
要約 Eager evaluation（先行評価）とLazy evaluation（遅延評価） 順序は重要です listOfのようなIterableな構造の結果とsequenceOfの結果は異なります。 sequenceOf(1,2,3) .filter { print("F...
Effective Kotlin - Prefer Sequence for big collections with more than one processing step
Summary Eager evaluation vs Lazy evaluation Order is important The result of an iterable structure like listOf is different from that of sequenceOf. sequenceOf(1,2,3) .filter { print("F...
屬性
Properties
Effective Kotlin - 屬性應代表狀態，而非行為
Kotlin 的屬性看起來與 Java 的欄位相似。然而，它們擁有不同的概念。即使以相同的方式使用，Kotlin 的屬性也能實現更多功能...
속성
Properties
Effective Kotlin - Properties should represent state, not behavior
코틀린의 속성은 자바의 필드와 비슷해 보입니다. 그렇지만, 서로 다른 컨셉을 갖고 있습니다. //Kotlinproperty var name:String?=null //Javafield String name=null; 같은 방식으로 사용할지라도, 코틀린의 속성은 좀 더 많은 것을 할...
プロパティ
Properties
Effective Kotlin - プロパティは動作ではなく状態を表すべき
KotlinのプロパティはJavaのフィールドと似て見えますが、異なる概念を持っています。//Kotlinproperty var name:String?=null //Javafield String name=null; 同じ方法で使用するように見えても、Kotlinのプロパティはより多くのことができます...
Effective Kotlin - Properties should represent state, not behavior
Kotlin properties may look similar to Java fields, but they have different concepts. Even if you use them in the same way, Kotlin properties can do much more...