apenwarr

27 ms·

211.
by apenwarr 15y ago
You could also try wvtest, which is a bit lighter weight and works with any shell, not just bash: https://github.com/apenwarr/wvtest
212.
by apenwarr 15y ago
It's as simple as this: never sign the document they hand you on the spot. Give it a day or two, say you might need to talk to a lawyer. They're firing you . They really want you to sign this document. They won't actually really take
213.
by apenwarr 15y ago
The waiter rule works - if someone is rude to a waiter, it's an incredibly bad sign, because at the very least, it means they've never heard of the waiter rule. However, just because someone is nice to a waiter doesn't mean they have good
214.
by apenwarr 15y ago
Not exactly a dick: you're intensely conscious of the social hierarchy. I've noticed that some people just are, and some people just aren't. What you do with it is what makes you a dick or doesn't. And a lot of that is under your conscio
215.
by apenwarr 15y ago
Colinux has the ability to mount your windows fs nowadays. I think the Linux module is called "cofs".
216.
by apenwarr 16y ago
30-50ms isn't nearly enough latency to make ssh suck. Even 225ms is fine for ssh. You almost certainly were suffering from high packet loss, which means you get spikes of super high "latency" in TCP (because after a couple of packet los
217.
by apenwarr 16y ago
I'm pretty sure the example in this article wouldn't confuse git: weirdness like this is the reason git has the "recursive" merge algorithm instead of just doing a plain three-way merge. A recursive merge basically tries to merge some of
218.
by apenwarr 16y ago
sshuttle does not (currently) attempt to do anything other than TCP and DNS. UDP ought to be possible (other than that UDP-over-TCP could have similar problems to TCP-over-TCP, ie. that packets are never lost and this could confuse a hypot
219.
by apenwarr 16y ago
What happens is you essentially get "infinite bufferbloat." When there's no packet loss, you end up absolutely filling the transmit buffers at the entry points to the tunnels. The result, as other people have mentioned, is extremely poo
220.
by apenwarr 16y ago
Previously on HN: http://news.ycombinator.com/item?id=1313083
221.
by apenwarr 16y ago
Sure, for some things. But it wasn't a valid alternative before a bunch of people decided to spend an awful lot of time making it, despite the unlikeliness of it ever being a real competitor to DOS. And years before that even, the GNU proj
222.
by apenwarr 16y ago
I agree with you, and about Waterloo specifically. I'm probably going to be banned from HN for saying this, but the giant Google talent vacuum cleaner is one potential reason that starting a startup right now is especially difficult and may
223.
by apenwarr 16y ago
Oddly enough, I'm in the opposite situation: I've never held a serious job that wasn't, in some way or another, working for myself. (Other than 4-month co-op placements as a student.) The opposite experience will be interesting to try out.
224.
by apenwarr 16y ago
Remember that's an average. Some people produce less and get paid less, some people produce more and get paid more. The two are not always correlated of course. In fact, at Google in particular, I'm sure it's crazily skewed: most people
225.
by apenwarr 16y ago
Your last line is an interesting one. The point when more than 50% of my friends worked at Google was a really serious one for me: it became the point at which joining Google meant gaining the freedom to talk to my friends. Not that th
226.
by apenwarr 16y ago
Good point, I forgot about those! They are a very exciting feature of the perl6 design, if only because someone is finally serious about making progress in the world of parsing. Some interesting articles about perl6's parsing: http://dev.
227.
by apenwarr 16y ago
Wow, you just put exactly what I was trying to say into a single simple sentence. Thanks!
228.
by apenwarr 16y ago
Many of the new "nosql" databases use a lot of similar concepts. But it's a new thing: I'm trying to see into the future here, not tell you what's already happened :) As for different DVCSs, I think you're exactly backwards. Almost everyo
229.
by apenwarr 16y ago
I'm the author of the OP. The comments here make me think (again) that the article wasn't clear enough: admittedly, when I first wrote it, I was just discovering git, as some of the comments said. The difference between me and perhaps man
230.
by apenwarr 16y ago
This is generally good advice, but redo tries to do something else: it actually tests all your shells, and picks the one that supports the features we're expecting. That way we can set a minimum baseline. All the features in the article
231.
by apenwarr 16y ago
Sweet. I've changed redo to try that as one of its possible shells.
232.
by apenwarr 16y ago
I'm pretty sure Solaris is one of those nasty OSes that continues to include a broken /bin/sh for "backwards compatibility." They presumably also have a non-broken shell around somewhere in the standard install. This is why redo goes th
233.
by apenwarr 16y ago
That only works in bash.
234.
by apenwarr 16y ago
pdksh (at least the one in Debian) has numerous bugs; try the shelltest.od script in redo to see some of them. I agree that "just see if it works" isn't a good portability strategy if you only test one shell. But the idea is to get as many
235.
by apenwarr 16y ago
Looks like $() is really really POSIX: http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu... In general, beware of trusting the people who wrote your editor instead just trying it to see if it works :)
236.
by apenwarr 16y ago
$() is standard, not a bashism. Every code example in the article was tested on multiple shells. Use $() and be happy, and I recommend never touching the backquotes again. They're a disaster as soon as you need to nest them. ${CC:=gcc} i
237.
by apenwarr 16y ago
No, that's exactly wrong. Go start your company and get your funding as fast as you can. Then hold onto it. When the inevitable dip (or "pop", for the zealous) comes, that's when you use that money to hire some recently-out-of-work engin
238.
by apenwarr 16y ago
A random nitpick that you might find interesting: in fact unused electricity is not "simply lost." Where would it go? Because of the law of conservation of energy, it would have to go somewhere, and we're talking about what might be a lo
239.
What I want from Open Source Hardware(blog.upverter.com)
3 points by apenwarr 16y ago|0 comments
240.
by apenwarr 16y ago
There are relatively painless workarounds for both situations. For multiple outputs, you can just make sure that anybody who depends on %.c also depends on %.h. This is pretty easy in the case of yacc. Then the rule can just be one for cr

More ›