HN user

teaspoon

1,894 karma

https://tombrow.com

Posts23
Comments207
View on HN
www.fcc.gov 3y ago

(Redacted) has hacked and stalked me for 12 years [pdf]

teaspoon
7pts9
overcode.yak.net 3y ago

My battle against stage IV melanoma (2005)

teaspoon
1pts0
sentimentalversioning.org 5y ago

Sentimental Versioning

teaspoon
2pts0
whatsstoppingyou.dev 5y ago

GitHub Contributor Graph Generator

teaspoon
1pts0
akrabat.com 5y ago

Ignoring mass reformatting commits with Git blame

teaspoon
3pts0
tombrow.com 5y ago

Before the law sits a Gatekeeper

teaspoon
2pts0
github.com 6y ago

jklp: a 36-key ergonomic keyboard

teaspoon
13pts6
tombrow.com 6y ago

Dark mode in a website with CSS

teaspoon
491pts189
www.informationweek.com 12y ago

Apple iOS Security Defeated By Sneaky App

teaspoon
3pts0
www.kickstarter.com 12y ago

Code is our enemy: flow-based programming with NoFlo

teaspoon
2pts0
georgiaweidman.com 13y ago

Guess You Thought I Was Someone To Mess With

teaspoon
62pts28
37signals.com 14y ago

Why 37signals Doesn't Hire Programmers Based on Brainteasers

teaspoon
605pts423
community.topcoder.com 14y ago

Win $50,000 by digitizing US patents

teaspoon
4pts0
xkcd.com 14y ago

What a Trillion Dollars Looks Like

teaspoon
4pts0
www.apple.com 14y ago

Cards, by Apple: make and send letterpress cards

teaspoon
1pts0
plus.google.com 14y ago

Google Reader's founder on Google Reader

teaspoon
47pts16
massless.org 14y ago

Google Reader's founder on Google Reader

teaspoon
2pts0
messymatters.com 14y ago

Nominology

teaspoon
11pts6
www.facebook.com 14y ago

Steve Jobs testing Photo Booth in 2005

teaspoon
46pts1
messymatters.com 14y ago

Products Don't Spread Virally

teaspoon
49pts15
messymatters.com 15y ago

When Close Isn't Good Enough

teaspoon
1pts0
www.amberdigital.com 15y ago

Where are you in the movie?

teaspoon
2pts0
learnyouahaskell.com 15y ago

Learn You a Haskell is now in print

teaspoon
186pts65

Are you talking about things like sensor noise and chromatic aberration? It would be interesting to see if downsampling the image beforehand affects the result.

However, it's hard to separate image patterns from camera structure insofar as linear projection is a result of camera structure.

That rule doesn't hold for some languages. For example, a Python lexer needs to remember a stack of indentation levels to know whether a given line's indentation should be tokenized as an INDENT, a DEDENT, or no token at all.

Why should I care that the company is Swiss? The point of client-side encryption is that I don't need to worry about who's hosting my data or what jurisdiction they're under.

Trust is Fragile 15 years ago

I wonder if parent was merely advocating obfuscating sensitive data so that engineers don't accidentally see things like "Downsizing-2012.xls". As long as the obfuscation is reversible, the data is still there for those who need it.

Of course, encryption per se is overkill for that. Something like ROT13 would do the trick.

The OP says that double-spacing is an obsolete holdover from the typewriter era, where the extra space made monospaced type easier to read. I'll go one further and say that spacing sentences using space characters -- any number of them -- is obsolete.

In the present era, the act of typing is separate from the act of typesetting. The comment I'm typing now may be typeset in Arial in Chrome, typeset in Ubuntu Mono in Emacs, or read aloud by a software program to a blind person. No prescribed number of space characters is going to be appropriate for all cases.

The reading software, not I, should be responsible for locating my sentence breaks and setting appropriate spacing there. Perhaps in the future we'll assist the software by marking up sentence breaks using a special character sequence. Ironically, a double-space would serve that function pretty well.

Is there an objective metric according to which guessing only positives is a less rigorous strategy than guessing both positives and negatives? Given no prior knowledge about the space of possible rules?

You're claiming that you can infer, just from a triple that I guess, whether I am attempting to confirm or refute the "ascending even numbers" hypothesis. But if I guess (2,4,6) and learn that it doesn't adhere, that's as much a refutation as if I guess (1,2,3) and learn that it does adhere. (2,4,6) looks like an attempted confirmation to you only because you have prior knowledge that the rule is not more specific than "ascending even numbers".

I'm currently appealing a similar rejection of an auto-renewing subscription app. Here's the rejection:

We found that the Purchasability Type for one or more of your In-App Purchase products was inappropriately set, which is not in compliance with the App Store Review Guidelines.

Your In-App Purchase is currently an Auto-Renewable Subscription. However, it would be more appropriate to use the Non-Renewing Subscription In-App Purchase type. Auto-Renewable Subscriptions are intended for periodical apps, such as magazines and newspapers. Non-Renewing Subscriptions should be used for products that are not appropriate for Auto-Renewable Subscriptions.

Nothing in Apple's documentation hints that Auto-Renewable Subscriptions are more appropriate for one class of app than for another, so I was hoping that my reviewer was acting on some subjective, high-level guideline that I could argue on. However, it's beginning to look as if there is a specific, unwritten policy against non-periodical apps.

I thought so too, but appending to a single string does even worse than reduce(:+):

  add 2  0.390000   0.000000   0.390000 (  0.390529)
  +=  2  0.540000   0.000000   0.540000 (  0.537450)

  add 3  0.530000   0.000000   0.530000 (  0.534131)
  +=  3  0.760000   0.000000   0.760000 (  0.752280)

  add 4  0.660000   0.000000   0.660000 (  0.668154)
  +=  4  0.960000   0.000000   0.960000 (  0.954727)
Code: https://gist.github.com/1562994

Couldn't a system with N supervisor-actor relationships be rewritten as a single process with N try/catch statements, where the catch block simply logs the exception and jumps back to the start of the try block?

I haven't used Erlang, so the two patterns seem roughly equivalent. I've even heard exception handling referred to as "happy path programming" by way of contrast to return value handling.

In the common case, selling someone $50,000 of licenses is a $50,000 win for the company.

That actually sounds like a very uncommon case. Even fully client-side software has variable costs in the form of support costs.

Support costs aren't relevant to your parent's example, but they do imply another misalignment of incentives. If a salesperson's commission is based on revenue alone, she'll just as soon sell to a costly, high-maintenance customer as to a profitable, low-maintenance one.

I was curious, so I benchmarked this with Ruby MRI. join('') beat reduce(:+) even on two strings, but is twice as fast only on four or more strings.

   $ ruby -v
   ruby 1.8.7 (2010-01-10 patchlevel 249) [universal-darwin11.0]
   $ ruby benchmark.rb
         user     system      total        real
   add  2  0.390000   0.000000   0.390000 (  0.385910)
   join 2  0.300000   0.000000   0.300000 (  0.305812)

   add  3  0.530000   0.000000   0.530000 (  0.527388)
   join 3  0.320000   0.010000   0.330000 (  0.329390)

   add  4  0.720000   0.000000   0.720000 (  0.720500)
   join 4  0.350000   0.000000   0.350000 (  0.353237)
Code: https://gist.github.com/1562617