ralph

Why use grep(1)?

    svn status | sed -n 's/^? *//p' | xargs svn add

You can also drop the selected text just to the right of the rightmost tab, left of the "scroll tabs right" arrow. When you're over the right spot, a down-pointing arrow appears indicating that a new tab will be created there. This actually works between any two tabs too, but the drop area can be smaller.

The 121 seconds of my time would have been better spent showing me it in action instead of trying to instill that there's only one M in scrumy.com. I know that now, but I don't need to know it since I'm not planning on spending more time investigating it. I think that's a shame for the both of us.

It's still down at the moment, but are you aware of diction(1) and style(1)?

You're assuming a limit on password length won't apply. In that case, I may as well print it in binary and just have 0 and 1 ASCII characters in my password.

Some of us are old enough to have used ed(1) out of necessity. :-) These days, `sed -i' is also useful for quick one-liners.

You used `md5' in your pipeline, I assumed you meant md5sum(1) as I'm not aware of an md5 command. md5sum gives a 32 character string that's the 128-bit MD5 digest in hex. Therefore it uses only characters 0-9a-f making the password weaker. I'm sorry that you find this criticism "silly" but others reading your pipeline may not, like you, realise its flaw, you got an upvote after all, and use it.

head may read an awful lot from /dev/urandom before it exits. ;-) And md5sum would limit my password to 0-9a-f whereas with tr(1) I get to choose the character set.

Bug: the whole of the URL isn't turned into a link in the parent: http://en.wikipedia.org/wiki/Braid_(video_game)

I use some variation on

    tr -dc 'A-Za-z0-9' </dev/urandom | dd bs=8 count=1 2>/dev/null; echo

when I want a quick throw-away password.

Would be nice if the put Fan's license somewhere clearly on the web site.

Have a closer look at the photo. There's rows of holes for connectors along the top and bottom of the board. I see one set is labelled JTAG. It looks like the tracks and holes are there for soldering on other I/O connectors if you wish. Oh, and there's a LED in each of the bottom corners. ;-)

Another unwelcome change is that the XML you get from, e.g. http://del.icio.us/api/tags/get now comes with a trailing comment containing the date and time. This means periodically downloading your data to store off-del.icio.us results in a growing set of diffs even when none of the real data's changed. E.g.

    -<!-- fe02.api.del.ac4.yahoo.net uncompressed Thu Jul 31 02:23:30 PDT 2008 -->
    +<!-- fe02.api.del.ac4.yahoo.net uncompressed Fri Aug  1 01:28:35 PDT 2008 -->

Now, I can change my scripts to easily work around this, but should I really have too? Didn't compiler writers learn a long time ago that embedding a timestamp into a object file is a bad idea; far better for it to be determinate for comparison and testing.

P.S. +1 for wanting the old UI back. Sorry, joshu.

Submitters, please spare a thought for those of us that read RSS. All I get is:

    Subject: WoW

    [Comments][1]

       [1]: http://news.ycombinator.com/item?id=228117

    URL: http://mattmaroon.com/?p=396
    comments: http://news.ycombinator.com/item?id=228117
    

If it's worth bothering all of us with your submission, please take the time to add a sentance covering the content if it's not obvious.

Kernighan and Plauger's _The Elements of Programming Style_ covers exactly this ground, showing in turn poor code and how it could be better. They use real-life bits of code they come across, not artificial constructions. Kernighan and Pike's later _The Practice of Programming_ also partially covers this. Both are must-reads. http://troff.org/pubs.html#style and http://troff.org/pubs.html#tpop

Yes, someone on slashdot was complaining of this. He visited a pr0n site daily. Fine. However, now there's a good chance that site will flick by, two lines high, as he starts typing in the location bar before he gets too specific. He doesn't want to wipe his whole history, but nor does he want it appearing all the time. I can see his point. Just type `e' and the top match isn't specific to the very vague `e' but may be embarassing.

It's the

    @{$h{$k}}

syntax that's fugly. +1 for Python.

1Gb is 1000Mb. 1Gib is 1024Mib.

What kind of binary files do you put under SCM?

"We have persistent objects, they're called files." -- Ken Thompson.

Can people submitting posts please take the time to give a few words of description if the title doesn't explain. It would save lots of others reading posts they've no interest in. Some of us use RSS to follow the site and having to pick and choose based on "Why is this shameful practice so common?" doesn't help.

"The files are kept forever as long as they are being downloaded".

Do they say how long after the last download the files are kept? Else they could always free up some disc space by removing the least recently downloaded files.

Very handy, and an improvement on how I remember it.

It would be nice to be able to search for "that post foo made to which bar replied". Often you remember the structure of the conversation rather than a unique word or two.

Here's the last time I pointed it out. http://news.ycombinator.com/item?id=18083 pg made the post dead and emailed me about publishing a DDoS. Yet here we still are, using a broken concept.

The posts on this thread show how news.yc has gone down the tubes.

No, it doesn't. The cheatsheet doesn't allow !^ and !$ to be constructed. The closest would be !!:^ and !!:$.

Let's take http://news.ycombinator.com/threads?id=pg as an example. When I visit that I get dealt 75 fnids. They're different every time I go to the page. So I'm using a new 75 slots in the cache every time. It's little overhead in CPU or bandwidth for me to get the page but it has a big impact on the other users of the system if I flush their fnids out of the cache before they try and use them. I first pointed this out at the end of April 2007. In response, pg cut the number of fnids used, but they've crept back in.

The technique's flawed, trivial to exploit, and should be dumped.

Continuations used to be used more on news.yc but it was trivial to flush the cache by making a few requests from a single client causing everyone's sessions to be hosed. That causes a switch to URL parameters for lots of things; why not all things? It's a fundamentally flawed model that I've never seen pg defend. It's certainly not scalable. Either the server stores info for all N clients, which fails for large N, or you give each client their own piece of info to store.

Yawn. Not definitive. Nothing that reading bash(1) wouldn't tell you. And bash(1) at least covers the useful !^ and !$ which this doesn't.

If I search for "ralph dos" I seem to get results from all over the place. One nice feature would just be able to get a list of a user's posts.