jstimpfle

458 ms·

3361.
by jstimpfle 11y ago
That's fantastic guys. I mean, think about it. Screenshot a . single . DOM . element. Upvote this. Oh my god I think I should just get some sleep.
3362.
by jstimpfle 11y ago
> This should be stateless; if you lose a packet, the next one has a full state update. This is enough for a simple FPS game. Also enough considering packet reordering? And corruption?
3363.
Free Monads from Functors from GADTs(jstimpfle.de)
2 points by jstimpfle 11y ago|0 comments
3364.
by jstimpfle 11y ago
Seconded. This is one of the few lines in my .vimrc > nmap <F11> :if exists("syntax_on") \| syntax off \| else \| syntax enable \| endif \|<newline><newline> that makes F11 a toggle-highlighting button. Someti
3365.
by jstimpfle 11y ago
The title is a reference to Russ Cox' excellent article (series) on implementing regular expressions: http://swtch.com/~rsc/regexp/
3366.
by jstimpfle 11y ago
I generally like the idea of tabular text files where the last column is free form text. If you need more commenting freedom or flexiblity, why not make another indirection and generate the data from some source which is tailored to your ne
3367.
by jstimpfle 11y ago
That's a good point. Makes me think again of "slow devices" and interrupts leading to EINTR or partial reads/writes. In my eyes a beautifully pragmatic solution to a real world problem, and yet at some point SA_RESTART w
3368.
by jstimpfle 11y ago
> It's really two separate discussions though: what is s good input/output format for Unix-like tools, and what makes a good format for a config file. I don't see where these are not one single problem. Everything is a fil
3369.
by jstimpfle 11y ago
>> Ten years ago this would be --xml. Who knows what it would be ten years from now. Text streams are timeless > Text streams are just an ad hoc structured format. Even an out of date format is better than one you have to invent or
3370.
by jstimpfle 11y ago
Thanks, also for your comments on the other one. I wish I could make a qualified analysis of the code snippet, but I'm not up to it. Adding -x / --one-file-system is all constructive suggestions I have regarding the command.
3371.
by jstimpfle 11y ago
> > However, some users didn't like having to think about whether the source and destination were on the same mountpoint > That's actually a good thing, because it makes scripts more composable. I argue that it actually p
3372.
The Unix way: A note on composability(jstimpfle.de)
15 points by jstimpfle 11y ago|3 comments
3373.
by jstimpfle 11y ago
There are different things that "move" can mean. rename(2) can "move" in a safe way, but not across devices. > Atomic file system changes are simply a nice side effect. Disagree. Also, my article was to show how mv&#x
3374.
by jstimpfle 11y ago
My article is not about how to write robust shell scripts. (Which is impossible in a very broad sense: for example, use a single pipeline A | B and include in your operational semantics that all processes can fail (SIGKILL). In shell, you c
3375.
by jstimpfle 11y ago
> In other words the "rename("/mnt", "/mnt/foo")" should have failed with EINVAL, not EXDEV I thought about that one, too. But I guess there is 2 kinds of subdirectory-of: In the mount hierarc
3376.
by jstimpfle 11y ago
Copy-then-remove-old has vastly different semantics. It creates a new file identity. For a start, just imagine what happens when the old file is still open from some processes. I'm not saying there should not be convenience wrappers ta
3377.
Unix filesystems: How mv can be dangerous(jstimpfle.de)
89 points by jstimpfle 11y ago|38 comments