lethwei的专栏

In the late 1960s, good programmers shared an intuition about software development: If you get the data structures right, the effort will make development of the rest of the program much easier.    

<br />周末无事, 想找本有意思的书看, 想起这本, 于是躺在床上翻了起来.<br /> <br />这类讲历史的书, 一向都比较有意思, 尤其是这种当事人亲自来讲述的, 一来可以了解很多东西的来龙去脉, 二来么, 八卦也比较多.<br /> <br />Bjarne 是个很会写文章的人, 大道理一通一通(非贬义 ;), 之前看他的 "TCPL" 就有这感觉. 看过这本自述史兼介绍 C++ 设计过程的书后才知道, 原来是位民间哲学爱好者.<br /> <br />C++ 现在挺不受人待见, 好像是个人都

<br />(WPF 设计师讲述 WPF 框架设计思路的书, 非常不错. 之前看了一半, 一直想要看完, 刚好最近有项目界面决定采用 WPF, 捡起这本书, 继续学习)<br /> <br />Chapter 5 Visuals<br /> <br />WPF 是个界面框架, 而界面, 是通过图形描绘出来的. <br />因此, 这一章讲的是 WPF 图形绘制机制, 同时也是上层界面搭建的基础.<br /> <br />5.1 2D Graphics<br /> <br />WPF 的 2D 图形绘制分为

<br />Chapter 6 Data<br /> <br />在 WPF 中, 数据绑定是一个核心的概念.<br /> <br />6.1 Data Principles<br /> <br />Most applications are built to display or create some type of data.<br /> <br />6.1.1 The .NET Data Model<br /> <br />A data model describes the contract be

<br />Chapter 7 Actions<br /> <br />Up to now we have focused on the output side of the platform, looking at how an application is built up from controls that use visuals to display and layout to position everything.<br /> <br />Now we can start to look at

<br />(一直有听说, Qt 的 API 设计很出色, 这篇文章以前看过, 最近试着用 Qt 做开发, 所以再看一遍)<br /><br />An API is to the programmer what a GUI is to the end-user. The 'P' in API stands for "Programmer", not "Program", to highlight the fact that APIs are used by programmers, who are

<br />Chapter 8 Styles<br /> <br />8.3 Using Styles for Good, Not Evil<br /> <br />8.3.1 Build Themes, Not Styles<br /> <br />Consequently, generally the best practice is to think of a theme as a “thing” rather than just a collection of styles at the root

<br />"You seem to glance of the fact there is no alternative. C++ has it’s flaws but no one is better at what it does. The most interesting software needs to have good performance: search engines, video games, dsp, artificial intelligence, etc. Y

<br />(微软 VC++ 小组关于 c++ parser 对 intellisense 支持的一些讨论, 比较有意思)<br /> Rebuilding Intellisense<br />Our first design decision involved both accuracy and scalability. We needed to decouple the Intellisense operations that require precise compilation inform

<br />(MSDN Magzine 上的文章)<br /> <br />"There are many different ways to distribute your work across multiple cores. One of the easiest and most robust is called task-based programming."<br />"To achieve this state of multicore bliss, you’ll have to r

<br />(Anders artima 访谈系列的第二部分)<br /> <br /> "Do the simplest thing possible, but no simpler."<br />最近在规划一些小东西, 发现自己常常无意识的犯下过度设计的错误, 幸好看到这句话, 让我幡然醒悟.<br /> <br />"I'm a strong believer in being minimalistic."<br />这个系列, 七七八八看差不多了, 从中可以看出, Anders 对于 .Ne

<br />因为开发需要, 最近开始研究 Web Service. 在 MSDN 中找到一篇文章 XML Files - The Birth of Web Services, 比较清楚的阐述了 Web Service 的定义, 产生背景, 及涉及的几个主要知识点, 非常浅显易懂, 在此记下心得体会<br /> <br />Web Service 说白了, 就是一种分布式的计算/数据服务, 套用文章中的说法, 叫 Distributed Computing Technology, 这种远端提供服务调用的程

<br />之前说到, Web 应用在平台互用方面的巨大潜力, 导致了 Web Service 概念的出现, 但是最初的 Web 应用并不是为这个目的设计的, 所以存在一定的缺陷, 照搬原文说法, 即 "URL-encoding and HTML aren't flexible, powerful, or descriptive enough for most data representation needs"<br /> <br />这些缺点, 主要讲的是 HTML. HTML 作为一个界面布局,

<br />(题外话: 推荐 www.artima.com, 很不错的技术网站, 可能很多同学都知道, 并早已熟读上面的文章了. 恕我孤陋寡闻, 最近因为设计一个尽管很小的分布式系统, 但也遇到了一些棘手的问题, 才按图索骥, 找到了这个网站.)<br /> <br />Designing Distributed Systems - A Conversation with Ken Arnold<br />这是一篇访谈, 讨论的是分布式系统设计.<br />看这篇访谈前可以先看另一篇文章预热(Introd

<br />(题外话: 这是  Ken Arnold 系列访谈的第二篇, 之前的第一篇, 及第三篇)<br /> <br />这篇访谈谈论的是 Taste 与 Aesthetics.<br /> <br />访谈开头, 提问者 Bill Venners 提到了 JINI 的主架构师 Jim Waldo, 并引用了他的一句话, "Much of [building a good team] is just finding people who have the right sense

<br />(题外话: 这是  Ken Arnold 系列访谈的第一篇, 之前的"Designing Distributed Systems"是该系列的第三篇)<br /> <br />这篇访谈, 讨论的是设计的问题.<br /> <br />Ken 认为不存在所谓的"完美"的设计, 原因有:<br />1. "One is that all designs take place in context.",  "So part of the reason no perfect design ex

<br />"To me the best way to understand the distinction between C# generics and C++ templates is this: C# generics are really just like classes, except they have a type parameter. C++ templates are really just like macros, except they look like classes

<br />ABSTRACT<br /> <br />"Reliable systems have always been built out of unreliable components"<br /> <br />"There are two implications of asynchronous state capture:<br />1) Everything promised by the primary is probabilistic.<br />2) Applications must

<br />(题外话: 比较有意思的系列文章, 回忆了 Visual Studio 的发展历程, 从远古的 DOS 年代, 及 VC 1.0 开始)<br /> <br />My History of Visual Studio (Part 1)<br /><br /><br />"C++ is like that, a lot of things seem easy until you combine them with other things and then they get hard."<br

<br />(Anders artima 访谈系列, 这是第 5 部分)<br /> <br />关于 DLL Hell<br />"The absolute answer, the only way guaranteed to not break anything, is to change nothing."<br />因此 "Versioning is all about relaxing the rules in the right way and introducing leeway.

<br />(artima 原文, reddit 上的讨论)<br /> <br />托管环境日益流行, 作为托管中重要环节的 GC, 对性能有比较大的影响, 所以对 GC 机制的一定了解, 还是有必要的.<br /> 原文讨论了他们公司实现 Pauseless GC 的思路, 在 reddit 的讨论中也有一些很精彩的评论, 在此摘抄部分.<br /> <br />rayiner@reddit<br />"There is no such thing as "pauseless" memory