github.iserv.nl
我的那堆虚拟机下代码终于他妈不用tsocks绕个半天圈子了
Update:大家好以下是愚人节笑话,虽然前两段是真的,谢谢支持 :D
最近我电脑极其傻逼,老子想用会chrome,chrome搞得我X crash,升级个内核,连续从 3.6 到 3.9 的内核全部他妈的有bug,要么亮度不对,要么黑屏,要么待机起不来,要么蓝牙断网后kernel panic。
wayland 也明显是一帮人在瞎他妈胡搞,为了区区所谓的安全性,放弃了无数的易于开发的方式,处处充斥着可笑的设计,搞到随便实现一个普通的功能,全部都要放到 compositor 里面去实现,实现,实现你妹啊,到时候等着他妹的compositor成天crash或者直接被各种功能拖到比X还卡吧。
所以综上所述,我不打算继续折腾了,反正继续折腾下去也是啥没前途的,那么就这样吧,各位再见。以后还是换个别的啥的系统好了。 Continue reading
开头先引用一下:http://lyric.im/individualism-on-internet/
“像 RMS 那样苦行僧般地活着我做不到也不会去做,像 Linux 那样的桌面我也不会有太多机会去用,但是并不代表他们就不重要。相反,他们很重要,他们的存在本身就是底线。只有支持他们,当我想从某个团体中收回控制时,才有选择的权力。”
搜狗拼音出来了,So what?其他人都回家洗洗睡吗?不,它只是 yet another choice,和 fcitx 或者其他的 sunpinyin,libpinyin 都没半毛钱关系,开源存在的目的本身就不是把用户体验放在第一位的,假设我真的考虑用户体验的话,我早就写程序直接收集所有 fcitx 用户输入了,因为这些数据本身对于改进用户体验都是非常重要的,但是 fcitx 永远也不会主动这么做。Free Software的意义不在于提供了多好的结果,甚至有的时候多数人也就是满足于还不赖就足够了。因为争取用户并不是开源的目标,提供给用户自由才是。
而 Choice is bad 本身就是和折腾 Free Software 的目的相悖的,所以想要做 business 从最开始就是要消除 Choice,Google 对待 Android 显然不是真正开放的,因为厂家需要认可反碎片化的协议。
所以你并不会从那些公司的产品中(即便是开源的)获得更多的自由,Free Software 的存在本身足以阻止封闭产品的垄断。
所以 WPS,或者 Sogou,或者 Ubuntu,或者 Android,或者 Apple,他们的存在都不会影响 Free Software 的存在的意义,所以即便用户对他们如此喜爱,也不会影响我们本来要做的事情。
虽然,我还是蛮在乎用户的 :P,所以即使没改代码,我也会在一些 fcitx 的默认设置的值上纠结半天。
P. S.
希望下半年能有时间开始填拖了很久的坑。
我来美国之后,才终于见到了一个电波相合的死宅,互相讲neta而不会冷场,从前我都是心想这neta高端过头了没人懂的所以从来不讲……
其次,终于见识了一个真心喜欢折腾系统的家伙,比如上次还跑过来和我讨论Xen的虚拟机怎么不出声了之类的问题……(虽然关于这个话题我完全不知道)
但概括起来就是……
这些果然都是小众啊……
一群小众混在一起也改变不了是小众的事实啊……
Well, the non-Chinese language support coming to fcitx is a story only since 2012, and obviously, it’s very hard for us (fcitx developers) to advertise fcitx to non-Chinese user. But I surprisingly find that there are some people around the world using fcitx.
Today, while I was spying fcitx-im.org search history via Google webmaster (It will give me some information about what keywords will lead to the website), I noticed a keyword “fcitx 한글” . This indicates there are some people using fcitx for typing Korean alphabet. So I just try to explore more, by typing this word into Google and search. And Google shows me some more result, and even one page in the result is a blog about how to configure fcitx.
And a few days ago, I noticed a video on youtube, https://www.youtube.com/watch?feature=player_embedded&v=7JWcoqteGwQ . It’s that some other people make a video about configuration (And I even found a bug of fcitx-configtool in the video 😛 ), which is about how to type Malayalam with fcitx.
Though I’m a developer of those input method, actually I have very little knowledge about Hangul (I learned some basic idea of Hangul when I develop fcitx-hangul), and exact no knowledge about Malayalam (I even thought it was Malaysian yesterday). And fcitx really needs people from other languages to test it and use it.
Those discovery makes me very happy, since obviously fcitx is really helping some one in some unknown-to-me part of the world.
P. S.
Following is some real advertisement, fcitx have some unique benefit against others: it archieves both high-modularization, independence, but also high-integration. The core of Fcitx only depends on libc, while every other thing can be replaced.
To get more native UI out of box: https://fcitx-im.org/wiki/Kimpanel
Fcitx doesn’t treat input method framework as a set of separated input method engines, but includes other helpful function which is done by “typing text” in it.
Type unicode, globally, everywhere: https://www.csslayer.info/wordpress/fcitx-dev/unicode-input-support/
And you can even use fcitx as a clipboard manager by Ctrl+Semicolon.
Fcitx really eats its own dog food, it uses the exact same code, to support spellcheck/hint while typing even with plain keyboard layout, and add English word hint to Pinyin at the same time.