yoduh · HackerTrans

14 yıl öncediscuss

My opinion: Anytime you share code by posting it publicly, you should always be prepared for negative feedback. In some cases that might be the whole point of posting it: you want to learn from your mistakes.

yoduh

14 yıl öncediscuss

Very well said.

yoduh

14 yıl öncediscuss

It's funny what Torvalds said about "good taste" because I have had the same sort of idea for years. But I'd never heard any programmer articulate it as such. I also call it "sensibilities". I have no clue if his idea of what is "good taste" is even remotely similar to mine, but it's interesting that he also thinks about this notion of "good taste". I can eliminate programmers and programs very quickly using this sort of qualitative assessment. It might not even be necessary to see any code. Just knowing how they would approach a problem, how they would design a solution (Rube Goldberg machine), and of course what language they would use says something about their "tastes". It's not so much a matter of what they do or don't know how to do, it's their selections from among different choices. Imagine hypothetically a programmer knows every language and can implement any design. The language he chooses and the design he chooses tells us about his "taste".

yoduh

14 yıl öncediscuss

<sarcasm>

Whatever you do, do NOT turn off Javascript, or stop using Microsoft products like Windows, or Adobe products like their "Flash" player or even their seemingly harmless PDF viewer.

Don't be fooled into thinking these "highly sophisticated" hackers need such things in order to succeed in their "exploits".

And even if they did, the costs of NOT using Javascript, Microsoft and Adobe far, far outweight the benefits.

</sarcasm>

Nevermind the word "lethal", I've always wondered by the word "attack" was chosen within the cryptography/computer security world. Maybe someone knows the history behind it? Once you get used to this term it's seems normal. But at first it's a bit strange. Playing around with computers and binary numbers seems like the furthest thing from an "attack" one could imagine. But I guess it goes without saying that computer nerds have very vivid imaginations.

yoduh

14 yıl öncediscuss

Hypothesis: Yelp relies on blackmail.

Disprove it.

yoduh

14 yıl öncediscuss

Haven't looked at the cheat sheets but...

If you just want something readable, a couple of quick and dirty ways are:

    col -bx < typescript|less
    strings typescript |less

You can further clean things up by deleting unwanted lines or characters using sed.

    strings typescript|sed '1d;/deleteme/d;s/deleteme//g'|less

There's also an old utility called ttyrec/ttyplay you might like.

yoduh

14 yıl öncediscuss

"Informational article" style advertising. In this case the ad is for Puppet/Chef.

yoduh

14 yıl öncediscuss

The author says: "Or it can form the backbone of a rich, full-powered Javascript command-line, inspired by "perl -pe", and doing for structured data what sed, awk, and grep do for text."

But... "structured data", at least in his examples (and nearly all the JSON I see on the web), is... text. Does his perl script handle binary json?

The author says: "Try doing THAT with any other CLI one-liner!"

Indeed I will, since I do not know perl. Should I learn it?

The folllowing seems to work, but I only tested it on the author's earthporn.json example

1. compile CamelCase filter called yycamel

2. compose throwaway sed oneliner to massage the text

3. pipe through unicode to ascii filter (not included)

4. pipe through yycamel

(I really do not like CamelCase, but whatever.)

   cat > camel.l << eof
   %%
   [ ][A-Za-z]  printf("%c",toupper(yytext[1]));
   eof

   flex -iCfa camel.l
   cc lex.yy.c -static -ll -o yycamel

   sed 's/\"title\": /\
   /g;' earthporn.json |sed 's/[[(]/\ 
   /g;' | sed '/^\"[a-zA-Z]/!d;s/[^a-zA-Z]/ /g;s/  */ /g' |yycamel

comments