【 以下文字转载自 SanFrancisco 讨论区 】 发信人: superdmv (你想咋的), 信区: SanFrancisco 标 题: 这个MIPS有他CEO说的那么好吗? 发信站: BBS 未名空间站 (Wed Sep 15 12:53:50 2010, 美东) MIPS vs ARM 1. 32/64 bit vs 32 bit 2. m-thread vs 1-thread; 3. more energy efficiency? http://seekingalpha.com/article/225279- ... n-monopoly MIPS Technology Challenges ARM's Cell Phone Chip Design Monopoly MIPS Technologies' (MIPS) stock has skyrocketed recently as it lays the groundwork to challenge ARM (ARMH), the dominant player in cell phone chip design.
i think mips has its catch since much more networking capabilities than arms . (Maybe my view is biased). But in terms of power, I think mips needs to work its way down before it can be implemented in cell phones.
【在 N***r 的大作中提到】 : 【 以下文字转载自 Joke 讨论区 】 : 发信人: xtxtxttchris (chris), 信区: Joke : 标 题: logic thinker : 发信站: BBS 未名空间站 (Tue May 31 11:59:54 2011, 美东) : i am a consultant :)
a*e
22 楼
这要贴标签吗? 你如果不知道,那真让人笑了。
【在 k***5 的大作中提到】 : 贴个标签就能说明一切?你是天真幼稚?
k*g
23 楼
Object oriented design / object oriented programming Namely, how to design and implement objects (classes) correctly in your ( employer's) choice of programming language. Elementary level: learn the must-follow guidelines in designing objects * Design of interfaces * Object Consistency / Invariants (how to ensure the object works correctly when its methods are called over and over again) * Visibility (public vs private) * It is convenient and sometimes necessary to split up a public method into several subroutines. Each of these subroutines may be unable to keep consistency. Thus, these subroutines must be private, to prevent misuse. * Defining public properties for objects (getters and setters, or built-in language support) * Documentation Intermediate level: guidelines that usually should be followed, or design techniques that are widely applicable (though not to be blindly adopted) * SOLID principle http://en.wikipedia.org/wiki/SOLID_(object-oriented_design) * Design patterns http://en.wikipedia.org/wiki/Software_design_pattern Advanced level: important concerns of commercial application development * Knowledge of operating systems * Knowledge of database systems * Knowledge of inter-process communication, or coordination between multiple running programs * User interface design * Compiler toolchain (how to build and consume code libraries built by other software teams in the same company, etc.) * Software testing * Unit testing * Integration testing * Acceptance testing * Manual (human) testing * Exploratory testing * UI Usability ("hallway") testing * Software troubleshooting * Logging * Debugging * Disassembly and memory dumps *.... ..*.. ....* .*... ...*.