- Mac OS X 背后的故事（一）力挽狂澜的Ellen Hancock
- Mac OS X 背后的故事（二）Linus Torvalds的短视
- Mac OS X 背后的故事（三）Mach之父Avie Tevanian
- Mac OS X 背后的故事（四）政客的跨界
- Mac OS X 背後的故事（五）Jean-Marie Hullot 的天才天才發明 Interface Builder
- Mac OS X 背后的故事（六）上善若水 Cordell Ratzlaff 引发的 Aqua 革命（上）
- Mac OS X 背後的故事（七）上善若水 Cordell Ratzlaff 引發的 Aqua 革命（下）
- Mac OS X 背後的故事（八）三好學生 Chris Lattner 的 LLVM 編譯工具鏈
- Mac OS X 背後的故事（九）半導體的豐收（上）
- [Mac OS X 背後的故事（十）半導體的豐收（中）](https
pi1ot pi1ot
mckelvin
/ remove_jietumacapp.sh
Last active
October 25, 2022 03:11
— forked from ITJesse/remove_jietumacapp
删除 QQ for Mac 的流氓截图
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #!/bin/sh | |
| chmod 0000 "/Applications/QQ.app/Contents/Library/LoginItems/QQ jietu plugin.app/Contents/MacOS/QQ jietu plugin" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 尊敬的客户，您好！ | |
| 接到电信运营商的通知，为了增强网络安全性，中国电信将于北京时间2017年09月28日00:00开始在全国范围的IDC机房电信链路网络出口添加病毒防护策略，屏蔽部分端口（详细参看下列清单），届时对这些端口的访问将被阻断。建议您提前检查您的业务中是否包含下述端口的服务，提前更换端口以免受到影响。 | |
| 具体屏蔽的端口如下： | |
| 目的端口：137-139，协议：TCP/UDP | |
| 目的端口：593，协议：TCP/UDP | |
| 目的端口：445，协议：TCP/UDP |
codeslinger
/ CircularFIFO.h
Created
January 3, 2016 15:38
SPMC ring buffer implementation in C++ from DKit
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /** | |
| * CircularFIFO.h - this file defines the template class for a single-producer, | |
| * multi-consumer, circular FIFO queue with a size initially | |
| * specified in the definition of the instance. This queue | |
| * is completely thread-safe so long as there is ONE and ONLY | |
| * ONE thread placing elements into this container, and there | |
| * can be as many as necessary remobing them from the queue. | |
| * The syntax is very simple - push() will push an element, | |
| * returning 'true' if there is room, and the value has been | |
| * placed in the queue. |