widely popular. Martin had written most of the ØMQ code, and I’d put up the funding
and organized the community. Over some Zlatý Bažant, we agreed that ØMQ needed
a new, simpler website and a basic guide for new users.
Martin collected some ideas for topics to explain. I’d never written a line of ØMQ code
before this, so it became a live learning documentary. As I worked through simple
examples to more complex ones, I tried to answer many of the questions I’d seen on the
mailing list. Because I’d been building large-scale architectures for 30 years, there were
a lot of problems I was keen to throw ØMQ at. Amazingly, the results were mostly simple
and elegant, even when working in C. I felt a pure joy learning ØMQ and using it to
solve real problems, which brought me back to programming after a few years’ pause.
And often, not knowing how it was “supposed” to be done, we improved ØMQ as we
went along.
From the start, I wanted the guide to be a community project, so I put it onto GitHub
and let others contribute with pull requests. This was considered a radical, even vulgar
approach by some. We came to a division of labor: I’d do the writing and make the
original C examples, and others would help fix the text and translate the examples into
other languages.
This worked better than I dared hope. You can now find all the examples in several
languages, and many in a dozen languages. It’s a kind of programming language Rosetta
Stone, and a valuable outcome in itself. We set up a high score: reach 80% translation
and your language gets its own guide. PHP, Python, Lua, and Haxe reached this goal.
People asked for PDFs, and we created those. People asked for ebooks, and got those.
About a hundred people have contributed to the guide to date.
The guide achieved its goal of popularizing ØMQ. The style pleases most and annoys
some, which is how it should be. In December 2010, my work on ØMQ and the guide
stopped, as I found myself going through late-stage cancer, heavy surgery, and six
months of chemotherapy. When I picked up work again in mid-2011, it was to start
using ØMQ in anger for one of the largest use-cases imagineable: on the mobile phones
and tablets of the world’s biggest electronics company.
But the goal of the guide was, from the start, a printed book. So it was exciting to get an
email from Bill Lubanovic in January 2012, introducing me to his editor, Andy Oram,
at O’Reilly, suggesting a ØMQ book. “Of course!” I said. Where do I sign? How much
do I have to pay? Oh, I get money for this? All I have to do is finish it?”
Of course, as soon as O’Reilly announced a ØMQ book, other publishers started sending
out emails to potential authors. You’ll probably see a rash of ØMQ books coming out
next year. That’s good. Our niche library has hit the mainstream and deserves its six
inches of shelf space. My apologies to the other ØMQ authors. We’ve set the bar horribly
high, and my advice is to make your books complementary. Perhaps focus on a specific
language, platform, or pattern.
xiv | Preface
剩余514页未读，继续阅读
wbybyb
- 粉丝: 1
- 资源: 6
我的内容管理
展开
最新资源
- 多模态联合稀疏表示在视频目标跟踪中的应用
- Kubernetes资源管控与Gardener开源软件实践解析
- MPI集群监控与负载平衡策略
- 自动化PHP安全漏洞检测：静态代码分析与数据流方法
- 青苔数据CEO程永：技术生态与阿里云开放创新
- 制造业转型： HyperX引领企业上云策略
- 赵维五分享：航空工业电子采购上云实战与运维策略
- 单片机控制的LED点阵显示屏设计及其实现
- 驻云科技李俊涛：AI驱动的云上服务新趋势与挑战
- 6LoWPAN物联网边界路由器：设计与实现
- 猩便利工程师仲小玉：Terraform云资源管理最佳实践与团队协作
- 类差分度改进的互信息特征选择提升文本分类性能
- VERITAS与阿里云合作的混合云转型与数据保护方案
- 云制造中的生产线仿真模型设计与虚拟化研究
- 汪洋在PostgresChina2018分享：高可用 PostgreSQL 工具与架构设计
- 2018 PostgresChina大会：阿里云时空引擎Ganos在PostgreSQL中的创新应用与多模型存储
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
