1,629 karma · joined February 14, 2011
For IRC or chat, it doesn't make sense to use capitalization or most punctuation. The beginning of the line serves as a delimiter between messages; capitalization is redundant in this capacity. Likewise, the end of the line serves a similar purpose, which makes periods (generally) redundant. The addition of a period in this medium adds extra emphasis to the message, which is often interpreted as aggressiveness (hence this article).
Also, it is unfair to associate lack of capitalization with poor grammar and spelling. Poor grammar is associated with lack of education. Lack of capitalization should not be! You probably were not implying an association, but many others I have spoken to over the years have. (For some reason, I've had a lot of conversations about this stuff...)
It's also a bit odd when people use capitalization beyond "I"--one of the best ways to tell newer users from older users.
I feel so weird dropping by, say, freenode, where the customs are so different.
(EDIT: Since people here are mentioning age, for the record, I am soon to be 26)
https://news.ycombinator.com/item?id=6672029 -> http://nypost.com/2013/11/05/microsoft-com-is-stuck-in-the-1... -> https://news.ycombinator.com/item?id=6681746
If I actually need to do something with an input or output before sending it to the next command, I'll switch to Python.
For CLI tasks in Python, http://docopt.org/ and http://shell-command.readthedocs.org/en/latest/ are invaluable tools. Yes, I know about Envoy, but shell_command is much nicer to use in my opinion. Envoy doesn't automatically escape arguments, which is annoying for all the reasons that SQL injections are annoying.
If you're interested, please read our ToS here: https://secure.mysociety.org/admin/lists/pipermail/developer...
That the contour of the API differs slightly means nothing. An example of true incompatibility would be, say, supporting UNIX-style mounts on Windows. If you wanted to support that cross-platform, either you or a library would have to directly implement the semantics of UNIX mounts, as opposed to just making a shim over what the OS already provides.
OpenSSH might count, from the rant on their homepage:
Please take note of our Who uses it page, which list just some of the vendors who incorporate OpenSSH into their own products -- as a critically important security / access feature -- instead of writing their own SSH implementation or purchasing one from another vendor. This list specifically includes companies like Cisco, Juniper, Apple, Red Hat, and Novell; but probably includes almost all router, switch or unix-like operating system vendors. In the 10 years since the inception of the OpenSSH project, these companies have contributed not even a dime of thanks in support of the OpenSSH project (despite numerous requests).
On a slightly unrelated tangent, the tup build system supports inotify, which I appreciate.
Maybe it is just that the Internet is more popular than it was in the 90s. On the other hand, I think rich media offers more opportunities to be snarky, and of course we are going to take advantage of this. #smh #justsayin
Instead, there are discount vendors that will sell older chips (generally 2-3 generations behind the curve) for cheap. The names to watch are Digilent for Xilinx and Terasic for Altera.
I tend to prefer Xilinx stuff. I don't really have the time to write a more detailed reply, but you can browse around here [1]. Get something with lots of ports, or you won't be able to make anything interesting without a lot of pain (where interesting means "I want to hear/see/communicate-to another-computer my results"). The Zynq boards also come with an ARM processor that can talk to the FPGA fabric.
[1]: http://www.digilentinc.com/Products/Catalog.cfm?NavPath=2,40...