anon_d

12 ms·

91.
by anon_d 15y ago
This is actually pretty cool. Shame about the title.
92.
by anon_d 15y ago
alt-codes for unicode characters Just use rfc1345 digraphs. In vim, do :set dg to enable, then just type <(backspace)= . Easy. Emacs also supports this.
93.
by anon_d 15y ago
((will-be (dearly missed)) he) FTFY
94.
by anon_d 15y ago
notepad
95.
by anon_d 15y ago
All these systems are doing it wrong. I don't want online backups, I want an infinite, encrypted, online filesystem. I should be able to mount it and treat it like any other hard disk. The local disk should just be used as a huge cache. I c
96.
by anon_d 15y ago
No no no. My logic is this: Take tight, readable code with short names a replace them with long names, and you'll have worse code. The converse isn't true because complex (bad) codes are more readable with long variable names. Complexity -&
97.
by anon_d 15y ago
This metric relies on the assumption that people are trying to produce readable code. IMHO long variable names are much more helpful in complex codes than simple ones.
98.
by anon_d 15y ago
I never understood the gzip one. Repetitive boilerplate is bad; why hide it?
99.
by anon_d 15y ago
I actually think raw byte-count is a pretty good metric. Documentation size and variable name length are also symptoms of complexity. Specifically I think wc -c $(find -type f) (how many total bytes) and find -type f | wc -c (how many f
100.
by anon_d 15y ago
I've written several (toy) compilers in both Lisp and Standard ML. I completely agree with the statement. Mostly, algebraic data types are a huge win for representing expression trees.
101.
by anon_d 15y ago
Too complicated; just use etherpad.
102.
by anon_d 15y ago
shudder
103.
by anon_d 15y ago
s/use/using/ . I hate not being able to edit my comments.
104.
by anon_d 15y ago
Could people please stop use "Functional Programming" as a synonym for "Pure Functional Programming"? The author uses them interchangeably even though his arguments do not apply to the impure style.
105.
by anon_d 15y ago
rc solves problems with sh by replacing annoying/problematic features. bash adds the same features, but keeps all the problems with sh. Read the "Design Principles" section for specific examples.
106.
by anon_d 15y ago
Looking at Alice ML which has significantly more features than ... FTFY My favorite thing about SML is that it only has known-good features.
107.
by anon_d 15y ago
[...] 1 sec [...]. Good enough for command line tool [...] lol
108.
by anon_d 15y ago
The case-folding behavior of the reader can now be explicitly controlled. Meh. Module System Is there a discussion of this somewhere? Why this style of module system?
109.
by anon_d 15y ago
Once you add exceptions, that goes away. Not really. Exceptions are easy to build on top of continuations, which are already part of R5RS.
110.
by anon_d 16y ago
It's silly to expect to be able to understand text in a foreign language. If you want to read APL, learn APL; It's a great language.
111.
by anon_d 16y ago
Not strictly true, it is quite possible to statically resolve many uses of function pointers.
112.
by anon_d 16y ago
GObject and glib in general aren't an improvement over anything , and both are largely shunned by the c-using community.
113.
by anon_d 16y ago
Everyone here is assuming that Word is easier to learn than LaTeX, but, IMHO, people are misinterpreting familiarity with intuitiveness. Word has a very steep learning curve that people don't see because everyone they know has already learn
114.
by anon_d 16y ago
None of the Lisp OO systems make objects feel second-class.
115.
by anon_d 16y ago
- Take a simple Lisp language. - Remove macros, s-expression. - Add a bunch of shit that could be trivially added if you still had macros.
116.
by anon_d 16y ago
Annoying special cases: $ cd / $ nm=/foo $ ls | grep nm $ cd nm $ pwd /foo $ cd ~ $ ls | grep nm nm $ cd nm $ pwd ~/nm $ echo FFFFFUUUUUUUUU Inflexible: $ cd nm/jan/img cd:
117.
by anon_d 16y ago
Why not just: echo "export nm=`pwd`/blog"' >> ~/.profile . ~/.profile cd $nm There's no need for magic when you know how to shell.
118.
by anon_d 16y ago
I use Vi because it decreases the learning curve for new languages. No new IDE; no new set of emacs key-chords and mode-tricks. I can edit very efficiently in Vi, and all of my editing tricks/habbits apply to all languages. Technically I u
119.
by anon_d 16y ago
After I swiched to vi, I stopped feeling the need to work with multiple files; Just pop in and out of the shell.
120.
by anon_d 16y ago
Visual Studio which has good 'discoverability'. Not my experience at all . It's a sea of confusion and pain.

More ›